Template talk:Latinx

From Wikipedia, the free encyclopedia

Is this really necessary—can't these fonts be rolled into the list for {{Unicode}}?. Shouldn't this be capitalized LatinX, to match the class name? Wouldn't the name {{LatinB}} better describe its function?

Not to criticize, but it's best to consider all the options before a new template shows up in hundreds of articles. —Michael Z. 2006-05-06 19:25 Z

I'm currently only using it to replace <font face="Microsoft Sans Unicode"> hacks. I have renamed the CSS class. —Ruud 22:58, 7 May 2006 (UTC)

Unfortunately it is nessacery, While IE will skip over fonts it doesn't have it won't skip over fonts that exist but don't have the needed character. {{unicode}} is a jack of all trades containing many fonts that cover most but not all of the BMP (non-bmp characters are only supported by IE with client side reconfiguration anyway). Plugwash 02:17, 28 May 2006 (UTC)

Won't it still be redundant very soon? I mean, how long can it take to fix an MSIE bug? ... oh, I see your point. Nevertheless, it would be more elegant to solve it via content-related templates, not encoding range oriented ones, such as having, say, {{lang|oe|...}} to encode Old English favour fonts that have the full inventory needed by Old English, etc. As it is, having yet another template to work around browser-specific deficiencies is rather annoying. dab (ᛏ) 21:39, 14 August 2006 (UTC)