On Mon, Dec 16, 2013 at 2:09 AM, Muhammad Bashir Al-Noimi <mbno...@gmail.com> wrote: > On 12/15/2013 02:26 AM, Nagaev Boris wrote: >> I think, it would be great to integrate Wt XML translation format with >> transifex and crowdin.net - they are better suited for not advanced >> users (not programmers). > In older discussion I wondered about the reason of not using Qt > translation or Gettext protocols for translation process but > unfortunately I didn't receive any convince response. > > Technically using gettext (for example) is very vital for localizing any > open source project because it decrease localizing process for 90% of > the current used way (I think it's similar to .properties in Java) I think, we need following things: 1. Option to use gettext-style translation system for Wt. I mean, English version is used as a key. Not too large-scale change, I think. 2. Tool to extract translations to XML. 3. Converter XML <-> PO. Probably to/from Qt translations as well. 4. Integration with transifex and/or crowdin. This is not simple uploading PO or other files. At least crowdin provides wysiwyg editor, like Qt Linguist. I think, Wt is capable to generate all HTML which is needed for this. Then translating Wt applications by anybody will be as simple as possible.
Regards, Boris Nagaev ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
