Gettext-style translations are really really bad, because they use the original text (usually in english) as a translation key, which means they simply can not handle situations where the same english text needs different translations depending on where the text is used. And yes, I have come across that issue once upon a time.
You are right that editing a dialog is annoying, but due to the way win32 resource dialogs work, it's unavoidable. Even if we could have a serpate file for reaching the translations, there's often the situation where certain languages need different layouts, or at least different control sizes, to accomodate for longer / taller text, or RTL. So even if we switched to a different system, that annoyance wouldn't go away.
I do agree that it would be nice to have some nicer tool for translators, but IMO, .po files are not it.
On 14 March 2017 at 23:14, Rafał Harabień rafalh@reactos.org wrote:
In my opinion it's very sensible proposal. I remember changing dialog layout in resources was a big pain because of amount of repeated work for all languages (and error prone). It was demotivating. On the other hand there are free translation platforms making project translation more organized and easier than editing raw resources. WINE is using PO for years and ReactOS IMO should do it as well. Just my two cents...
W dniu 14.03.2017 o 14:31, Ștefan Fulea pisze:
Marți, 14 martie 2017 12:00:02 +0000, Mark Jansen learn0more+ros@gmail.com a scris:
How about a better way to translate ros? For example integrating .po files with our rc files (possibly needs a preprocess step or something tho), Or creating a resource editor that allows multiple files to be edited at once?
Please don't push for .po resources, for these are not better. As for improving the process, I doubt it'd repay the investment. After the initial translation effort, the further maintenance requires very little.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev