I think that the present procedure to update the pages of the national web
sites is using some auxiliary files (.mdtext, .js …) that are processed to
give the final “.html” files to upload into the server.
I am not sure of that, but I think too, that presently we can not correct
directly those final files.
But the files automatically processed in that way sometimes are incorrect for
languages with word order in the sentences not equal to the one used in English.
For instance, in Basque there is no way to translate the item “ is unavailable
for “ because English sentences like “XXX is unavailable for YYY” should be
translated to something like “XXX is unavailable YYY-for”
This is just an example, but similar things occur frequently.
So, if we consider XXX, YYY and ZZZ constant values that must appear in any
language, as long as the .html file generating process is not able to consider
3+1 (constant number +1) language dependent strings to combine with them in the
following way:
lang.dep.str.1 & XXX & lang.dep.str.2 & YYY & lang.dep,str3 & ZZZ &
lang.dep.str4
we can not assure that the automatically generated “.html” Is going to be
correct for all languages.
Actually, even with the (N+1) strings we can not assure the correctness,
because the N constants do not necessarily appear in the same order in all the
languages.
I think that trying to implement an automatic procedure to get final “.html”
files for any language nowadays is too complicated and that, because of that,
it should be possible to make small changes directly on the final “.html”
files.
Not directly the translators, of course; but AOO should accept uploading
directly the corrected final “.html” files sent by them.
Is there, presently, a procedure to make small changes on the final “.html”
files without having to change the auxiliary files and regenerate automatically
those final “.html” files?
What must we do simply to change a bad link in a final “.html” file?
