[Webcom] Portal urls of translated pages

[Jorge Gaspar Sanz Salinas]

Dave Patton escribió:
> Jorge Gaspar Sanz Salinas wrote:
> 
>> My proposal is to add at the end of the url the ISO code for the
>> language, for example:
>>
>> the about page is:
>> http://www.osgeo.org/content/foundation/about.html
>>
>> and the translated ones should be:
>> http://www.osgeo.org/content/foundation/about_ES.html
>> http://www.osgeo.org/content/foundation/about_IT.html
>> ...
> 
> URIs don't have to match the on-disk directory structure,
> so in that sense, it doesn't matter if the "about pages"
> all reside in the same directory, or in directories that
> are organized by ISO language code. However, if there isn't
> a direct one-to-one correspondence between the URI and the
> page's location, would webserver rewrite rules be made any
> easier with a different system than that proposed above?

When one is translating one page is very common to see that OSGeo pages 
links to other pages through a relative path, so, if we place translated 
pages in the same "virtual" path, links will not need to be updated and 
everything will work fine.

I think we need an approach that makes translating less annoying, prone 
to errors and easier in general.

Another issue, would be interesting to have a *site map* for the OSGeo 
portal. I think there are a lot of information that cannot be reached 
from the main page as for example Incubator pages. A site map is a very 
common tool that more or less everyone expects a big portal should have, 
isn't? For example, a very nice Drupal site is spreadfirefox.com and 
their site map is automatically generated by the drupal module:

http://www.spreadfirefox.com/sitemap

Regards
-- 
Jorge Gaspar Sanz Salinas
Ingeniero en Geodesia y Cartografía
correo: jsanz [en] geomaticblog [punto] net
web:    http://www.geomaticblog.net