Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I don't think that existence of independent (276) makes really sense when widely used (12625) also exists.

Also a task of text parsing is a subset of parsing in general terms, and parsing-of-not-a-text is less used than of a text, isn't it?

Update: Please note that [parsing] is used significantly more often, more than 45 times! [parsing] will mean the same as [text-parsing], it can do its "job". Will anybody notice that [text-parsing] is called just [parsing] now? It already have 3 synonyms, and can have more.

I think such a great amount of tags (909 pages, it's more then 32000 tags!) makes no sense, it's bad, they are too various. Do we want a tag for each possible term in programming? No, I think we don't. Will you add [text-parsing] into your favorite tags, while [parsing] will no addt?!

share|improve this question

closed as off-topic by Martijn Pieters, animuson, Shadow Wizard, Aziz Shaikh, ChrisF Aug 12 '14 at 9:38

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Martijn Pieters, animuson, Shadow Wizard, Aziz Shaikh, ChrisF
If this question can be reworded to fit the rules in the help center, please edit the question.

Parsing covers much more that just text parsing, I'd say. What about a regular expression parser for example? – Martijn Pieters Aug 25 '12 at 17:39
@MartijnPieters: I think he meant text-parsing --> parsing – nhahtdh Aug 25 '12 at 17:45
@nhahtdh: Yes, I understood that. But text-parsing has a more specific meaning than the generic parsing, which is what I meant. – Martijn Pieters Aug 25 '12 at 17:46
@MartijnPieters: They hardly make any difference to me. Parsing involves text processing either way. – nhahtdh Aug 25 '12 at 17:49
Well, there is parsing of tokens in a compiler. I'm not sure that such parsing always involves text, and programmers who parse such things as CSV files are not really concerned with that. To merge the text-parsing tag, you would have to show that the tag has no real value as a separate tag. – Robert Harvey Aug 25 '12 at 17:56
@RobertHarvey: The general reason to propose that for me was the fact that [parsing] is used 45 times more often that [text-parsing]! It's meaningless, nobody will follow it, [parsing] itself ca do the same job alone. Nobody will care that we've merged [text-parsing], nobody will even notice that. I'm sure that existence of alone, rarely used [text-parsing] makes no sense, it's not required to exist, it does no job. – abatishchev Aug 25 '12 at 18:08
At least three people (the downvoters) disagree. Hopefully they can weigh in with their reasoning. (hint, hint) – Robert Harvey Aug 25 '12 at 18:10
@RobertHarvey: thank you, I updated my post. – abatishchev Aug 25 '12 at 18:23
The number of times a tag is used doesn't make a tag less helpful. The fact that it doesn't add more meaning make [text-parsing] no better than [parsing] – nhahtdh Aug 25 '12 at 18:31
@nhahtdh: I think in opposite, popular tag is important and helpful, not popular is not. if it were, it would be used more often. but it's not. this affects general term tags, not application or version specific – abatishchev Aug 25 '12 at 18:59

Quite simply, is a superset of . Parsing comes in many different forms.

The fact of the matter is that while you can parse text, you can parse streams of anything, another common form being byte stream parsing (think images, Office documents, etc).

Basically, you can have any data type (not just strings) in a sequence and then have a specific set of rules around how to process that sequence. That is parsing in it's general form.

Applying that to a sequence of strings is text parsing.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .