Bug 799795 - RFE: Expose strings in brand specific xsl files to translation
RFE: Expose strings in brand specific xsl files to translation
Status: CLOSED WONTFIX
Product: Publican
Classification: Community
Component: publican (Show other bugs)
future
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jeff Fearn
Ruediger Landmann
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-04 23:26 EST by Tim Hildred
Modified: 2012-11-06 20:28 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-06 20:28:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tim Hildred 2012-03-04 23:26:49 EST
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-06 20:28:24 EST
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.