4 ms·
I don't think a NSFW tag belongs in an international standard. "NSFW" is a concept which is limited in scope to a small number of cultures, particularly Englis
by sounddust 17y ago
I don't think a NSFW tag belongs in an international standard. "NSFW" is a concept which is limited in scope to a small number of cultures, particularly English-speaking ones.
I have a site that is community-translated, and the phrase "NSFW" is usually left untranslated. It even sparked several discussions in which people were genuinely confused about why content would be considered "not safe," and why it would be unacceptable at work but acceptable at home, etc..
- j2d2 17y agoAlmost every programming language is written in English.
- Xixi 17y agoI think this is about culture, not language. It's two very different things. Except for all the ASCII/Unicode nightmare, there's not much in a programming language that depends on country/language/culture. Who wants to see something like that : CultureInfo.GetCultures(CultureTypes.Puritan);
- qeorge 17y agoI agree, for the reasons you've stated as well as others. While I do think being able to properly label adult content is important, its better achieved through a meta tag, the class attribute, or in the case of a link, the rel attribute. With the HTML5 and XHTML movements a primary focus has been on eliminating non-semantic tags like div and span. Its a noble pursuit, but I think in the witch-hunt to eliminate general purpose, non-semantic tags a monster has been created. When all elements must be semantic, we need many more to achieve the same goals. Microformats are an example of doing it the right way. Instead of creating new HTML elements to represent each concept, microformats use an existing, general purpose attribute (class) to convey meaning. I'm all for adding new elements when they make sense, but a NSFW element feels like a step backwards.