<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Better, because editable in OpenCms,
would be to define the Properties "category-title-de",
"category-title-en" for each category.<br>
<br>
To print out the categegory names in the jsp template:<br>
<cms:property name="category-title-${locale}"
file="${yourCategory}"/><br>
(site root needs to be removed from your category if you're using
the _categories-folder in /sites/default/ )<br>
<br>
Works fine when "english-only" category names ("Title"-Property
of the category folder) inside the editor are ok.<br>
<br>
Best,<br>
Tobias<br>
<br>
Am 15.02.2013 15:58, schrieb Rüdiger Kurz:<br>
</div>
<blockquote
cite="mid:http:%2F%2Fpermalink.gmane.org%2Fgmane.comp.cms.opencms.devel%2F37695@localhost.localdomain"
type="cite"><base
href="http://permalink.gmane.org/gmane.comp.cms.opencms.devel/37695">
<title>Re: Locale macro in XSD schema</title>
<base
href="http://permalink.gmane.org/gmane.comp.cms.opencms.devel/37695">
<pre>Hi,
think you are right with your assumption. What you're trying to archive
is localization of categories. I might be wrong, but I think that
localizing categories,tags,facets,... does not make that much sense,
since the 'tags' should be the same for one content. (Categories are
assigned to VFS resources not to the real-localized content).
However, I would try to use the same taxonomy for all languages and then
localize its output at rendering time: The messages.properties could
have entries per category path, using dots instead slashes and then on
JSP side you will replace the slashes pf the category path with dotes
and try then to receive the localized value.
What do you think?
Am 15.02.2013 16:49, schrieb Arturo Martín Lladó:
</pre>
</blockquote>
<br>
</body>
</html>