Originally discussed in thread
avoiding forced-uppercase generation when identical dictionary-uppercase exists Kevin Brubeck Unhammer Tue, 28 Feb 2017 01:34:30 -0800 (nabble)
If I have this in foo.dix:
<e><p><l>PC-ane</l><r>PC<s n="n"/><s n="m"/><s n="pl"/><s n="def"/></r></p></e>
then I get
$ echo '^PC<n><m><pl><def>$' | lt-proc -d foo.autogen.bin
PC-ane
which is what I want. 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?)
The only other solution I can think of is to put a tag on anything that
has an uppercase lemma, which sounds like more testvoc.
Diff:
https://github.com/jimregan/lttoolbox/issues/31#issuecomment-292018281 – relevant?
My changes there won't solve this particular issue (yet :), it just handles a somewhat similar problem with mixed case.
Actually, it seems to:
vs old
Last edit: Kevin Brubeck Unhammer 2017-04-21
Ok, committed
Nice! Btw, would it be possible to make the option compatible with -g or -d or -n? So we can do
lt-proc -g -Corlt-proc -n -C, since modes.xml typically saylt-proc $1in order to let the driver script optionally remove unknown word marks.On 18 May 2017 at 09:41, Kevin Brubeck Unhammer unhammer@users.sf.net wrote:
Give it about two weeks, I'll probably need -d by then.