On Thu, Sep 6, 2012 at 12:28 PM, Frank Bennett <[email protected]> wrote: > On Wed, Sep 5, 2012 at 10:56 PM, Frank Bennett <[email protected]> wrote: >> On Wed, Sep 5, 2012 at 10:13 PM, Rintze Zelle <[email protected]> wrote: >>> On Wed, Sep 5, 2012 at 7:41 AM, Sylvester Keil <[email protected]> wrote: >>>> >>>> Note: I haven't worked out a general algorithm for gender lookups yet that >>>> considers all these fallbacks. >>> >>> >>> The scheme I had in mind is this: >>> >>> - if the target noun is neuter, only the neuter gender-variants are taken >>> into consideration >>> - if the target noun is feminine (or masculine), both the feminine (or >>> masculine) and neuter gender-variants are taken into account. If an ordinal >>> term exists both as a feminine (or masculine) and a neuter variant, the >>> feminine (or masculine) variant is used >>> >>> For example, with >>> >>> <term name="ordinal">.ª</term> (1) >>> <term name="ordinal-01">.ª</term> (2) >>> <term name="ordinal-01" gender-form="masculine">.º</term> (3) >>> <term name="ordinal-01" gender-form="feminine">.ª</term> (4) >>> <term name="ordinal-02" gender-form="masculine">.ºº</term> (5) >>> >>> * if the target noun is neuter, term definitions 1 and 2 are taken into >>> account >>> * if the target noun is feminine, term definitions 1 and 4 are taken into >>> account >>> * if the target noun is masculine, term definitions 1, 3 and 5 are taken >>> into account >>> >>> Rintze >> >> Okay, that's helpful. > > So it was a quick month. > > I've put up a fresh release of MLZ (m245) that works with the updated > fr-FR locale and handles the above example as per Rintze's description > of the gender fallback logic on ordinals. > > What threw me is that the fallback priorities on ordinals differ from > those for straight terms (at least in my implementation). Terms always > have a hard-wired default value (assigned now according to the logic > of my earlier post). Getting that right was tricky, because the > default priorities can't be evaluated until the full set of ordinal > terms is known. Ordinals need to steer clear of the default unless it
Correction: the above should read "until the full set of gender variants is known". > was a non-gendered term assigned explicitly. > > In any case, I'm pretty confident that it's right now, but it hasn't > been extensively tested. Please try to break it; if problems turn up, > we'll fix them. > > Frank > >> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> xbiblio-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel >>> ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
