Re: [translate-pootle] Frequncy list
On Thu, Jan 29, 2009 at 10:00 AM, Leandro Regueiro wrote: > I have interest in what you are doing. Maybe it will be a good idea to > join with other developers, there are a lot of people interested in > that glossary servers stuff... I thought that's what I was doing here! >> Summmary. TBX is what you want: Lokalize, Virtaal and other commercial >> apps support it. OK, cool. Good to know. -- Steve Herrick Maybe we can eventually make language a complete impediment to understanding. - Hobbes the tiger -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Thu, 2009-01-29 at 17:00 +0100, Leandro Regueiro wrote: > > TBX - TermBase eXhange - designed to store terminology/glossaries. > > TMX - Translation Memory eXhange - designed to store translation > > memories i.e. previous translations. > > > > Its not really an issue of pro's or con's they're different formats for > > different needs. > > > > At its simplest a glossary is a two column spreadsheet. TBX adds a > > number of features including the ability to include definitions, parts > > of speech, etc. Most you probably won't use but it makes your data > > available and extensible. > > You don't need them in the translation, but yes in the discussion of the > terms. > > > > TMX allows sharing of previous translations between applications. It > > will do things like abstract placeables, something glossaries will never > > do. Its designed to have lists of source and target language segments. > > TMX is like a enhaced po compendium. Some useful references: http://translate.sourceforge.net/wiki/toolkit/tmx > > Summmary. TBX is what you want: Lokalize, Virtaal and other commercial > > apps support it. > > if you want to use it for glossaries. And it is also a ISO standard. And for TBX: http://translate.sourceforge.net/wiki/toolkit/tbx -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * xclip - where have you been all of my life! http://www.translate.org.za/blogs/dwayne/en/content/xclip-where-have-you-been-all-my-life * Virtaal on Fedora * Translate Toolkit on Fedora. Status of Virtaal and Pootle Stop Digital Apartheid! - http://www.digitalapartheid.com Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
>>> I would really recommend that you look at TBX as a starting point. It >>> probably contains more then needed but if you can get your data to fit >>> in that it has a number of benefits. >> >> I've created my own application with a server-side glossary (8000 >> entries and growing steadily). My next step will be to develop input >> and output to standard file formats, to make my system interoperable >> with others, like Pootle. With that in mind, can someone explain in >> small words what the difference is between TBX and TMX, and what the >> pros and cons of each are? I have interest in what you are doing. Maybe it will be a good idea to join with other developers, there are a lot of people interested in that glossary servers stuff... > TBX - TermBase eXhange - designed to store terminology/glossaries. > TMX - Translation Memory eXhange - designed to store translation > memories i.e. previous translations. > > Its not really an issue of pro's or con's they're different formats for > different needs. > > At its simplest a glossary is a two column spreadsheet. TBX adds a > number of features including the ability to include definitions, parts > of speech, etc. Most you probably won't use but it makes your data > available and extensible. You don't need them in the translation, but yes in the discussion of the terms. > TMX allows sharing of previous translations between applications. It > will do things like abstract placeables, something glossaries will never > do. Its designed to have lists of source and target language segments. TMX is like a enhaced po compendium. > Summmary. TBX is what you want: Lokalize, Virtaal and other commercial > apps support it. if you want to use it for glossaries. And it is also a ISO standard. 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Mon, 2009-01-26 at 12:43 -0600, Steve Herrick wrote: > On Fri, Jan 23, 2009 at 4:15 AM, Dwayne Bailey > wrote: > > > I would really recommend that you look at TBX as a starting point. It > > probably contains more then needed but if you can get your data to fit > > in that it has a number of benefits. > > I've created my own application with a server-side glossary (8000 > entries and growing steadily). My next step will be to develop input > and output to standard file formats, to make my system interoperable > with others, like Pootle. With that in mind, can someone explain in > small words what the difference is between TBX and TMX, and what the > pros and cons of each are? Any more info on your applications? TBX - TermBase eXhange - designed to store terminology/glossaries. TMX - Translation Memory eXhange - designed to store translation memories i.e. previous translations. Its not really an issue of pro's or con's they're different formats for different needs. At its simplest a glossary is a two column spreadsheet. TBX adds a number of features including the ability to include definitions, parts of speech, etc. Most you probably won't use but it makes your data available and extensible. TMX allows sharing of previous translations between applications. It will do things like abstract placeables, something glossaries will never do. Its designed to have lists of source and target language segments. Summmary. TBX is what you want: Lokalize, Virtaal and other commercial apps support it. -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * xclip - where have you been all of my life! http://www.translate.org.za/blogs/dwayne/en/content/xclip-where-have-you-been-all-my-life * Virtaal on Fedora * Translate Toolkit on Fedora. Status of Virtaal and Pootle Stop Digital Apartheid! - http://www.digitalapartheid.com Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Fri, Jan 23, 2009 at 4:15 AM, Dwayne Bailey wrote: > I would really recommend that you look at TBX as a starting point. It > probably contains more then needed but if you can get your data to fit > in that it has a number of benefits. I've created my own application with a server-side glossary (8000 entries and growing steadily). My next step will be to develop input and output to standard file formats, to make my system interoperable with others, like Pootle. With that in mind, can someone explain in small words what the difference is between TBX and TMX, and what the pros and cons of each are? -- Steve Herrick Maybe we can eventually make language a complete impediment to understanding. - Hobbes the tiger -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
>> 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. >>> >>> I think before that its probably best to think of the type of data that >>> is needed and exchanged. >>> >>> My thoughts would be: >>> request_term(term) -> (term, disambiguation, definition, translation, >>> translated_definition)*N >> >> Um, this is difficult to say if we don't have defined the structure of >> the glossary. In Trasno Project we are trying to synthesize what has >> our actual glossary (maintained by hand on a wiki) to make a >> specification for our new glossary and find a system that allow us to >> maintain the glossaries and interchange them in several formats, and >> in several ways with several CAT programs. > > I would really recommend that you look at TBX as a starting point. It > probably contains more then needed but if you can get your data to fit > in that it has a number of benefits. > > 1) TBX is a file and standard so anyone implementing that can use the > data. Translate Toolkit does some TBX support already. > 2) Let that influence how you think of the queries that can be made, > since the web side is less constrained to the format chosen. First we look at our current glossary to see what we really need (we have things in our actual glossary that could be removed or multiple things that really are the same), then we will see how TBX represents that things, for finally having a structure that could be used via TBX. 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Thu, 2009-01-22 at 15:26 +0100, Leandro Regueiro wrote: > On Thu, Jan 22, 2009 at 2:57 PM, Dwayne Bailey > wrote: > > On Thu, 2009-01-22 at 12:38 +0100, Leandro Regueiro wrote: > > > > > > > >> >> 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. > > > > I think before that its probably best to think of the type of data that > > is needed and exchanged. > > > > My thoughts would be: > > request_term(term) -> (term, disambiguation, definition, translation, > > translated_definition)*N > > Um, this is difficult to say if we don't have defined the structure of > the glossary. In Trasno Project we are trying to synthesize what has > our actual glossary (maintained by hand on a wiki) to make a > specification for our new glossary and find a system that allow us to > maintain the glossaries and interchange them in several formats, and > in several ways with several CAT programs. I would really recommend that you look at TBX as a starting point. It probably contains more then needed but if you can get your data to fit in that it has a number of benefits. 1) TBX is a file and standard so anyone implementing that can use the data. Translate Toolkit does some TBX support already. 2) Let that influence how you think of the queries that can be made, since the web side is less constrained to the format chosen. > > > >> > More importantly. How did they create that flash presentation! > >> > >> :) I think the important thing is what the presentation shows. > > > > Not if you want to make some of your own presentations like that. > > Then contact Shaforostoff http://youonlylivetwice.info/ > > 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 > Translate-pootle@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/translate-pootle -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * xclip - where have you been all of my life! http://www.translate.org.za/blogs/dwayne/en/content/xclip-where-have-you-been-all-my-life * Virtaal on Fedora * Translate Toolkit on Fedora. Status of Virtaal and Pootle Stop Digital Apartheid! - http://www.digitalapartheid.com Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Thu, Jan 22, 2009 at 2:57 PM, Dwayne Bailey wrote: > On Thu, 2009-01-22 at 12:38 +0100, Leandro Regueiro wrote: > > > >> >> 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. > > I think before that its probably best to think of the type of data that > is needed and exchanged. > > My thoughts would be: > request_term(term) -> (term, disambiguation, definition, translation, > translated_definition)*N Um, this is difficult to say if we don't have defined the structure of the glossary. In Trasno Project we are trying to synthesize what has our actual glossary (maintained by hand on a wiki) to make a specification for our new glossary and find a system that allow us to maintain the glossaries and interchange them in several formats, and in several ways with several CAT programs. >> > More importantly. How did they create that flash presentation! >> >> :) I think the important thing is what the presentation shows. > > Not if you want to make some of your own presentations like that. Then contact Shaforostoff http://youonlylivetwice.info/ 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Thu, 2009-01-22 at 12:38 +0100, Leandro Regueiro wrote: > >> 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. I think before that its probably best to think of the type of data that is needed and exchanged. My thoughts would be: request_term(term) -> (term, disambiguation, definition, translation, translated_definition)*N > > More importantly. How did they create that flash presentation! > > :) I think the important thing is what the presentation shows. Not if you want to make some of your own presentations like that. -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * xclip - where have you been all of my life! http://www.translate.org.za/blogs/dwayne/en/content/xclip-where-have-you-been-all-my-life * Virtaal on Fedora * Translate Toolkit on Fedora. Status of Virtaal and Pootle Stop Digital Apartheid! - http://www.digitalapartheid.com Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
>> >> 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Wed, 2009-01-21 at 12:23 +0100, Leandro Regueiro wrote: > >> 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. > 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. > 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. More importantly. How did they create that flash presentation! -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * xclip - where have you been all of my life! http://www.translate.org.za/blogs/dwayne/en/content/xclip-where-have-you-been-all-my-life * Virtaal on Fedora * Translate Toolkit on Fedora. Status of Virtaal and Pootle Stop Digital Apartheid! - http://www.digitalapartheid.com Firefox web browser in Afrikaans - http://af.www.mozilla.com/af/ African Network for Localisation (ANLoc) - http://africanlocalisation.net/ -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
>> 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. 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. 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 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
G'day Chris > 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. Samuel -- Samuel Murray sam...@translate.org.za Decathlon, for volunteer opensource translations http://translate.sourceforge.net/wiki/decathlon/ -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
G'day Asiri > Dear All,If their any possibilities to obtain most frequent used 100 UIs > (User Interface) in the software? > If their any place to download or collect that resources? Here is one: http://pootle.locamotion.org/projects/terminology/ ...but I'm not sure what the history of that list is. Also, on the Locamotion server, in the Decathlon translation project, I created frequency word lists for each of the projects. See for example: http://translate.sourceforge.net/wiki/decathlon/wxdfast ...and click the link for "glossary for Pootle" (5th link from the top) The way I created the above lists, is described here: http://translate.sourceforge.net/wiki/guide/clunky_glossary_creation > My Objective is collecting above resources, because when localizing SW we > usually we do same strings again and again. That is a good idea, but IMO a better idea would be to create such lists for broad categories of software instead. Words that are common in graphical software may not be common in communication software, for example. Samuel -- Samuel Murray sam...@translate.org.za Decathlon, for volunteer opensource translations http://translate.sourceforge.net/wiki/decathlon/ -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Tue, Jan 20, 2009 at 12:03 AM, Asiri Udara wrote: > Dear All,If their any possibilities to obtain most frequent used 100 UIs > (User Interface) in the software? > If their any place to download or collect that resources? > > My Objective is collecting above resources, because when localizing SW we > usually we do same strings again and again. So collecting such as data: I > hope to make a pre translated database which anyone can reuse and > distribute > . So that will help to merge with other data bases easily. > You ask "any possibilities to obtain most frequent used 100 UIs (User Interface) in the software?" The question is which software? I am interested in ways to improve standardization of internationalization (I18n) practices by use of common UI strings with similar contexts within the One Laptop per Child project's many small collections of UI strings for the Sugar software and activities (small applications). Sugar represents an interesting case as Sugar software design practices emphasize a heavily graphical interface with fairly minimal Ui strings and so there are many one word UI strings (e.g. Save, Open, etc.). 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. This means that while having translation memory available to make suggestions (as can be accomplished by using a terminology project in Pootle, you cannot eliminate the need for a skilled human translator in providing an thoughtful interpretation (in context), although you can certainly reduce the number of times certain strings need to be re-typed. http://en.wikipedia.org/wiki/Translation_memory See for instance OLPC Thai terminology project: https://dev.laptop.org/translate/th/terminology/ The tools described on these pages maybe of interest: Within Translate toolkit: http://translate.sourceforge.net/wiki/toolkit/pocompendium http://translate.sourceforge.net/wiki/toolkit/poterminology Within Pootle: http://translate.sourceforge.net/wiki/pootle/updatetm http://translate.sourceforge.net/wiki/pootle/terminology_matching cjl -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Frequncy list
On Tue, Jan 20, 2009 at 10:33 AM, Asiri Udara wrote: > Dear All,If their any possibilities to obtain most frequent used 100 UIs > (User Interface) in the software? > If their any place to download or collect that resources? > > My Objective is collecting above resources, because when localizing SW we > usually we do same strings again and again. So collecting such as data: I > hope to make a pre translated database which anyone can reuse and distribute > . So that will help to merge with other data bases easily. Are you looking at commonality between UI or, common strings ? If the latter, then I guess poterminology is what you would be looking at. -- http://www.gutenberg.net - Fine literature digitally re-published http://www.plos.org - Public Library of Science http://www.creativecommons.org - Flexible copyright for creative work -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Frequncy list
Dear All,If their any possibilities to obtain most frequent used 100 UIs (User Interface) in the software? If their any place to download or collect that resources? My Objective is collecting above resources, because when localizing SW we usually we do same strings again and again. So collecting such as data: I hope to make a pre translated database which anyone can reuse and distribute . So that will help to merge with other data bases easily. Thank you Best regards Asiri -- 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 Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
