Profile

Title: RE: [xliff] Fragment Identification Hi Yves, all, > > For modules they should define their own two to five character > > prefix (as David suggested) to be used for references. The prefixes > > should be registered with the TC to avoid conflicts. > > Mmm... the registration aspect is a bit problematic: ...

Title: RE: [xliff] Fragment Identification Hi Yves, all, > Thanks for the thoughts on the different options. No problem. > - Any suggestions for modules/extensions? For modules they should define their own two to five character prefix (as David suggested) to be used for references. The prefixes should ...

Title: Fragment Identification Hi all, I have been looking into the fragment identification proposals made by David, Yves and Fredrik (original subject was "Comments on Fragment Identification"). As I see it there are two ways to go. We can either have David's solution where references can be local to ...

Hi all, In accordance with my previous comment (see below) I would suggest changing the id attribute on the segment element from OPTIONAL to REQUIRED. This way it would be possible to reference the segment id from a module like the matches module. In the case of the matches module it would mean ...

Hi all, In accordance with my previous comment (see below) I would suggest changing the scope of the id attribute on inline markup. It is currently only unique at segment level. This does not support the current matches implementation or my suggested implementation of matches (which references inline ...