Re: help: How to use section name instead of node name in info files.

[Takesi Ayanokoji]

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 customization variables NODE_NAME_IN_INDEX=0 and
> NODE_NAME_IN_MENU=0 in makeinfo arguments(I saw
> http://stress.stappe.de/software/texinfo/manual/texinfo/html_node/Other-Customization-Variables.html#Other-Customization-Variables
> ).
>
> Info files would have to use the node name in menus and other
> references between nodes. Unlike HTML where the target of a hyperlink
> is not visible to the reader of the document, the target of a link in
> Info is in the text the user sees. It would be awkward to show section
> names instead of node names in Info.
>
> These two customization variables appear only to be used for HTML
> output, so I think they should be documented in the "Other
> Customization Variables" node instead.
>

help: How to use section name instead of node name in info files.

[Takesi Ayanokoji]

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
http://stress.stappe.de/software/texinfo/manual/texinfo/html_node/Other-Customization-Variables.html#Other-Customization-Variables
).

When I generate html-files, it works fine.

But when I generate info-files, node names are used instead of section
names.

Did I miss anything?

Thanks.

Re: [help-texinfo] (no subject)

[Takesi Ayanokoji]

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
> >> $ dvipdfmx emacs.dvi
> >> Here, ptex and dvipdfmx are distributed by TexLive packages.
> >
> > This is not surprising. ptex is a different version of TeX. Japanese
> > Texinfo has also been successfully converted with two other programs
> > based on TeX, XeTeX and LuaTeX.
> >
> > I'm copying in Masamichi Hosoda on this email, in case he isn't
> > subscribed to this mailing list. He did work on getting Japanese to
> > work with Texinfo, including with XeTeX and LuaTeX.
>
> Current Texinfo contains Japanese sample file doc/short-sample-ja.texi.
> The following command can compile it.
>
> $ PDFTEX=xetex texi2pdf short-sample-ja.texi
> or
> $ PDFTEX=luatex texi2pdf short-sample-ja.texi
>
> For XeTeX, TeX Live 2012~2016 XeTeX related package and Japanese package,
> and Chinese package are required.
>
> For LuaTeX, TeX Live 2016 LuaTeX related package and Japanese package
> are required.
>
> pTeX cannot be used.
>
> Here is another Japanese Texinfo sample.
> https://github.com/trueroad/texinfo-sample-jp
>
> If you can read Japanese texts,
> the following web page describes making Japanese Texinfo files.
> http://www.trueroad.jp/2016/05/14-01.html
>

Re: [help-texinfo] how to distribute translated manuals?

[Takesi Ayanokoji]

> > 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 manual were to
> managed through the TP, then the manual would have to be converted
> into a POT file, and the PO files that the translators produced would
> have to be converted back into Texinfo files?

I translate texi file by po4a which is used internationalize  GNU web via
GNUnited nation package.
I manage po files on GitHub personally.
See https://github.com/ayatakesi/emacs-24.5-doc-emacs .

Re: [help-texinfo] (no subject)

[Takesi Ayanokoji]

> > @setfilename ../../info/emacs-ja
>
> This is wrong. It would be
>
> @setfilename emacs-ja.info
OK, I will use tsis filename.

Re: [help-texinfo] (no subject)

[Takesi Ayanokoji]

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 specifies -o(--output option), but I want to
check only @setfilename, so I omit  -o option from commandline.
  3) I modified only @setfilename from ../../emacs to ../../emacs-ja

>From a conclusion,
I guess texi2dvi family (texi2pdf, texi2ps) only see the filename.
And I guess makeinfo --html don't work correctly when @setfilename
includes relative path.

Here is the execution log

#
# start here
#

### I only modified @setfilename line. ###
$ head -4 emacs.texi
\input texinfo  @c -*- coding: utf-8 -*-

@setfilename ../../info/emacs-ja
@settitle GNU Emacs Manual

### Make info file and it works as expected. ###
$ makeinfo --force --enable-encoding -I . --no-split emacs.texi
$ ls -l ../../info/
合計 2360
-rw-r--r-- 1 hiden hiden 2414105 10月  4 20:07 emacs-ja

### Make dvi and pdf files###
$ TEXINPUTS=".:../misc:$TEXINPUTS" \
> MAKEINFO="makeinfo --force --enable-encoding -I ." \
> texi2dvi emacs.texi

  ... (texi2dvi's output messages) ...

###  But it didn't produce emacs-ja.dvi ###
### It Is seems like only detect texi's filename ###
$ make mostlyclean
rm -f *.aux *.log *.toc *.cp *.cps *.fn *.fns *.ky *.kys \
  *.op *.ops *.pg *.pgs *.tp *.tps *.vr *.vrs
$ ls -a ../../info/
.  ..  emacs-ja
$ ls -l *.dvi
-rw-r--r-- 1 hiden hiden 3538752 10月  4 20:13 emacs.dvi

### Make dvi file###
$ TEXINPUTS=".:../misc:$TEXINPUTS" \
> MAKEINFO="makeinfo --force --enable-encoding -I ." \
> texi2pdf emacs.texi

$ make mostlyclean
rm -f *.aux *.log *.toc *.cp *.cps *.fn *.fns *.ky *.kys \
  *.op *.ops *.pg *.pgs *.tp *.tps *.vr *.vrs
$ ls -a ../../info/
.  ..  emacs-ja
$ ls -l *.pdf
-rw-r--r-- 1 hiden hiden 2528996 10月  4 20:18 emacs.pdf

### At last, make html and this befavior is strange. ###
$ makeinfo --force --enable-encoding -I . --no-split --html emacs.texi

### ls *.html files but not found. ###
$ ls -l *.html
ls: cannot access '*.html': No such file or directory
$ ls -l ../../info/*.html
ls: cannot access '../../info/*.html': No such file or directory

### So, I find. ###
$ find /usr/local/src/emacs-24.5 -type f -name \*.html
/usr/local/src/emacs-24.5/doc/..html
/usr/local/src/emacs-24.5/leim/MISC-DIC/CTLau-b5.html
/usr/local/src/emacs-24.5/leim/MISC-DIC/CTLau.html
/usr/local/src/emacs-24.5/admin/unidata/copyright.html
/usr/local/src/emacs-24.5/nextstep/Cocoa/Emacs.base/Contents/Resources/Credits.html

### I find the file. It was generated the file which name starts '.'. ###
$ ls -l /usr/local/src/emacs-24.5/doc/..html
-rw-r--r-- 1 hiden hiden 4084383 10月  4 20:24
/usr/local/src/emacs-24.5/doc/..html

#
# ends here.
#

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
$ dvipdfmx emacs.dvi
Here, ptex and dvipdfmx are distributed by TexLive packages.

Regards.

Re: [help-texinfo] (no subject)

[Takesi Ayanokoji]

> 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', etc., and they all will appear in the DIR file.
Hi Eli.
OK, I will try this approach.
I guess it is achieved only cheange the value of @setfilename.
But I don't know the filename of pdf, html or text which are generate
from texinfo.
(Maybe, this is not a serious matter.)

Regards.

[help-texinfo] (no subject)

[Takesi Ayanokoji]

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, html, pdf...) correctly.

So next, how should I distribute these translations?
Currently, I distribute these manuals paersonaly via github under original
texinfo document's license.
Is this only way? For instance, such man-pages system has
internationalization support but info-system has or will support
internationalization system?

Regards.