> As far as I know there are some Japanese characters with a grammatical
> function that shouldn't appear at the start of a line. That's probably
Yes, there are - at least for Japanese I can give explanations (but
not for Chinese). The basic case is that between *kanji* one can
break, between *kan
On Tue, Nov 03, 2015 at 08:06:30PM +0200, Eli Zaretskii wrote:
> > Date: Tue, 3 Nov 2015 17:57:42 +
> > From: Gavin Smith
> > Cc: Norbert Preining , "Brendan O'Dea"
> > , Texinfo ,
> > Karl Berry
> >
> > > http://unicode.org/reports/tr29/
> > >
> >
> > As far as I know there are som
> Date: Tue, 3 Nov 2015 17:57:42 +
> From: Gavin Smith
> Cc: Norbert Preining , "Brendan O'Dea" ,
> Texinfo ,
> Karl Berry
>
> > http://unicode.org/reports/tr29/
> >
>
> As far as I know there are some Japanese characters with a grammatical
> function that shouldn't appear at the
On 2 November 2015 at 16:15, Gavin Smith wrote:
> Fixing the program that generates the
> Info files not to output the line breaks should be possible (i.e. an
> implicit @w around the Chinese characters).
I've implemented something, and it gives good output for the help2man
translation, as far as
On 3 November 2015 at 15:29, Eli Zaretskii wrote:
>> Date: Tue, 3 Nov 2015 23:06:19 +0900
>> From: Norbert Preining
>> Cc: Brendan O'Dea , Texinfo ,
>> Karl Berry
>>
>> > Chinese text isn't written with spaces between words, so makeinfo
>> > allows a break anywhere.
>>
>> Which is complete
> Date: Tue, 3 Nov 2015 23:06:19 +0900
> From: Norbert Preining
> Cc: Brendan O'Dea , Texinfo ,
> Karl Berry
>
> > Chinese text isn't written with spaces between words, so makeinfo
> > allows a break anywhere.
>
> Which is completely correct.
Not AFAIK, and not according to this:
http
> Chinese text isn't written with spaces between words, so makeinfo
> allows a break anywhere.
Which is completely correct.
Norbert
PREINING, Norbert http://www.preining.info
JAIST, Japan
On 2 November 2015 at 22:32, Karl Berry wrote:
> 1) In principle, there should be no line breaks within @w. That is the
> purpose of @w. (Even if fixed, I agree that's hardly a practical
> solution for the problem at hand, of course.)
>
> 2) Why is makeinfo considering that mid-text location to
