> It is not always just 2 letters. For example, Portuguese is PT and Brazilian > Portuguese is PTBR.
Two thoughts this brings up. One is that we are not following the ISO standard. Perhaps not a big deal, but that means we are on our own and will definitely need to document everything to avoid confusion and "maverick programmers". The other thought is that this is going to create problems with 8.3 file names where the language abbreviation must fit into the three letter file extension. This, I think, implies that LFNs are _required_ whenever we support multiple languages? I also see that some of the existing language files have file extensions like .FR.UTF-8, which at least seems to imply the use of both LFNs and UniCode which are both outside the realm of "regular" DOS. BTW, one option I was considering is a single .LNG file (or something) with all the translations inside a single file instead of needing a separate file for each language. I don't know if that's a good idea or not -- it's certainly incompatible with KITTEN, at least in its current form. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
