[EMAIL PROTECTED] wrote:
On 1/27/06, Jörn Nettingsmeier <[EMAIL PROTECTED]> wrote:
Jörn Nettingsmeier wrote:
the issue has been solved.
my english resource catalog was called cmsui_en.xml. as it turns out, it
is assumed to be in the file cmsui.xml, even if english is not the
default language of the publication. changing the filename fixed the
problem for me. maybe i'm overlooking some subtleties, but iiuc this
behaviour is counter-intuitive and needs to be changed.
FYI:
You can use cmsui.xml or cmsui_en.xml, but you must be consistent. If
Lenya sees cmsui.xml with the desired language specifier, it will not
look for cmsui_xx.xml for that language. This is documented (poorly?)
at:
http://solprovider.com/lenya/i18nfiles
your docs say, "The default language files "cmsui.xml" will only be used
when the language is specified and there is no language file."
this is definitely not always the case.
i think the problem is that the global file is cmsui.xml, which is
implicitly english, and my publication used cmsui_en.xml.
I prefer the language extension in all filenames.
so do i.
and i wonder whether the i18n catalogues should be moved. right now,
they are in lenya/resources/i18n, which by current usage means that
system properties are being overridden, i.e. the gui translations. this
does not make sense, because i18n fixes for the gui should be fed back
to the trunk anyway. no publication should need to keep their own i18n
resources for system stuff.
since most people use it to i18nize their live websites, it would be
much nicer to have the catalogues in resources/i18n.
what do you think?
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]