tag:blogger.com,1999:blog-6519198.post2575771857703634329..comments2023-09-13T06:17:41.165-04:00Comments on technoflak: Imagesets in content managementUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6519198.post-5207182103036084792009-02-17T13:14:00.000-05:002009-02-17T13:14:00.000-05:00You're so right and it is incredible that an Ameri...You're so right and it is incredible that an American missed that, for it is common in our country to have websites, especially government websites, that need to be translated into several languages.Alicehttps://www.blogger.com/profile/13910093886404792584noreply@blogger.comtag:blogger.com,1999:blog-6519198.post-77450496902228631872009-02-17T09:15:00.000-05:002009-02-17T09:15:00.000-05:00Hi Alice,Thanks for your comment! You're right - i...Hi Alice,<BR/><BR/>Thanks for your comment! You're right - in a lot of cases there <B>is</B> a different homepage or even an entirely different website for a specific language/locale. The case I'm describing however, is when you have a site that is translated one-to-one into a bunch of different languages. This happens frequently for governmental websites, for example. When every page <B>must</B> be available in two or more languages, then it makes sense to work with language variants and imagesets as I described. The complexity here is in keeping track of whether every page and every image has been translated before it's pushed live. This requirement is not needed when you have different sites for different languages, as you suggest.<BR/><BR/>Obviously, with <A HREF="http://www.onehippo.org/cms7" REL="nofollow">Hippo CMS 7</A>, you can do both :)<BR/><BR/>-- ArjéAnonymousnoreply@blogger.com