> With what OS? Here tested on Linux Debian 9.5 64/32bit, FreeBSD 10 64bit,
> Windows 10 64/32, Rpi ARM 32, for all it is working out-of-the-box.
> Asap, I will release mseide with lang libraries for Russian,
Spanish, Italian, French, German and Dutch.
> (Of course every complete lang is welcome).

Languages will never be completed. Needs to include all 100 or to allow to
compile who needs it.
You can compile only 1 language library and by gui only. It's not needed.
Needs to compile all 100 languages by command line - console mode of
msei18n.

> No gettext support
> Mostly and no more needed, msei18n can do the work with his tools.

Gettext support is using MO files for localization or at least PO files
instead of MO.

> Languages are present just to be present without using except constants
> cause they are directly in code.
> Sorry but this one I do not understand.  Are you talking
about seconsts_xx.pas unit files?

PO files are present, but nothing uses them to have localized gui.

> I prefer hidden vs disabled

You do not respect Martin. He disabled them, but not hided.

> Lazutf8 instead of original Martin's strings.
> Yes it was for you needs, you impose me to make msei18n LC_ALL=C
compatible.
> Now msei18n is fully utf8 compatible, even using LC_ALL=C

It was LC_ALL=C compatible before. Martin did it without Lazarus code.

>What is code upstream?

Main developing of application. You have fork.
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Reply via email to