GNU bug report logs -
#40695
[PATCH] ; Fix some typos and doc issues
Previous Next
Reported by: Štěpán Němec <stepnem <at> gmail.com>
Date: Sat, 18 Apr 2020 11:38:01 UTC
Severity: normal
Tags: patch
Done: Štěpán Němec <stepnem <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
On Sat, 18 Apr 2020 18:38:52 +0300
Eli Zaretskii wrote:
>> From: Štěpán Němec <stepnem <at> gmail.com>
>> Cc: 40695-done <at> debbugs.gnu.org
>> Date: Sat, 18 Apr 2020 17:31:18 +0200
>>
>> > Either the split already occurs or is close (i.e. the offending text
>> > is close to the edge of a line. Otherwise we will have to put all of
>> > them in @w{..}, and that seems too much.
>>
>> I rechecked the occurences and tried to remove some of the added @w{}s,
>> and notably failed with ispell-kill-ispell and ispell-change-dictionary,
>> both of which are as far from the edges as one can get (the case of
>> ispell-message was already mentioned in the bug#6411 message)
>
> Sorry, I don't understand what failed here.
Even though all three of them are in the middle of the line (in
Texinfo), they end up split in Info, unless wrapped in @w{}.
> Maybe I wasn't clear enough: by "close to the edge" I meant in the
> produced Info file, not in Texinfo. If that's not the issue, please
> point out what am I missing.
Yes, that's the issue: the Texinfo source doesn't seem to be useful in
determining which occurences are safe from splitting (which seemed to be
what you were saying in
https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-04/msg00245.html
835ze8o53t.fsf <at> gnu.org
)
The only way to know is checking the Info output, barred maybe some
exceptional cases like single-line paragraphs.
--
Štěpán
This bug report was last modified 5 years and 112 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.