Photo Gallery Forums

Since the local information can be got from the Accept-Language parameter of request, can imagevue supports I18N?

For example, if accessing from a en_US system, shows the menu/tip in english and if accessing from a de_DE system, shows the menu/tip in German (Of course, user need to define what to be shown of each language. If not defined, the default local message will be shown)

That's an interesting suggestion. We already have language files for most 'big' languages, and I had to check that flash could in fact read language property from system, which it can:
language (capabilities.language property)

Of course, it means we would need to include a language-selector in the interface - Just because I'm located in China or Norway, doesn't mean I necessarily read those languages.

It would also need some good testing on platforms and operating systems to see if it's consistent.

This is my suggestion:

Currently, imagevue stores the description data in xml. I think it can be updated, such as:

<folder title="pictures1" description="default" description_en="English desc" description_jp="Japanese desc" sort="auto" page="gallery" previewimage="eSIgzTdqulvenT1blx.jpg" fileCount="3" maxThumbWidth="100" maxThumbHeight="100">
<file name="1.jpg" title="River" title_en="English Title" description="River Winter Landscape" description_en="English Title"/>

</folder>

for description and title attribute, additional local can be added.
If current locale from browser(in php, $_SERVER['HTTP_ACCEPT_LANGUAGE'] ) is jp for example, imagevue will try to find description_jp or title_jp attribute. If it exists, then read the data, otherwise, default data will be read.

mjau-mjau wrote:That's an interesting suggestion. We already have language files for most 'big' languages, and I had to check that flash could in fact read language property from system, which it can:
language (capabilities.language property)

Of course, it means we would need to include a language-selector in the interface - Just because I'm located in China or Norway, doesn't mean I necessarily read those languages.

It would also need some good testing on platforms and operating systems to see if it's consistent.

Of course, one thing is to create automatic localization navigation/controls based on the language of the browser ... A far more complex task is to create, load and save descriptions for all languages.

How are you gonna save titles and descriptions for all languages? Filtering attributes when loading description? There are also many other issues not worth mentioning ...