> that's horrible anyway. Having such fragments in the catalog rather
> than full messages makes it impossible to make good translations
> to languages where the word order should be different.
Thank you. I simply do not have the programming skills to point out the
cause of the problems I was having as a translator.
I think you asked how we could get more people interested in translating.
Well, fragmentation, the method that seems to have been adopted, is not the
way to get rid of replications. I'm sorry, but _compromises_ will have to
be made, i.e., strings will have to rewritten to be more inclusive, but of
course not to the point that they become ambiguous. It's a tightwire to
walk, I know. If no one has the time to do it, then stop mucking with the
strings. There's nothing more discouraging to a translator than to have his
work thrown out the window by someone who isn't even aware of what he's done.
Secondly, as I've mentioned before, the catalogue for Lynx is huge. Since
there is no indication to the translator what the priority, high-incidence
strings are, taking some of the bulk out might encourage some people to give
it a try. I mentioned removing the .lynxrc stuff as a start; I don't think
that is unreasonable. If I were to press the issue, I'd ask for
reconsideration of strings used only once, like the message you get when you
press 'a' for the first time before you have established bookmarks.
Thirdly, there are quite a few strings which really have no need to be
translated because they are as easily understood in English as in any other
language. Again, this would require work on someone's part to list them up
and get a "sorta" consensus. I'm talking about strings like the following:
"Gopher Menu"
"CSO Search Results" |_ probably combinable
" Search Results" |
"CSO index" |_ probably combinable
"This is a searchable index of a CSO database.\n" |
__Henry
