Closed Bug 184189 Opened 23 years ago Closed 19 years ago

Marking of changed strings

Categories

(Mozilla Localizations Graveyard :: MozillaTranslator, enhancement)

x86
All
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gp, Assigned: rpmdisguise-nave)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; da-DK; rv:1.2) Gecko/20021202 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; da-DK; rv:1.2) Gecko/20021202 Dear Henrik. It is very difficult to identify changed strings in MT. When you update your product you get a list off changed strings, but if this list contains let's say 500 strings and it is late at night it is impossible to translate them right away, and then the information is lost. I would like a feature of MT that marks the changed strings as FUZZY when the English text changes. It should also compare the new and old English text when I make a "import translation". Hope you will consider it. Gunner Poulsen. Danish translator. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Status: UNCONFIRMED → NEW
Ever confirmed: true
What about appending a special char at the end of the translated text, or in the comment field (as long as elusive bugs with search on this field are resolved)?
I'd like a save/load current view function for continues working. as bug <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=197286"> 197286</a> mentioned. It also mets your requirements.
Actually that solution won't solve the problem here. Adding a special char allows for sharing of translation works among different team members and makes it easier for evryone in the team to overview other peoples' work for QA. The "save state" option suggested as is works just for the single user setup.
Reassigning to me.
Assignee: henrik → rpmdisguise-otros
This is desirable, it's true, and while a load/save list is not implemented, an acceptable (for me) workaround can be used. Accepting bug.
Status: NEW → ASSIGNED
Every time a string is changed or added, its "Fuzzy" flag is set. Every time a string is reviewed through Edit Phrase Dialog (whether it's modified or not), its "Fuzzy" flag is unset. "Fuzzy" flag can be also set/unset in any chrome or list view selecting strings and pressing the appropiate button, and all fuzzy flags can be unset at once through Edit -> Clear ALL Fuzzy flags. "Fuzzy" flag is persisted in Glossary.zip. With all above preconditions met, the procedure working for me is this: - Clean up the translation, so you don't have fuzzy flags set on non-fuzzy strings. - Run either File -> Update product or Import -> CVS Import Directory. New and updated strings will be marked as Fuzzy (removed strings are gone, obviously). - As long as you don't unset Fuzzy flag explicitily or by reviewing the string through Edit Phrase Dialog, the string will be marked as Fuzzy, even if you save the glossary, exit the program and reopen it later. I'll keep this bug open for a while to let people complaint, suggest or confirm if it works for them.
*** Bug 197286 has been marked as a duplicate of this bug. ***
Nobody has pronounced himself against the implemented solution, so I'm closing this bug.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: Mozilla Localizations → Mozilla Localizations Graveyard
You need to log in before you can comment on or make changes to this bug.