Hello,

I have looked at https://techbase.kde.org/Localization but failed to
take too much from their site. Maybe Andy could outline how his system
differs from what po4a would come up with.

The difficulty I see is that the synchronisation between the original
and its translations is not supported. And it may be preferable to have
one translation system for everything.

Also, I am with J.M. that the roles of developers and translators should
possibly be kept apart a bit more. This way, it is easy to tell that a
translator with a quick introduction to git will not unintentionally
change something functional.


Best,
Steffen

On 09.11.21 22:37, J.M. Garcia wrote:
Hi, Andy.
In my opinion, this solution has an drawback: the developer must take the
role of translator. And for several languages. I think it is potentially
dangerous, prone to errors and overload development work.
It's just my opinion.

El mar, 9 nov 2021 a las 20:54, andy pugh (<[email protected]>) escribió:

On Tue, 9 Nov 2021 at 19:21, J.M. Garcia <[email protected]> wrote:

worked last year I found many problems that were difficult to solve.
Example: the documentation of modules generated with halcompile.
I did manage to come up with a partial solution to this, which might
be practical in conjunction with gettext. Or might be totally
superseded by gettext.


https://github.com/LinuxCNC/linuxcnc/blob/andypugh/multilingual_comp/src/hal/components/abs.comp

Is an example of how a .comp file with multilingual documentation could
look.

(note that the language tags are _deliberately_ inconsistently
formatted for testing.)

It might be a better plan to hack halcompile to automatically
gettext-ify the docs, though.

--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers


_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to