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


Hi,

I found out that the information about paths to source code files with the strings to translate is now missing in Pootle. This is a drawback of the (surely necessary) migration to gettext - strings are now stored in messages.po files which does not correspond anymore with the structure of the source code. (In some cases, the path can be derived from file name, e.g. .ui files lives in uiconfig/ui/, but this is not 100%.)

This broke my workflow, as I am used to jump often to the Github history of the file corresponding with a translated string (its URL is created by a JavaScript bookmarklet using data from a current Pootle page). By that, I got very useful overview of the change (e.g. if it is cosmetic or not), I could check related bugzilla reports to see what a new feature should do and where to find it in UI etc.

Does anyone else miss the paths? And would it be possible to give them back, i.e. to save them together with file name when generating .po files?

Best regards,
Stanislav

--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://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.