>> >> The challenge in trying to >> >> leverage this without extensive reference to context is that many short >> >> strings can have ambiguous meanings >> >> >> >> Left (remaining) or Left (direction), Clear (erase) or Clear (transparent) >> >> and so on. >> > >> > Yes, I also found this in the short frequency words lists I created for >> > the Decathlon (see my mail to Asiri). >> > >> > I think the most practical solution would be to create such a list >> > anyway, and then try to find as many different meanings for each word, >> > and include all those meanings in the list. You'll end up with meanings >> > that are not common, but at least you'll cover all the meanings that are >> > important. >> > >> > For example, if the list contains "file", you might put both computer >> > file and nail file in the word list, even though nail file is very >> > unlikely to occur in a software translation. In this way, translators >> > (who must use these lists intelligently) can easily spot the appropriate >> > meaning. >> >> I think the terminology should be created and maintained via a >> specific program for this task. Using a program for seeing the words >> that are more used could be useful until certain point, because a very >> common word is "the", a word that I think doesn't need to be in a >> glossary. > > That's why you have to use stoplists, like poterminology does.
Someday I will read all the Pootle wiki stuff for knowing better the Pootle environment. >> Another thing is that in a good glossary doesn't appear words. A good >> glossary has only concepts as entries, and several entries could have >> the same word (because words could have several meanings). >> >> Sometimes could be a good idea having several glossaries, because you >> don't use the same words in Battle for Wesnoth or in Firefox, for >> example. > > Or maybe groups of terminology that cover common and then domain > specific stuff. Yes, I forgot the common stuff glossary, but the others are specific. >> A good support (or even only support) for glossaries is a great lack >> of a lot of CAT programs. In Lokalize there is some support for this >> http://youonlylivetwice.info/lokalize/lokalize-glossary.htm > > I must say I've been underwhelmed by most glossary solutions. Thanks > for that link the lokalize approach looks interesting. Yes. It could be a good idea that instead of saving the new entries added to the glossary in local, it could connect to a terminology server and add them there. Perhaps is time to specify a kind of protocol that have all the things needed for this things. > More importantly. How did they create that flash presentation! :) I think the important thing is what the presentation shows. Bye, Leandro Regueiro ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
