Hello,
Thanks for all the suggestions. I tried to come up with a rule that deals
with this issue, but it doesn't seem to work so well. So, the rule would be
as follows:
<rule>
<pattern>
<pattern-item n="vbfaire"/>
<pattern-item n="adj"/>
</pattern>
<action>
<out>
<lu>
<lit v="vbetre"/>
<lit-tag v="a_verb"/>
<clip pos="1" side="tl" part="temps"/>
<clip pos="1" side="tl" part="pers"/>
<clip pos="1" side="tl" part="nbr"/>
</lu>
<b/>
<lu>
<clip pos="2" side="tl" part="lem"/>
<lit-tag v="adj"/>
<clip pos="2" side="tl" part="gender"/>
</lu>
</out>
</action>
</rule>
My intention was: when having the french verb faire(to do) followed by an
adjective it should be translated using etre(to be) followed by the
adjective.
The verbs from the pattern being matched are defined like:
<def-cat n="vbfaire">
<cat-item lemma="faire" tags="vblex.*"/>
<cat-item lemma="faire" tags="vblex"/>
</def-cat>
In the same manner I defined:
<def-cat n="vbetre">
<cat-item lemma="être" tags="vblex.*"/>
<cat-item lemma="être" tags="vblex"/>
</def-cat>
The pattern is recognized, the adjective is also translated ok, but the
verb doesn't get translated. ( for example fait beau has the output #vbetre
frumos instead of este frumos).
Where am I going wrong?
Thanks a lot,
Alexandru Blanda
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
