"Bernard Chardonneau" <[email protected]> čálii: >> From: Tommi A Pirinen <[email protected]> >> Am Tue, 28 Feb 2017 10:33:25 +0100 >> schrieb Kevin Brubeck Unhammer <[email protected]>:
[...]
>> > However, sometimes people write compounds in
>> > lowercase, so I try including both upper and lower-case lemmas (I only
>> > care about generation now):
>> >
>> > <e><p><l>pc-ane</l><r>pc<s n="n"/><s n="m"/><s n="pl"/><s
>> > n="def"/></r></p></e> <e><p><l>PC-ane</l><r>PC<s n="n"/><s n="m"/><s
>> > n="pl"/><s n="def"/></r></p></e>
>> >
>> > but that gives
>> >
>> > $ echo '^PC<n><m><pl><def>$' | lt-proc -d foo.autogen.bin
>> > PC-ane/PC-ANE
>> >
>> > Would it make sense for lt-proc to not output forced-uppercase
>> > analyses if there's an otherwise identical dictionary-uppercase
>> > analysis? (Would it be easily implementable?)
>>
>> I have no idea of the implementability of this, but it affects most
>> fin- pairs, so if there's anything remotely reasonable I can also help
>> as much as I can.
>>
>
> Why not putting a LR restriction on the unwanted surface form ?
This issue is only about generation. If we do
<e r="LR"><p><l>pc-ane</l><r>pc<s n="n"/><s n="m"/><s n="pl"/><s
n="def"/></r></p></e>
<e> <p><l>PC-ane</l><r>PC<s n="n"/><s n="m"/><s n="pl"/><s
n="def"/></r></p></e>
then sure, '^PC<n><m><pl><def>$' will turn out correct as "PC-ane", but
'^pc<n><m><pl><def>$' will be ungeneratable and give "#pc".
We want '^pc<n><m><pl><def>$' to give "pc-ane",
but '^PC<n><m><pl><def>$' to give "PC-ane".
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
