>>>>>> 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
