Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Special Problem by using the txp:lang-Tag...
Hello
The txp:lang-Tag is a shortcut for a language-description of a website and any value of RFC 1766 is possible. If you have a German page then you can simply use “de” and the only correct position for this tag is:
In XHTML: <html xmlns=“http://www.w3.org/1999/xhtml” xml:lang=“de” lang=“de”>
and in HTML 4.1: <html lang=“de”>
You can test the proper function of it, if you bowse this page by a firefox, click into the text, click the right mouse button to open a menue and then you have to find the point “Proberties”. If you select this command, you will be informed about the language of the page. If you do not use the tag correctly, “properties” will not been shown.
The main problem of Textpattern is to bind this value onto the language of the admin-interface. If I select an English interface, the value will be “en-US”. If I select a German one, the value will be “de”. But in the normal case, this language is independent of the language of an artcle.
Normaly this setting should be binded onto the section-Property. The Section “article” for example should produce a page language of “en” and the section “artikel” a language of “de”.
That’s my opionion of how to solve this problem.
Thanks for reading it
Best regards
Wolfgang
Offline
Re: Special Problem by using the txp:lang-Tag...
Sections are not the only element with content in differing languages, and I doubt that we could reap increased benefits from linking a front end language definition to the section definition instead of the back end language, as long as lang is a valid attribute for almost any XHTML element.
Have a look into MLP for an alternative way to manage multilingual content.
Offline