Re: [okapi-devel] Global <gls:glossary> element in XLIFF 2.0?

[Martin Wunderlich <marw@censhare.com>]

OK, thanks a lot, Yves. I will have a look to see, if this was discussed at any stage what the arguments were.

Cheers,

Martin
 


Am Montag, 19. Oktober 2015 16:42:41 UTC+2 schrieb Yves:

I think it used to be allowed at the file level very early on. I wasn’t involved much in the glossary definition, so I’m don’t know the why it was removed from there. A possible cause I can think of is the streaming aspects (reading/writing references separated from their data may be hard to do in a single pass); another is the idea of making the <unit> quite self-contained. But others may know the real reasons.

 

In any case, that is the type of feedback the TC needs to hear.

 

FYI, most of the discussion regarding the glossary module can be found here:

http://markmail.org/search/?q=glossary+at+file+level&q=list%3Aorg.oasis-open.lists.xliff#query:glossary%20at%20file%20level%20list%3Aorg.oasis-open.lists.xliff+page:1+mid:an34a6nikslsmkdn+state:results

 

Cheers,

-yves

 

 

From: okapi...@googlegroups.com [mailto:okapi...@googlegroups.com] On Behalf Of Martin Wunderlich
Sent: Monday, October 19, 2015 6:58 AM
To: okapi-devel <okapi...@googlegroups.com>
Cc: xliff-...@lists.oasis-open.org
Subject: Re: [okapi-devel] Global <gls:glossary> element in XLIFF 2.0?

 

I have another question in relation to this: Does anyone know what the rationale is for allowing a <gls:glossary> node only on the <unit> level, but not on the <file> or <group> levels? I might be missing something, but it seems that it is not possible to have one global glossary module node for the XLIFF file. This, however, could lead to a lot of duplicate information when the same term occurs many times throughout the text (as is usually the case, for example, with technical texts).

Cheers,

Martin
 

Am Sonntag, 18. Oktober 2015 15:45:30 UTC+2 schrieb Yves:

Hi Martin,

 

Yes, I suppose: pointing to the first occurrence is the only option.

It’s not great as the several occurrences may be in separate segments, and thus treated separately from the user viewpoint.

 

Maybe someone in the XLIFF TC has some idea how to address that use case?

 

Cheers,

-yves

 

 

From: okapi...@googlegroups.com [mailto:okapi...@googlegroups.com] On Behalf Of Martin Wunderlich
Sent: Friday, October 16, 2015 6:05 AM
To: okapi-devel <okapi...@googlegroups.com>
Subject: [okapi-devel] Global <gls:glossary> element in XLIFF 2.0?

 

Hi,

This is not strictly an Okapi question, but somehow I have this feeling that people here might be able to help. I am currently looking into using the glossary module provided by XLIFF 2.0. I noticed that the glossary entries can be attached to several different strucural elements. One glossary entry can reference one id atrribute. This is the id attribute of the mrk element, which is used to mark the occurrence of the term. However, since this id attribute needs to be unique within a <unit> element, how would you deal with the same term occurring in several segments in the same unit? Would you reference only the first instance?

Cheers,

Martin
 
PS: I haven't forgotten about checking the source jar generation; it's been a weird week...

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.