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


On 5/18/26 15:12, Christian Lohmaier wrote:
Hi Ilmari, *,

On Thu, May 14, 2026 at 11:04 AM Ilmari Lauhakangas
<ilmari.lauhakangas@libreoffice.org> wrote:

In the LibreOffice site .pot file we have currently:

#: data/footer.toml:0 i18n/en-us.toml:0
msgid "Blog"
msgstr ""

I would like to split it, so translators can completely control what is
in the header (maybe they want to link somewhere else than some blog):
[…]
But if I do this, `hugo gettext-extract pot` will always put it back
together again. It didn't help that I added a description to the source.
Is there a way to solve this?

Traditionally gettext uses the message context flag to disambiguate
same/identical strings.
https://www.gnu.org/software/gettext/manual/html_node/Contexts.html

So the po entries should end up with a msgctxt "clarifying context" to
make the string unique - that being said doesn't seem like
hugo-gettext would support that/at least no obvious way..
Yes, I didn't update the thread, but in a patch I commented that I found this and I have delegated adding support to hugo-gettext to a colleague.

Ilmari

--
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/
Privacy Policy: https://www.documentfoundation.org/privacy

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.