On Fri, 2020-08-07 at 14:03 +0900, himajin100000 wrote:
Hi,
Does anyone know the background behind why "Source string comment"
gives SVX_NUM_ARABIC for "A, B, C, ..." ?
https://translations.documentfoundation.org/translate/libo_ui-master/svxmessages/en/?offset=&q=+note%3AbBGa7+&sort_by=-priority%2Cposition&checksum=
The source is svx/inc/numberingtype.hrc and the strings are extracted
for translation by ./solenv/bin/hrcex which will run...
xgettext -C --add-comments --keyword=NC_:1c,2 --keyword=NNC_:1c,2,3 --
from-code=UTF-8 --no-wrap svx/inc/numberingtype.hrc -o -
on that .hrc. In the current numberingtypes.hrc the comments are
*after* the string so xgettext has put each comment with the following
translation, not the correct one which is the one before the comment.
It should have appeared as "1, 2, 3, ..." with a Source string comment
of SVX_NUM_ARABIC.
https://gerrit.libreoffice.org/c/core/+/100309 will change the .hrc so
that the next time hrcex is used to extract the translations the
comments will get matched to the correct translation.
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.