First, lets see if we can resolve one issue… Does anyone object to using PB as the two letter language code for Portuguese-Brazil?
It would then be the same length as all other current language codes we use. It will not conflict with any languages in the ISO standard. It at least starts with the same letter as official designation (PT-BR) used in later ISO standards and should be easier for the user to find than things like BX or BZ. > On Oct 26, 2025, at 4:59 PM, tom ehlert via Freedos-devel > <[email protected]> wrote: > > Hallo Herr Fritz Mueller via Freedos-devel, > > am Sonntag, 26. Oktober 2025 um 19:22 schrieben Sie: > >> Hi, >> using the language code for FD NLS ( >> https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes >> <https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes> ) will have >> the following consequences with the file ending: >> >> a) Czechia should use "cs" instead of "cz" ( 4 changes, see: >> https://shidel.github.io/fd-nls/report.html >> <https://shidel.github.io/fd-nls/report.html> ) >> b) Denmark should use "da" instead of "dk" (12 changes) >> c) Estonia should use "et" instead of "ee" (3 changes) >> d) Slovenia should use "sl" instead of "si" (2 changes, both .sl already >> exist) >> e) Brazilian should use "whatever you want, as it is not in ISO 639), >> instead of "ptb or ptbr" (12 changes). > > You somehow managed to miss that Germany should use "de" instead of “gr" While some programs like FreeCOM use compiled translations and filenames like “finnish.lng”, most of the program translations stored at FD-NLS translation project[1] use external (or tacked onto the executable) NLS files that use the language code as the file extension. I am not aware of any non-source based NLS files which use GR instead of DE for their German. If there were NLS files which used GR as an extension, those would show up on the FD-NLS Status page[2]. Whether or not we decide to leave some existing two letter language codes as-is or change them to be more inline with the ISO standard, we really should provide a list of those codes and languages. With such a table, it becomes less important to what code is actually used. The end user can simply look them up or be pointed to the table when they cannot find the proper code for their language. > Using the country code would have more problems: > https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes > a) Esperanto "eo" has no country -> no country code (delete???) > [..] While country codes and regions are just as important as language codes, I think that is a separate issue. Jerome [1] https://github.com/shidel/fd-nls <https://github.com/shidel/fd-nls> [2] https://shidel.github.io/fd-nls/ <https://shidel.github.io/fd-nls/>
_______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
