https://bugs.documentfoundation.org/show_bug.cgi?id=151359
--- Comment #17 from Eike Rathke <[email protected]> --- (In reply to Mark Hung from comment #14) > (In reply to Eike Rathke from comment #13) > > (In reply to Caolán McNamara from comment #11) > > > if we're not using this field for anything, perhaps we can just remove it > > > entirely > > > > The field needs to be present (or we change the DTD), but we could use > > Is there any issue if we change DTD? No issue, we'd just have to mark the element as optional (if anyone actually used the locale.dtd to validate data against, as lined out there and pointed to in https://wiki.documentfoundation.org/LibreOffice_Localization_Guide/How_To_Submit_New_Locale_Data). > As far as I know LibreOffice support adding language by extension, maybe > that might be an issue. Locale data can't be added by extension (afaik, unless you implement a complete css::i18n::XLocaleData5 interface and manage to plug that into the css::i18n::LocaleData2 service somehow so that it switches depending on what locale the interface is being asked for), but even if there was such, having an optional element being present wouldn't harm. > As Caolán mentioned, "short names" in 3166 are different than what > LibreOffice has here in some places. Note that names may also change over time (like even worse country codes can, hence we go only with IANA type region subtag country codes nowadays), they may have been different in the past. > While there is no description about > DefaultName property , maybe it is enough to just update the comment for > CountryID to explicitly express it is not 3166 short name as a way to get > rid of unecessary debate? ? CountryID is *only* ISO 3166-1 alpha-2 country codes, or the IANA type region two letter code equivalent. > > So far I always regarded it as a kind of comment that is preserved by all > > XML processing.. maybe making it optional and just removing it in zh_TW.xml > > would indeed be best. > > Is the statement 'best' based on easiness of implementation? Not only that. It would avoid endless political discussions about what content would be right or wrong. Obviously whatever we put there will be wrong for *someone*. We don't need the element for functionality, it's not shown anywhere in the UI, so let's just get rid of it in this case. -- You are receiving this mail because: You are the assignee for the bug.
