Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


2012.02.25. 10:02 keltezéssel, Sveinn í Felli írta:
At the LibreOffice conference in Paris, Andras did mention conversion to
gettext as a future possibility;
has there been any feedback from the devs about that ?

 From what I've seen, there are other pending restructurations of the
codebase; another toolkit (GTK?), simplification of icon locations,
skinning, etc.


Caolán also mentioned gettext in his FOSDEM 2012 presentation.
See http://people.redhat.com/caolanm/FOSDEM2012.odp
All slides from FOSDEM 2012 LibreOffice devroom:
http://wiki.documentfoundation.org/Marketing/Events/Fosdem2012

A started to write a program that converted po files to LibreOffice resources. Unfortunately I did not finish it and I have not worked on it since last summer. I also had a gettext patch but it had strange character corruption issues and nodoby could tell why. So it was dropped. I'm sure that Caolán's solution will be more robust. I'm not a programmer after all. :)

Best regards,
Andras


--
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.