These messages are generated by gettext's msgmerge and there is a key
for switching this. I think that these obsolete messages are usually
not needed.

`--previous'
     Keep the previous msgids of translated messages, marked with `#|',
     when adding the fuzzy marker to such messages.

Ain

On Mon, Aug 24, 2009 at 08:55, Dwayne Bailey<dwa...@translate.org.za> wrote:
> Hi All,
>
> On Mon, 2009-08-24 at 10:42 +0800, Aijin Kim wrote:
>> Hi Dick and all,
>>
>> Sophie wrote:
>> > Dick Groskamp wrote:
>> >> Sophie schreef:
>> >>> Hi Dick,
>> >>> As André said, this a bug on Pootle. If you use an external tool to
>> >>> translate, these strings won't appear in the tool, only if you edit
>> >>> the file with an application like gedit or the like,  you will see
>> >>> the .txt file structure.
>> >>> The strings were used on the UI but they have been migrated to
>> >>> cui.po. Why they are kept here? I don't know, may be we could
>> >>> discuss this. Your translation memory should have them any way if
>> >>> you choose to use it.
>> >>
>> >> Thanks SOPHIE,
>> >> I understand but my main point is that it shouldn't be visible in
>> >> Pootle at all.
>> >> That means that it is to be corrected.
>> >
>> > Yes, you're right so this bug has to be reported to the Pootle team.
>>
>> I forwarded this issue to Friedel who is the Pootle developer.
>> Let's wait for his reply if it's a known bug.
>
> Friedel and a number of other Pootle coders have been in Egypt at
> Pootlemania for a code sprint.  He is back so I'm sure he'll chip in
> today if needed.
>
> I've had a quick look at the issue and I'll try summarise then explain
> the issue so that everyone gets an idea of what's going on even if you
> don't care for code!
>
> Here is the bug that I've raised to track this:
> http://bugs.locamotion.org/show_bug.cgi?id=1114
>
>
> Issue
> =====
> These strings are being presented by Pootle because Pootle is seeing
> obsolete messages (marked as #~ in PO files) as untranslated.
>
> There is nothing wrong with the PO files which is why translators who
> are using offline tools are not seeing the issue.
>
>
> Fix
> ===
> Fortunately I don't think the fix will be too hard and it will probably
> be easy to patch the OOo Pootle server.  I'm hopeful that we'll be able
> to have a fix before the end of today.   So you might not need to try
> any of the following workarounds.
>
>
> Workaround
> ==========
> 1) Ignore these messages with no source text until we fix the issue.
> 2) Try work offline by downloading and uploading PO files to Pootle.
> (There have been a few suggestions of possible tools, you can also try
> out Virtaal http://virtaal.org/)
>
>
> Issue in more detail
> ====================
> Pootle uses the Translate Toolkit to do much of its manipulation of PO
> files.  We did a major work in the Translate Toolkit for v1.4 where we
> removed the old KDE style comments and replaced them with proper Gettext
> msgctxt.
>
> The change was important as it meant that we got proper PO files for
> OpenOffice.org and did away with the non-standard KDE comments.  Many PO
> editors didn't understand KDE comments and it could lead to translators
> being confused and translating the KDE comment instead of ignoring them.
>
> It was an invasive change, we knew that, but the benefits were great.
> We tested quite extensively doing roundtrip test but unfortunately it
> seemed the change has impacted our code that tracks the state of a
> string.  I.e. whether a string is translated, fuzzy, untranslated or
> obsolete.  The toolkit is now seeing an obsolete message with msgctxt as
> untranslated when it should be ignoring them completely.
>
> Pootle relies on this state information to find untranslated strings and
> is thus finding them and presenting them to you even though they should
> be ignored.
>
> The bad news is that our battery of unit tests didn't check for this
> condition so it slipped through in our changes.
>
> The fix should be as simple as to ensure that obsolete messages with a
> msgctxt field are not seen as untranslated.
>
> Please feel free to join the bug but I'm sure we'll announce the fix on
> the list.
>
> --
> Dwayne Bailey
> Associate             Research Director        +27 12 460 1095 (w)
> Translate.org.za      ANLoc                    +27 83 443 7114 (c)
>
> Recent blog posts:
> * Google Translate + libtranslate + Virtaal = machine translation in 7 new 
> languages
> http://www.translate.org.za/blogs/dwayne/en/content/google-translate-libtranslate-virtaal-machine-translation-7-new-languages
> * Fixes for Skype Video, Webcam on Fedora
> * libtranslate, TM plugins and Virtaal
>
> Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/
> African Network for Localisation (ANLoc) - http://africanlocalisation.net/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
> For additional commands, e-mail: dev-h...@l10n.openoffice.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org

Reply via email to