User talk:ChristTrekker/UnicodeSymbol: Difference between revisions

Content deleted Content added
m you got it. I correct some spellings to clarify.
m My comments: eh, another sp
Line 4:
::Commons.css encoders (those who have to enter and maintain the font set per class) might not be happy with:
::-Non-stable groups, class-names and font-sets. IOW: they [class-names and font-sets] should work well in most/all of the browsers, they should not change too often (any more), and they should not be too many especially if they can be correctly grouped (e.g., when some different groups can share a font set). Also the number of classes can become an issue (it could grow to 100 or 200).
* User input (editors input): use {{cosecode|1=#switch}} to its best: it allows many inputs. Still ambiguous input should give a warning.
* Class naming: I suggest to use all lc and use underscore "_" to suggest a space character. So that would be "unicode_emoticon" not "UnicodeEmoticon". I think the prefix "unicode_" is fine, maybe a shorter one can be found.
::-When it applies, use the proper formal ''[[Unicode block]] name'' or the ''[[Template:ISO_15924_script_codes_and_Unicode|Unicode script name]]'' [http://www.unicode.org/charts/ or via]. These are well defined. If there is such a name, there is no need to introduce a new name.