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

Hi *,

On Fri, Mar 11, 2016 at 3:03 PM, Sophie <> wrote:
Hi all,

+ Many strings are the same content but with xml tags placed differently

Most fuzzy strings are not because xml tags being placed differently
(where xml tags are different,  it was to fix validation errors), but
most fuzzy strings are due to changes in message context.

for example:
-<paragraph role="bascode" id="par_id3154685" xml-lang="en-US"
l10n="U" oldref="4">ChDrive Text As String</paragraph>
+<paragraph id="par_id3154685" role="bascode" xml-lang="en-US">ChDrive
Text As String</paragraph>

→ the effectivechange is removalof obsolete attributes l10n and
oldref. What matters here  is oldref, as that was part of the po

-#. Hew7C
+#. rkzEY
 #: 03020402.xhp
 msgctxt ""
 msgid "ChDrive Text As String"
 msgstr ""

→ the oldref gets removed from message context, making  it a new
entity/new string. as there's an identical source-string, pootle
reuses the translation and marks it fuzzy.

            + only help files; for pt_BR: 57k new words to review.
            + can compare 5.1 vs. master dbs (JanI)
AI:     + unwind / script changes here (Christian)

So to make it more explicit, is there among our group somebody able to
write a script that will remove fuzzy strings when it's only and xml tag
that has been moved?

See above, it is not about  xml-tags, but changes to message context.
Writing a script to un-fuzzy automatically is possible, but not
entirely trivial.

for each fuzzy string look in translations marked obsolete whether
"same context+one additional line (consisting of only a number)"
exists with exact msgid and translation string, and if so, remove
fuzzy marker.

But as it is time til August, not urgent (doesn't need to be done this
or next week IMHO). Remember: if we wouldn't have master projects, you
wouldn't know about this right now :-))

Just avoid basic/shared (that's where nearly all of this kind of
change was done) and you won't be bothered by those fuzzy ones. Of
course the reason why it was done was because files in basic/shared
had lots of syntax/validation errors, so even after the fuzzy ones are
gone, there will be some strings to translate, but of course much


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.