On Sun, Dec 15, 2013 at 11:09 PM, Muhammad Bashir Al-Noimi <
mbno...@gmail.com> wrote:
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)
>
>
There are some limitations in pure GNU gettext that make it unsuitable (or
at least, inconvenient) for some uses.
Some solutions have been proposed and implemented, the most advanced of all
being "Gettext Generalized" by Caslav Illic:
http://nedohodnik.net/gettextbis/
It's implemented in KDE under the name "Transcript".
Some more information on the limitations of pure GNU gettext can be found
here:
http://laxstrom.name/blag/2013/11/20/review-of-gettext-pot-file-format/
(please note some of the points that blog post makes do not apply to
Gettext Generalized)
A while ago I flirted with the idea of providing a pure .NET implementation
of Gettext Generalized for a project I was working on. Maybe I should
change plans and do it in C++, with a few of the enhancements described in
the above blogpost...
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
------------------------------------------------------------------------------
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
