[publican-list] [Bug 708278] New: RFE: support translation memory

bugzilla at redhat.com bugzilla at redhat.com
Fri May 27 06:31:48 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: RFE: support translation memory

https://bugzilla.redhat.com/show_bug.cgi?id=708278

           Summary: RFE: support translation memory
           Product: Publican
           Version: 2.5
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: publican
        AssignedTo: jfearn at redhat.com
        ReportedBy: r.landmann at redhat.com
         QAContact: rlandman at redhat.com
                CC: mmcallis at redhat.com, publican-list at redhat.com
    Classification: Other
      Story Points: ---


Description of problem:
Right now, translation reuse between different versions of the one document
depends on the version-control mechanism and success and sanity depends largely
on writers' and translators' skill in branching and merging within those
systems. Reusing translations between different projects is only possible
through manual use of the gettext tools and again, comes down to the skill of
the person using them. 

One specific problem is that when documents are not branched carefully, it's
very easy for translations to fall out of step with published books, making it
very difficult to correct the translation of one particular version of a
document without pulling in all the subsequent changes to the document.

I've seen translators using scripts to create and apply gettext compendiums to
get around these problems, but it would be good if Publican itself could
support translation memory to assist reuse, or at the very least, have some way
to "freeze" a version of the original language against which translations are
applied.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the publican-list mailing list