OK, let me answer some issues, then digress a bit and outline the reasoning behind the default listing. I am preemptively sorry for the unusually long post.
rupeeIndian
in the Languages entries for the Southeast Asian scripts: I had thought that was already the case, but apparently we are adding them now. That was what Georg’s question (further above) was about.
Why? A symbol can be (and in fact, many are) listed in multiple places. One good question I see is: does it make sense to add it in the Category > Symbol list, so we do not need to add it everywhere.
That is what it already does. It is primarily a filter. If a currency symbol is in the font, it will be listed there.
Two misunderstandings here. First, rupeeIndian
already IS part of the currency category, like all the other approx 60 currency symbols we have in the glyph info at the moment.
And secondly, you actually cannot get around yen. That is because yen is part of both Win1252 and MacRoman. Not supporting yen
breaks the font in Office software and with almost any keyboard out there. That includes the Hungarian and the ABC India keyboard layouts, so it is required.
IOW it is listed there, so we do not need to repeat it in all the collections, like we list the comma and the colon there, because it is essential for pretty much any keyboard layout out there.
Please understand: this is a weak argument. Because there is nothing that keeps designers from including it in their fonts now already. I accept that what you want to do is a noble endeavour, but that is not the point of the category list.
The real question is: is it necessary to ‘force’ it on all type designers? What is the actual problem if it is missing in fonts? We need to have a very good excuse, and it is clear that ‘we want to encourage you’ really doesn’t cut it. I would actually love to remove things like lozenge
from the listings, but we cannot because a font lacking them will break.
So, the strongest argument for listing it by default is its typeability on a range of keyboards: Gujarati, Kannada, Konkani, the Devanagari keyboards, etc. The chance of someone typing it and triggering a fallback font (or notdef in DTP software) is too high.
The counterargument is that all of these keyboard layouts are specifically Indian. So it may be a better option to add it to all Southeast Asian entries in the Languages section.
The counterargument to the counterargument would be that rupeeIndian
is included on the Mac’s ABC India keyboard (Opt-4) and on Windows 10, you can type it with AltGr-4 on the English (India) keyboard. And, please correct me if I am wrong, I think it is not only plausible, but likely to do a Latin-only font for the Indian market. And a designer doing such a font would have no other way to see if all required bits and pieces are covered or not. The Southeast Asian listings would not help in this case.
Yet another option would be to add a Currency entry for the Languages section, much like we have Emoji and Math now. There it would make sense to strive for completeness, and categorise better. I would especially look forward to a ‘Legacy’ section, where we can park historic ballast like drachma, franc, germanpenny, etc. But that is another story.