The following comment has been added to this issue:
Author: Pedro I. Sanchez
Created: Thu, 26 May 2005 2:26 PM
Body:
Couple of comments:
1. It could work, but for me to test it I would like to get clarification on
two things:
a) How do you enable the <i18n ..> </i18n> thing to work? I just put your code
in my web site and Forrest complains with
skinconf.xml:369:9: Element type "i18n" must be declared.
skinconf.xml:370:50: Element type "token" must be declared.
b) lang="en", what does it mean? If "en" refers to the system language in the
host where the web developer is working (the locale setting) then this doesn't
work. I am developing an all-Spanish web site while working in an all english
host environment.
2. What about the non-tokenized strings like "Search"?
---------------------------------------------------------------------
View this comment:
http://issues.cocoondev.org//browse/FOR-506?page=comments#action_12433
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org//browse/FOR-506
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-506
Summary: Do not hard-code site-visible message strings in skin files
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Forrest
Components:
Skins (general issues)
Versions:
0.7-dev
Assignee:
Reporter: Pedro I. Sanchez
Created: Thu, 26 May 2005 10:49 AM
Updated: Thu, 26 May 2005 2:26 PM
Environment: N/A
Description:
Text strings like "Copyright", "Published", and "Search" are hardcoded into
skin files like site2xhtml.xsl. When creating web sites in languages other than
English the web developer is forced to create local versions of these skin
files with the appropriated translations.
Instead, the DTD for the skinconf.xml should be improved to allow these
translations to be specified in this file. This would make Forrest much easier
to use.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
