unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: bob@rattlesnake.com, emacs-devel@gnu.org
Subject: Re: `texinfo-format-buffer' doesn't fold long lines
Date: Tue, 01 Mar 2005 06:36:01 +0200	[thread overview]
Message-ID: <01c51e18$Blat.v2.4$512429a0@zahav.net.il> (raw)
In-Reply-To: <b9yr7j0i6gc.fsf@jpl.org> (message from Katsumi Yamaoka on Tue, 01 Mar 2005 08:57:07 +0900)

> Date: Tue, 01 Mar 2005 08:57:07 +0900
> From: Katsumi Yamaoka <yamaoka@jpl.org>
> Cc: emacs-devel@gnu.org
> 
> >     ... I don't think this fix should be used as is.
> 
> > Evidentally, back in November 2001, a user in FSF India could not
> > format the then new edition of `emacs-lisp-intro.texi' using
> > `texinfo-format-buffer' because `texinfmt.el' created the bad line
> 
> >     @end itemize@refill
> 
> > He was using a Microsoft operating system and thought (erroneously,
> > according to Eli Zaretskii) that `makeinfo' had not yet been ported.
> > That is why he was using the deprecated `texinfo-format-buffer'
> > command.
> 
> > In any event, I completely forgot about it.
> 
> I see, and I will have to keep in mind that there might still be
> need to fix the `@end itemize@refill' problem.

I'd rather not have us fix a problem by reintroducing another problem
that we fixed in the past.  Isn't there another way to solve both of
them at once?

> Probably, what makeinfo should do first will be to decode text,
> before formatting them.  And the means to know the coding system
> which is used to decode text will be necessary.

There's already such a means: the @documentencoding directive.  What
is missing is support for multibyte encodings.

  reply	other threads:[~2005-03-01  4:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28  9:18 `texinfo-format-buffer' doesn't fold long lines Katsumi Yamaoka
2005-02-28 15:11 ` Robert J. Chassell
2005-02-28 23:57   ` Katsumi Yamaoka
2005-03-01  4:36     ` Eli Zaretskii [this message]
2005-03-01  5:32       ` Katsumi Yamaoka
2005-03-01 19:42         ` Eli Zaretskii
2005-03-01 15:30       ` Robert J. Chassell
2005-03-02 11:22     ` Richard Stallman
2005-03-02 12:21       ` Katsumi Yamaoka
2005-03-03 11:03         ` Richard Stallman
2005-03-03 11:54           ` Katsumi Yamaoka
2005-03-04  4:52             ` support of Japanese in makeinfo Katsumi Yamaoka
2005-02-28 21:53 ` `texinfo-format-buffer' doesn't fold long lines Richard Stallman
2005-02-28 22:09   ` Stefan Monnier
2005-02-28 22:31     ` Katsumi Yamaoka
2005-03-02 11:22     ` Richard Stallman

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='01c51e18$Blat.v2.4$512429a0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    /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).