Re: [MSEide-MSEgui-talk] msei18n vs PO files
> I'm not sure what you want to say with that - did it fail to compile for > you, did it fail to start, were you unable to get it to work, or something > else? https://github.com/mse-org/mseide-msegui/issues/1#issuecomment-468327170 Fre;D ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] msei18n vs PO files
> I mean to remember that it was neccessary to convert the project's .mfm > files to a different format, and indeed I found files with a .trd extension > holding the conversion parameters, along with the msei18n .trp project > files. It seems to me too that some conversions are needed. But it seems too that after the patches of Glixx it does not need such conversion (or I missed something). I did not change my locale (not out-of-the-box in Debian 9.5) to test if localization i working with MSEide + i18n. But it seems that for Glixx who has Russian locale it is working. But maybe there is something that he does after compiling that I miss. Fre;D De : Sieghard Envoyé : vendredi 1 mars 2019 22:34 À : mseide-msegui-talk@lists.sourceforge.net Objet : Re: [MSEide-MSEgui-talk] msei18n vs PO files Sehr geehrter Herr fredvs, Sie schrieben am Thu, 28 Feb 2019 14:28:26 -0700 (MST): [msei18n] > My biggest problem is that I cannot make run the msei18n demo so difficult > to measure the feature. I'm not sure what you want to say with that - did it fail to compile for you, did it fail to start, were you unable to get it to work, or something else? I could compile it without problem with the latest released IDE (4.6.2) and fpc 3.0.2 x64, although I used the 32bit precompiled IDE. The resulting program did run, although it didn't find some files I had used previously, because in the meantime I had done some reorganisation on my machine... My problem at this place is that I just cannot really remember what exactly had to be done and prepared to create a working project for msei18n. I mean to remember that it was neccessary to convert the project's .mfm files to a different format, and indeed I found files with a .trd extension holding the conversion parameters, along with the msei18n .trp project files. It' s just too long since I did this project, must be more than 5 years by now, and I didn't even have to do much work on it since. So I will need some time to find out again how this is to be used and I can provide a working example. Sorry for that. -- -- (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 mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] msei18n vs PO files
Hello Sieghard. > I'm not sure what you want to say with that - did it fail to compile for > you, did it fail to start, were you unable to get it to work, or something > else? I said that the /msegui/apps/i18ndemo/i18ndemo.prj is not working so I cannot evalute mse-i18n. Fortunately Glixx gave patches to make MSEide i18n enabled (localization). @Glixx, one more time: big wow. https://github.com/mse-org/mseide-msegui/commit/d08b31fd4f4212ab42e8cdb6aabdc62117e0cce7 Here infos of the fixes: https://github.com/mse-org/mseide-msegui/issues/1 So, yes MSEi18n is working and great. Glixx proposes to also enable PO files for MSEgui (like fpGUI does), so we may have to choose or using MSEi18n or PO files. If you want to compile/test MSEide with i18n enabled, please check the option "-dmse_i18n" in project-option/make-option in mseide.prj. > I can provide a working example. Sorry for that. No problem, the working 18n example is now MSEide (and it s a perfect example!). And for the demo 18ndemo.prj I will try to fix it asap. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Re: [MSEide-MSEgui-talk] msei18n vs PO files
Sehr geehrter Herr fredvs, Sie schrieben am Thu, 28 Feb 2019 14:28:26 -0700 (MST): [msei18n] > My biggest problem is that I cannot make run the msei18n demo so difficult > to measure the feature. I'm not sure what you want to say with that - did it fail to compile for you, did it fail to start, were you unable to get it to work, or something else? I could compile it without problem with the latest released IDE (4.6.2) and fpc 3.0.2 x64, although I used the 32bit precompiled IDE. The resulting program did run, although it didn't find some files I had used previously, because in the meantime I had done some reorganisation on my machine... My problem at this place is that I just cannot really remember what exactly had to be done and prepared to create a working project for msei18n. I mean to remember that it was neccessary to convert the project's .mfm files to a different format, and indeed I found files with a .trd extension holding the conversion parameters, along with the msei18n .trp project files. It' s just too long since I did this project, must be more than 5 years by now, and I didn't even have to do much work on it since. So I will need some time to find out again how this is to be used and I can provide a working example. Sorry for that. -- -- (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 mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
