Op Vr, 2009-02-13 om 02:16 +0900 skryf Nguyen Vu Hung:
> 
> Vietnamese, and probably Japanese, Korean and Chinese as well
> have a big problem in word segmentation that prevents pootle from
> making a good terminology.
> 
> At least in Vietnamese, the feature "suggested terminology" in pootle
> is quite useless. We have to use an external dictionary.

I am sorry that it is not working well for you, and disappointed that
this is the first time we hear about this. What is needed to improve it?
What does segmentation have to do with it? Surely you are translating
from English so the segmentation of the Vietnamese is not required, or
is it? The only feedback I have gotten so far about the terminology
feature is that it is extremely useful. So if your experience is
different, please help us to understand how your expectations are
different and how we can improve it. Perhaps we can help you tune the
terminology list with knowledge of how Pootle makes the suggestions. 

For those interested, the terminology feature is explained here:
http://translate.sourceforge.net/wiki/pootle/terminology_matching

Pootle is developed as an open source project. We really need
contributors to get involved and help us to improve it. Obviously I
can't promise that somebody will fix everything in 10 minutes, but over
the years volunteers to the project have tried to improve things in many
areas for many languages - especially Vietnamese. Most recently a
volunteer from the One Laptop Per Child project contributed some
improvements to the quality checks for Spanish. We would welcome your
contributions.

Last year there was a Google Summer of Code project suggested to improve
the handling of terminology. Perhaps it will be proposed again this year
and you can help to work out how things should work and help to test it.

Thank you for the feedback.

Friedel

--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/language-and-dialect-codes


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to