forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sjur N. Moshagen (JIRA)" <>
Subject [jira] Commented: (FOR-580) Default language in
Date Thu, 21 Jul 2005 07:50:47 GMT
    [ ] 

Sjur N. Moshagen commented on FOR-580:

No strong opinions on which of the two alternatives would be better, but here are some thoughts:

1. When building a language override menu (cf. FOR-579), it is desireable to include the default/fallback
document as well in the list of available languages. If the language/locale isn't part of
the filename, one would have to look inside the document to get that info (assuming it is
encoded using something like @xml:lang).

2. In our project ( the "default" (i.e. unmarked in the sense of Juan
Jose Pablos) language varies with the content: for documents intented for the general audience,
it is 'se', whereas for technical documentation it is 'en' (the technical documentation is
mostly monolingual). Thus, one can't assume that a file without a language extension allways
implies one and the same language. At least in our case it is a one-to-many relationship (the
fact that it is so is based on language politics, documented at
This fact seems to me to complicate the construction of a language override menu, cf 1) above.

3. It doesn't make much sense to add a language extension to files when there is only one

> Default language in
> --------------------------------------
>          Key: FOR-580
>          URL:
>      Project: Forrest
>         Type: New Feature
>   Components: Core operations
>     Versions: 0.8-dev
>     Reporter: Sjur N. Moshagen
>     Assignee: Juan Jose Pablos

> When developing a multilingual site, it would be beneficial if the default/fallback language
could be configured from This would imply that, given 'no' as fallback,
one of the following two scenarios would be true:
> 1)
> files: index.xml, index_es.xml, index_en.xml
> Requests for both index.html and index_no.html would generate the returned page from
> 2)
> files: index_no.xml, index_es.xml, index_en.xml
> Requests for both index.html and index_no.html would generate the returned page from
> In both cases the end result would be that there would be no need to maintain more than
one file for the fallback language.
> I would prefer the second alternative just for the sake of symmetry and equality of languages.
It has the additional benefit of making it very easy to change the default/fallback language
- just change the setting. The second alternative would also make it easier
to create a language override menu, as all the available languages/locales would be encoded
explicitly in the file name.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message