Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

[fredvs]

Thanks Roland.

You will need the source of mseide-msegui from mse-org to use msei18n.
There was some problems with the trp (mse TRanslate Project files) for
Windows 10 (but ok with wine).
So was added in each /lang/lang_xx/ of mseide and msei18n a trp for Windows
and a trp for Unix.

So if you want to play with i18n, please use the trp of
mse-org/mseide-mesgui (not the one in previous attachment).

Note also that the trp of mseide is big and can take some time to load.

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] Destiny of Martin's projects

[Roland Chastain]

Hello Fred. Thank you. I test that ASAP.

Best regards.

Roland 

 

Envoyé: lundi 15 avril 2019 à 23:27
De: "Fred van Stappen" 
À: "General list for MSEide+MSEgui" 
Objet: Re: [MSEide-MSEgui-talk] Destiny of Martin's projects



@Roland bis:


 

 

Note that in the attachment the binaries were tested with Windows 10, but not deep.

 

Fre;D

 

 

De : fredvs 
Envoyé : lundi 15 avril 2019 23:21
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

 



Hello Roland.

It is always a pleasure to read your good advices.

In attachment, mseide and msei18n en version Française.

mseide-msei18n.zip
 

Note that for mseide there are still words not translated (asap if I can).
But for msei18n, all is Frenchy.

If you want to try msei18n, maybe begin with
/i18n/lang/lang_fr/msei18n_i18n.trp.

At first load you will have a error message about the macro "Directory of
units and Forms"
and the project-config form will appear.

Just adjust the 3 yellow fields according of your system.

You may play with import/export into po or text file.
The text-with-context is a format for use of Google-translate.
The idea is to associate each word to translate with a other (the path of
the node without delimiters) that Google-translate will not understand.

Once you have done the translation, import that translated text file into
msei18n project.
The not translated word will be used to assign the original node value).

It is in beta test, but it works.

Have fun.

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


___ 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] Destiny of Martin's projects

[Fred van Stappen]

@Roland bis:

Note that in the attachment the binaries were tested with Windows 10, but not 
deep.

Fre;D


De : fredvs 
Envoyé : lundi 15 avril 2019 23:21
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

Hello Roland.

It is always a pleasure to read your good advices.

In attachment, mseide and msei18n en version Française.

mseide-msei18n.zip


Note that for mseide there are still words not translated (asap if I can).
But for msei18n, all is Frenchy.

If you want to try msei18n, maybe begin with
/i18n/lang/lang_fr/msei18n_i18n.trp.

At first load you will have a error message about the macro "Directory of
units and Forms"
and the project-config form will appear.

Just adjust the 3 yellow fields according of your system.

You may play with import/export into po or text file.
The text-with-context is a format for use of Google-translate.
The idea is to associate each word to translate with a other (the path of
the node without delimiters) that Google-translate will not understand.

Once you have done the translation, import that translated text file into
msei18n project.
The not translated word will be used to assign the original node value).

It is in beta test, but it works.

Have fun.

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
___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Destiny of Martin's projects

[fredvs]

Hello Roland.

It is always a pleasure to read your good advices.

In attachment, mseide and msei18n en version Française.

mseide-msei18n.zip
  

Note that for mseide there are still words not translated (asap if I can).
But for msei18n, all is Frenchy.

If you want to try msei18n, maybe begin with
/i18n/lang/lang_fr/msei18n_i18n.trp.

At first load you will have a error message about the macro "Directory of
units and Forms" 
and the project-config form will appear.

Just adjust the 3 yellow fields according of your system.

You may play with import/export into po or text file.
The text-with-context is a format for use of Google-translate.
The idea is to associate each word to translate with a other (the path of
the node without delimiters) that Google-translate will not understand.

Once you have done the translation, import that translated text file into
msei18n project.
The not translated word will be used to assign the original node value).

It is in beta test, but it works.

Have fun.

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