Hello all, My name is Ivan and I am leading an effort on the website-dev list to update the OOo homepage, as well as providing a replacement for the minitabs (these appear at the top-right corner of every page - Search / Change Language / Log In, and they have been a particular accessibility concern).
You can see the design that we are intending to implement at: http://www.patentpending.co.nz/openoffice/test/home.htm Alexandro Colorado of the Spanish NL project contacted me about making language selection easier, as many people who may not speak English still go to openoffice.org, rather than specific NL projects. We hope that this update will address this, by providing a clear link with an icon. As the header is universally applied to all pages in the openoffice.org domain, this will affect all NL project pages... which leads me to my next point: an effort to make localization easier. Unfortunately, CollabNet does not allow us to localize content such as the header, so we have to use JavaScript, as many NL project pages already do. What I would like to propose is a method that any NL project could use to localize the header and translate things such as the positioner ("the free and open productivity suite"), change the link that the OpenOffice.org logo points to, and provide translations of the header functions (search, log in...), as well as providing a custom navigation menu. Basically, it involves 2 .js files: one will be a 'settings' file full of variables that allow NL projects to specify localized strings, navigation links and some other settings. This will be hosted separately by each NL project. The second file will be hosted in one place and will take care of the actual HTML replacement. This will allow us to make changes if necessary without making each NL project do it individually. You can see this concept in action at http://www.patentpending.co.nz/openoffice/test/localized.htm And the two files that make it work can be seen at: http://www.patentpending.co.nz/openoffice/test/locale.js (for NL projects) and http://www.patentpending.co.nz/openoffice/test/localization.js (universal) I will write up a wiki page with full instructions if this is given the go-ahead. It is important to note the biggest limitation of this approach - namely, if JavaScript is turned off, it will not work. What do you think? Do you think this could be of use to your project? Is there any other functionality that you would like to have? Thanks in advance, and sorry for the wordy email :) Ivan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
