Aivaras Stepukonis wrote:
What must we do simply to change a bad link in a final “.html” file?
Use CMS, edit the html file of your interest (for a native-lang project,
usually located in <.../trunk/content/native-lang/...>), then submit,
commit, stage, and publish.
This does not work for the download pages. The main download page is
generated using JavaScript, so you have no "generated" HTML file since
that is assembled directly in the visitor's browser.
To restrict the conversation to the exact example Jon Peli mentioned,
the string
"OpenOffice 4.1.0 is not available in Basque"
is generated here:
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/download/download.js?view=markup
starting from line 545.
In theory one could check the language there and generate a different
string (with a different order of pieces) for Basque. It is a dangerous
path to follow, but it may work so long as the exceptions are maintainable.
Otherwise (this would be my favorite, but it would break existing pages
if not done properly, so CCing Marcus) we could use the bottom part of
the msg_prop_l10n_XY.js file to store "derived strings" like
var error_not_available = l10n_download_error_aoo_text + VERSION_SEL
+ l10n_download_error_not_available_for_text + "<b>" + RELEASE_LANG[
1 ] + " ("
+ RELEASE_LANG[ 2 ] + ") (" + LANG_SEL + ")</b>.";
so that we have customized versions for those too in the
msg_prop_l10n_XY.js file.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
