Ah, understand.
Thanks.
2019年11月7日(木) 午前5:06 Gavin Smith :
> On Mon, Nov 4, 2019 at 1:21 PM Takesi Ayanokoji
> wrote:
> >
> > Hi.
> >
> > Is there a way to use section name instead of node name in info-files?
> >
> > To do this, I use cu
Hi.
Is there a way to use section name instead of node name in info-files?
To do this, I use customization variables NODE_NAME_IN_INDEX=0 and
NODE_NAME_IN_MENU=0 in makeinfo arguments(I saw
Thanks.
I will try those commands.
2016年10月5日(水) 午後8:51 Masamichi Hosoda :
> >> By the way, japanese translated texi can't converrt to pdf by using
> >> makeinfo nor texi2pdf.
> >> I generate translated pdf by bellow commands.
> >> $ TEX=ptex texi2dvi -c emacs.texi
> >> $
> > Don't know. I would think you would send your translated manuals to
> > the relevant projects: Emacs and gettext, in this case. The TP just
> > handles POT files -- when provided by the original project -- and the
> > resultant PO files.
>
> So what I understand is, if the translation of a
> > @setfilename ../../info/emacs-ja
>
> This is wrong. It would be
>
> @setfilename emacs-ja.info
OK, I will use tsis filename.
I tried few patterns and I found funny behavior of TexInfo's tools.
For Prerequisite,
1) I tried out original emacs distributions texinfo(English version)
to see only check for feature of @setfilename.
2) In emacs distribution's $(distdir)/doc/Emacs/Makefile,
some of commanline
> I think having the translated manuals by different names in the same
> directories is better, as there won't be a need to tweak INFOPATH
> then, and the user can choose which version to read as they see fit.
> So, in addition to 'emacs.info', there will be 'emacs-ja.info',
> 'emacs-de.info',
Hi all.
I often read GNU application's, and one day, I decided to translate these
manuals to non-English(Japanese).
After that, I translated 2 application's manuals(emacs and gettext).
Texinfo wotks fine to handle Japanized texinfo. Translated manuals are
converted to any kind of device(info,