The request for HTML/XML tags for no translation has been made some
time ago. It does not seem that complicated to me. It would be a
useful facility if you want to design a multilingual website.
Also is it possible to recognize formulae?
- Ian Parker
On Sep 15, 3:58 pm, esdoornblad wrote:
> I see a number of very positive and useful suggestions being offered
> on this Group, but I rarely see any comments by GT staff. There is
> only a small number of comments per day, not exactly overwhelming.
>
> For example, I had a simple question and suggestion regarding words
> that are not translated. It would seem like GT could provide a simple
> answer, and indeed, would wish to incorporate the suggestion. But
> simply no reply.
>
> Permit me to repeat that recommendation, and to offer another straight-
> forward issue that so far have been completely ignored by GT.
> -------------
> Untranslated words.
> When GT is unable to translate a word, it simply inserts the same word
> into the translation. There is no indication that this is not a valid
> translation but simply the original word. It is very difficult to find
> such errors, especially in similar languages such as English <> Dutch.
>
> Since GT knows that it cannot translate the word, it would be easy to
> the flag the translation with something like *gobblygoop* that would
> alert the user to the fact that GT found no suitable translation. In
> other words, use an * or two *s, or something else, to flag
> untranslated words.
> -------------------
>
> "The quick brown fox jumps over the lazy dog." (a standard test
> sentence) is not translated AT ALL from English into Dutch. I
> submitted the correct translation a couple of times in the last year,
> but no improvement in GT.
>
> Are the submitted improvements ever used?
