Murray,
you're reading my mind ;-)
I was thinking though about having a link between the localized
versions. This is simply because the page name would have to also
change between language to language, and I'm not sure whether it's
worth the while to dissociate the page URL from the page name, as the
URL needs to be accessible through the localized name as well ("What
do you mean I have to link to TextFormattingRules when the page is
clearly called "Tekstinmuokkaussäännöt?")
Properties cannot be added to properties. But you could use siblings
with same name, or some other tree structure.
/Janne
On 23 Jan 2008, at 11:52, Murray Altheim wrote:
Janne Jalkanen wrote:
Page level localization is not supported. However, the controls
(e.g. "Save", "Edit this page", etc) are localized.
Janne,
Bit of a tangent, but I take it that, given that with our future
JSR-170 storage model, document content will be treated as a Just
Another Property, we therefore tag such properties with a natural
language indicator (ISO 639) and therefore permit content
localization as well?* Would be an interesting challenge...
...I'm trying to find where in JSR-170 we can actually add a
property (e.g., lang) to a property (e.g., content). No luck so
far but I just started looking.
Murray
* or localisation as they write in some countries?
......................................................................
.....
Murray Altheim <murray07 at altheim.com>
=== = =
http://www.altheim.com/murray/
= = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk
= = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
