unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Cc: help-texinfo@gnu.org, emacs-devel@gnu.org
Subject: Re: [help-texinfo] Re: coding systems vs. info files
Date: Fri, 10 Feb 2006 18:13:27 -0600	[thread overview]
Message-ID: <200602110013.k1B0DRH23757@f7.net> (raw)
In-Reply-To: <873biscpjr.fsf@jurta.org>

    the `Local Variables' section too far from the end of the Info file,
    so Emacs can't find it.

Because the tag table is huge, I would guess?  Or is there some other
reason?  Can someone point me to the problematic Texinfo file?

    It seems like makeinfo should
    ignore LANG for the most part, 

Right, it should not use LANG for output (this is nothing new), but
neither I nor anyone has implemented it yet.  (Bruno informed me it is
not so easy to switch languages in gettext, unfortunately, which is what
it boils down to.)  Meanwhile, using LANG for output means that at least
it is possible to get those boilerplate fragments in (say) French for a
French document.

    and just use the language the texinfo

BTW, Texinfo has @documentlanguage and @documentencoding commands.  It
doesn't try to "guess" anything.  The coding: tag reflects the
@documentencoding.  If there is no @documentencoding, there will be no
coding: tag.  I don't think it has any way of knowing what encoding the
translation for language XX used.

karl

  reply	other threads:[~2006-02-11  0:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  1:58 coding systems vs. info files Miles Bader
2006-02-09 14:54 ` Jesper Harder
2006-02-09 19:14   ` Juri Linkov
2006-02-11  0:13     ` Karl Berry [this message]
2006-02-11  1:11       ` [help-texinfo] " Juri Linkov
2006-02-12  1:40         ` Karl Berry
2006-02-12 10:01           ` Andreas Schwab
2006-02-12 21:44         ` Kevin Ryde
2006-02-13 17:48           ` Juri Linkov
2006-02-13 22:07             ` Kevin Ryde
2006-02-11 22:03       ` Miles Bader
2006-02-12  4:28         ` Eli Zaretskii
2006-02-09 17:28 ` Juri Linkov

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=200602110013.k1B0DRH23757@f7.net \
    --to=karl@freefriends.org \
    --cc=emacs-devel@gnu.org \
    --cc=help-texinfo@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).