Bug 799795 - RFE: Expose strings in brand specific xsl files to translation
Summary: RFE: Expose strings in brand specific xsl files to translation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-05 04:26 UTC by Tim Hildred
Modified: 2012-11-07 01:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-07 01:28:24 UTC
Embargoed:

Attachments (Terms of Use)

Description Tim Hildred 2012-03-05 04:26:49 UTC 
Description of problem:
In order to customize generated text, it is necessary to edit xsl files. For documentation that is translated into many languages, it is necessary to add translated equivalents manually, by liaising with a translator.


Expected results:
Customized, brand-associated xsl files (pdf, html, html-single) should have related PO files, allowing customized generated text to be translated as part of existing translation work flows.
Comment 1 Jeff Fearn 🐞 2012-11-07 01:28:24 UTC 
Translations in XSl are handled by DocBook gentext.
Note You need to log in before you can comment on or make changes to this bug.