Cannot save a translation project with MSEi18n

[rchastain]

Hello Fred and other MSE friends!

I intend to rework my tutorial about using MSEi18n, and to write another one about using MSEi18n for a Lazarus project. I have discovered that MSEi18n supports both MFM and LFM files!

Unfortunately, I encounter some issues. Sometimes, MSEi18n fails to save my translation project. It seems that it tries to save the TRP file with the folder name.

It's weird because I don't remember to have encountered that issue when I wrote my tutorial.

I built msei18n from several versions of MSEgui, and they have all the same issue. Maybe it's me that do something wrong...

It's under Linux.

[fredvs]

Hello Roland.

Yes, I did try with a other user to use MSEi18n. This experience ended bad and I don't really want to delve back into this code which doesn't leave me with good memories. Sorry.

[fredvs]

Note also that Martin was still busy with that MSEi18n project and was not yet terminated.

[fredvs]

MSEi18n is much more than a translating feature. It works like a kaleidoscope and is able to give totally customized application per language (or other classification).

But, imho, for language it is a few "too much", because it will depend of a library that must be compiled and used for each language.

For multi-languages app, I prefer the way that Sieghard and I developed with dynamic loading of po/mo files.

Of course, it is my 0,001 kopek and I absolutely don't want to slow you down in your documentation which is always perfect and welcome.

[rchastain]

Yes, I did try with a other user to use MSEi18n. This experience ended bad and I don't really want to delve back into this code which doesn't leave me with good memories. Sorry.

As you like, dear Fred.

I created a repository where I will try to repair the application.

[fredvs]

Good luck and of course I will try it and help if I can.

In fact I see more MSEi18n like a wonderful tool for commercial application, you can use it as a "pluggin" binary, if the customer take it, only with the "pluggin" all the application can be changed, with new features, languages, extension, etc...

[rchastain]

Good news! It isn't a bug. I had just forgotten one step: providing a name for the data file (when editing the translation project).

[rchastain]

The other issue was that you sometimes (?) get an exception saying that MSEi18n cannot read a MFM file. But in fact it reads it. Martin specified that the exception can be ignored. (Why he didn't fix it, I don't know.)

[rchastain]

So, I go back to my tutorials. I think many people could decide to use MSEi18n once they discover it. It's a simple, light and powerful application (as all what Martin did).

I close the issue.

[rchastain]

The solution had been given by Martin here.

msei18nedit.png

[rchastain]

MSEi18n is much more than a translating feature.

Yes indeed, MSEi18n is more than a translation editor (like Poedit), but it isn't easy to find words to describe what exactly it is.

It does what Lazarus AND Poedit do.

[rchastain]

The other issue was that you sometimes (?) get an exception saying that MSEi18n cannot read a MFM file. But in fact it reads it.

Not always, alas. It sometimes fails to load a MFM file. Even the official i18ndemo doesn't work for me. :(

It seems to work better with LFM files!

Fred, I wonder if this would not be related to the bug where MSEide couldn't read MFM files. Does it remember something to you?

[rchastain]

Fred, I wonder if this would not be related to the bug where MSEide couldn't read MFM files. Does it remember something to you?

I mean this bug.

As an experiment, I would like to compile MSEi18n with FPC 3.0.4, but unfortunately I am unable by any means to install it. I tried FPC OOTB, fpcupdeluxe, a package from Sourceforge, without success. :(

The 3.0.5 package from FPC OOTB compiles, but the binaries generated don't work.

Don't want to bore you with that. I will continue to investigate.

[fredvs]

Hello Roland.

For the bug see my previous post: 39cce61#commitcomment-153174452