> Are the changes being implemented going to alter the behavior of the
> punctuation marks that are not analyzed as tokens?
>
Yes, as was discussed in the thread about markup handling in Apertium,
input blanks are now read as a queue and output in order in the available
spots in the rule output.
Missatge de Tino Didriksen del dia dg., 30 d’ag.
2020 a les 11:15:
> Why is - a blank in the first place? If it's needed in contexts, it should
> be fully analyzed as a token.
> This goes for all Apertium languages and pairs. I don't understand why
> punctuation generally isn't analyzed. I
Also, I agree with Tino, if the punctuation is important for the context
then it should probably be analysed as a token.
*तन्मय खन्ना *
*Tanmai Khanna*
On Sun, Aug 30, 2020 at 3:16 PM Tanmai Khanna
wrote:
> Hèctor what I mean is, if you don't want a space in the output of rules
> you have to
Hèctor what I mean is, if you don't want a space in the output of rules you
have to remove the .
For eg.,
$ echo "f.75v." | apertium -d .. fra-frp
*f.75 v..
This space between 75 and v is now there because the output rule has a
and so if you want the output to come without a space, you should
Missatge de Tanmai Khanna del dia dg., 30 d’ag.
2020 a les 12:06:
> Hi Hèctor,
> I'm dealing with the issues I see one by one.
> 1. I was flushing the remaining blanks after processOut because I thought
> usually we only have one .. block in the rule, but in some of
> your rules there's
Why is - a blank in the first place? If it's needed in contexts, it should
be fully analyzed as a token.
This goes for all Apertium languages and pairs. I don't understand why
punctuation generally isn't analyzed. I assume it's just historic.
-- Tino Didriksen
On Sun, 30 Aug 2020 at 08:27,
Hey,
It solved them Franco-Japanese issue as well :D
Can you check the diff once and see if there's any more issues Hèctor?
(After updating apertium).
*तन्मय खन्ना *
*Tanmai Khanna*
On Sun, Aug 30, 2020 at 2:35 PM Tanmai Khanna
wrote:
> Hi Hèctor,
> I'm dealing with the issues I see one by
Hi Hèctor,
I'm dealing with the issues I see one by one.
1. I was flushing the remaining blanks after processOut because I thought
usually we only have one .. block in the rule, but in some of
your rules there's multiple, so in the latest commit to apertium/apertium,
I made them flush after the
Missatge de Tanmai Khanna del dia dg., 30 d’ag.
2020 a les 9:49:
> My guess is, the transfer rule for Franco-Japanese has a two word input,
> so the stored blank is "-". Now the output has 3 words "una
> Franco-Japonêsa", since the blanks are printed in order, they're printed in
> the first
My guess is, the transfer rule for Franco-Japanese has a two word input, so
the stored blank is "-". Now the output has 3 words "una Franco-Japonêsa",
since the blanks are printed in order, they're printed in the first
available spot in the output rules.
There's a few possible solutions for
Hèctor,
No worries I'll look into this. Can you send the input sentences? I want to see
the transfer rules that are applying to the erroneous parts. They might need
some changing.
तन्मय खन्ना
Tanmai Khanna
From: Hèctor Alòs i Font
Sent: Sunday, August 30, 2020
Unfortunately, I found a lot of problems cased by superblanks, especially
with the handling of hyphens. See a couple of differences in translations
of my French test corpus into Arpitan before and after the update:
< 00607. Tandis que les Tétes Broulâyes sont en *permission sur *Espritos
Marcos,
12 matches
Mail list logo
