Hallo Fred van Stappen, vous ecrit au Tue, 8 Mar 2022 01:47:35 +0000:
> At the moment, without recompilation, if you add new mo/po file > in /lang directory, in the languages list of /menu/settings/lang, the > new language will appear at end of list with only, as name, > 'Language" and the lang-code. (It is how "createnewlang()" works in > my po2array.pas.) By the way, in ideU source, your "po2array.pas" was > renamed "mo2array.pas", I did not check how you do if the number of > mo files are > than the length of language array.) I completely adopted your evaluation method of language files, so it should really behave the same. But what if there are _fewer_ language files than entries in the constant array? As I see it, the missing languages will be still be presented and could be selected, but nothing will happen and it will look like the selection doesn't work. This, IMHO, requires an explanation for the unsuspecting user. > I agree it is not ideal, maybe the name of the language should be > strored into the po/mo file into a comment and use that as That would be a good way, and indeed, that seems to be the intended way, as such a "comment" field is available already, within the header part of the language file. as part of the "msgstr" string of the very first entry, with the empty "msgid". Unfortunately, it is neither required nor is the content defined, so it may be missing or just repeat - or even contradict - the language item found from the file itself. > language-name. But, indeed, for all the other languages, only the > English name will appear (or need to add the translated name of new > language for each language.) Yes, there is something to think there. Yes, there certainly is... I imagine - no, I not only imagine, I was reported of this by several people - that you could get thoroughly lost in the menues of an appliance that you "unintentionally" set to some strange language, especially if that language even uses a different, unknown to you, character set. How on earth could you manage to set the thing back to your native language if you cannot at all tell what the settings mean? Yes, the locale short names on every entry _will_ be helpful, that's a very good idea, at least if everyone knew them. Hopefully, they do. This issue isn't addressed by the "gettext" people either, they just leave that as a task to be solved by the implementor. That is, by us people trying to provide a viable method fpr internationalisation. One possible way out that I see would be to simply _NOT_ translate the language names at all, but instaed display them all in their OWN language and writing. That way, every user should be able to find the name of his native language in any case, if he manages to find the settings menu at all, and, of course, thumb through it all the way to see all entries. Unfortunately, this requires the system presenting such a setting scheme to support _all_ writing systems, i.e. character sets of all the language files provided. So this would exclude "a few" languages from mseide-msegui for now, until the multi-byte character set issue got solved. But it would allow, say, an italian not knowing any cyrillic to correctly reset a display set to russian so he could use the thing again. So far to my opinionated thoughts about the issue. I'm not at all sure that this can be viable, useful or even appreciable. I't just an imagination. (BTW: I DO archive ALL my posts and those of other posters locally, so there's no need to re-iterate all of them every time again.) -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
