name=* is for "common name". It should reflect what is normally seen on signboards (not entirely as we still have good practice in naming conventions).
As pointed out by Roger, name prefixes/suffixes (which are part of the default name values) are generally and majorly written in English in PH. We still use Street, Avenue, Highway, Boulevard, Rotonda, Expressway, School, Day Care Center, Health Center, Fire Station, Boundary, etc etc. Since name=* is also the "default name" shown by simple map apps (with no custom rendering), localizing default name values (to FIlipino) can work to our disadvantage during disasters ...if outside-emergency responders would still "Google Search" or need an "online language translator". Take for example (by looking at Japan/Korea/China OSM Map): if a major disaster happen there now, imagine yourselves as an outsider, mapping for, or volunteering to help with the aid of an online map or using a downloadable offline gps map; is it way harder for non-techie individual to engage them (eg. Searching keywords for a particular feature can be a pain -- if you still have to figure out the local dialect and/or character-symbols. It is good that Japan, Korea and alikes are technologically-capable of helping themselves (and won't concern much with the worries of outsiders not understanding them); because having a common local language worked for them -- actually made them stronger as a nation. Localizing default name-labels is an enabler for citizens of these non-English speaking countries - to disseminate and consume information efficiently, without a need for an English translator. But for us who still needs outside help from time to time with technical & financial aids, or attracting tourists. Introducing "language-barrier" on maps becomes a dis-abler. Some Filipino words in fact need translation even to those locals from NCR/Region 4. Like it or not, English is/was already 'forced on us' through our education systems; or by business / social pressure to use technologies with english-default menu system. My impression is, only a few would like to use Filipino menu-system even if it's available on devices... well, I feel the same with a general-purpose maps. Besides, a good number Filipino words are not character-efficient (too long to write) for labeling purposes on maps + or needs a "glossary" to understand. :-) So in terms of naming-convention, I still like to see and use a more universally readable English label (unless a particular local name proves more popular) as OSM's default name. That (English) advantage on naming priorities, has a slight edge over the noble effort for heritage-preservation (language) advocacy using "default maps" as a medium. We can always customize maps at the moment If in the future perhaps, when the Philippines seemingly decides, (trending at least 40%) in use of local dialects on signboards, then we may take it as a sign to reconsider to "localize" the default values for "name="; English will be secondary using name:en=* --- but only until then (that's just my opinion). No issues with adding other local language on name:xx=* _______________________________________________ talk-ph mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-ph
