[
https://issues.apache.org/jira/browse/TS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004160#comment-13004160
]
Alan M. Carroll edited comment on TS-694 at 3/8/11 8:43 PM:
------------------------------------------------------------
That's what the proposed solution does. It's just put on the "AltLangText"
variable. E.g.
AltLangText:l33t altx0s
in the header variable section. This has several advantages:
* The location of the text is determined by the template, not the page editor.
* We don't have to have the magic "LANG" marker.
* We at least get a decent default if the editor forgets.
was (Author: amc):
That's what the proposed solution does. It's just put on the "AltLangText"
variable. E.g.
AltLangText:l33t altx0s
in the header variable section.
> "Alternate Languages" needs to be translated too.
> -------------------------------------------------
>
> Key: TS-694
> URL: https://issues.apache.org/jira/browse/TS-694
> Project: Traffic Server
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.1.7
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Priority: Minor
> Fix For: 2.1.7
>
>
> The "Alternate Languages" links are auto-generated rather than being embedded
> in the source content files. This creates the problem that the phrase
> "Alternate Languages" can't be translated too. The template should be changed
> to have pull the phrase from a variable and default to "Alternate Languages".
> This way it's always there, but translated files can override it in order to
> translate it. It would have to be done for every translated file, but that's
> no worse than the previous system which required it for every file,
> translated or not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
