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+...@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
