unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: teddy@recompile.se, 20704@debbugs.gnu.org
Subject: bug#20704: info.el bug fix; Interprets Info format wrongly
Date: Wed, 10 Jun 2015 21:21:25 +0300	[thread overview]
Message-ID: <83twufs9ui.fsf@gnu.org> (raw)
In-Reply-To: <jwvvbevpi7k.fsf-monnier+emacsbugs@gnu.org>

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: teddy@recompile.se, 20704@debbugs.gnu.org
> Date: Wed, 10 Jun 2015 13:50:29 -0400
> 
> > Using byte-to-position would make things worse for Latin-1 and the likes.
> 
> There's also the problem of EOL encoding, but I'll just ignore it for now.

That was never a problem before Texinfo 5.x: makeinfo didn't count
the CR characters in the CRLF EOLs, and the Info readers removed the
CR characters when reading the Info files.

But Texinfo 5.x and later does count the CR characters, so the
stand-alone Info reader was recently changed to account for that.
Which means that Emacs will now have a problem, whereby the byte
counts in the tag tables will be inaccurate, and our only hope is the
1000-character tolerance we use to look for the node around the
position stated in the tag table will be large enough.

Read the gory details about that in this thread:

  http://lists.gnu.org/archive/html/bug-texinfo/2014-12/msg00068.html





  reply	other threads:[~2015-06-10 18:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 14:54 bug#20704: info.el bug fix; Interprets Info format wrongly Teddy Hogeborn
2015-06-01 14:01 ` Stefan Monnier
2015-06-01 15:12   ` Eli Zaretskii
2015-06-09 11:09     ` Teddy Hogeborn
2015-06-09 14:29       ` Eli Zaretskii
2015-06-09 16:01       ` Stefan Monnier
2015-06-10 17:50     ` Stefan Monnier
2015-06-10 18:21       ` Eli Zaretskii [this message]
2015-06-11  3:02         ` Stefan Monnier
2015-06-11 13:11           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83twufs9ui.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20704@debbugs.gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=teddy@recompile.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).