t;
> Please insert @hyphenation{auto-ma-ti-cal-ly}
> in texinfo.tex.
OK done.
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
Please insert @hyphenation{auto-ma-ti-cal-ly}
in texinfo.tex.
--
Dr Richard
...@debbugs.gnu.org; bug-texinfo@gnu.org
Subject: RE: bug#18308: 24.4.50; Info viewer cannot follow menu entry for
'(texinfo) @- @hyphenation'
use exactly the same node names whatever the language, so that the
same link can be used, and when the manual is compiled to multifile
HTML, you have the same
Answers inserted below...
Date: Sun, 31 Aug 2014 23:37:06 +0100
Subject: Re: bug#18308: 24.4.50; Info viewer cannot follow menu entry for
'(texinfo) @- @hyphenation'
From: gavinsmith0...@gmail.com
To: vincent@hotmail.fr
CC: 18...@debbugs.gnu.org
On Mon, Sep 1, 2014 at 8:40 PM, Vincent Belaïche vincent@hotmail.fr wrote:
Having translated node names isn't as important because there would be
translated headers in the contents of files/nodes saying what section
we're in. The main use would be the status bar in a browser giving the
use exactly the same node names whatever the language, so that the
same link can be used, and when the manual is compiled to multifile
HTML, you have the same file tree whatever the language. Seems
Currently the usual practice is that a translated document is just
(adding bug-texinfo)
On Fri, Aug 22, 2014 at 11:04 PM, Vincent Belaïche
vincent@hotmail.fr wrote:
Finally, as an EMACS user, it would be more important to me
* if docstring could be written in a sort of texinfo-light format (when
you create a package or anything you first do docstring,
From: Vincent Belaïche vincent@hotmail.fr
Cc: 18...@debbugs.gnu.org, Texinfo bug-texinfo@gnu.org
Date: Fri, 22 Aug 2014 15:01:43 +0200
- texi2any must collapse multiple blanks in node names *everywhere*, but
it is still allowed to break and indent a node name containing a blank
2014 09:36:14 +0300
From: e...@gnu.org
Subject: Re: bug#18308: 24.4.50; Info viewer cannot follow menu entry for
'(texinfo) @- @hyphenation'
To: vincent@hotmail.fr
CC: gavinsmith0...@gmail.com; 18...@debbugs.gnu.org
[...]
I a nutshell, there are cases of node references where the info
How to enable hyphenation of this word?
The hyphenation points are already being considered. I put @loggingall
in the source and inspected the resulting paragraph breaking; it has the
expected discretionaries for the determining.
What's happening is that TeX is trying to minimize badness
in a string.
no hyphenation occurs. The output is still the same.
How to enable hyphenation of this word?
Bruno
inline: ugly-paragraph.png
On 2008/10/13 06:05 +0200, Werner LEMBERG wrote:
the CVS version of texinfo now supports non-English hyphenation!
As far as I can see in 2.1.62 French, German and Spanish Learning
Manuals, it already partially did before I updated texinfo.tex
yesterday, although I'm not sure how some words
translated, but there wasn't any hyphenation
support.
I didn't notice any hyphenation difference after updating texinfo.tex,
but I guess TeXlive 2008 is needed to see improvements (Fedora 9
provides TeXlive 2007).
Yes, probably.
It's certainly a good thing you added txi-LL.tex files, as people
who
it already partially
It used English hyphenation patterns in all cases (and still does, if
the real patterns aren't there).
I didn't notice any hyphenation difference after updating texinfo.tex,
but I guess TeXlive 2008 is needed to see improvements
More precisely, what you need
It works with etex too if you use
I made changes to texinfo.tex and all the txi-??.tex files to implement
this. Thanks very much for the suggestion and code.
karl
Do you want to?
Will have a look, but I can't promise anything due to time
constraints.
To get some basic non-English hyphenation support, almost nothing has
to be changed if you use the current TeXLive. Here I demonstrate what
to do for German.
. The basic trick is to process
Hi Werner,
On Do, 02 Okt 2008, Werner LEMBERG wrote:
. The basic trick is to process the texinfo file with `eplain'
instead of `tex'. With TeXLive, this gives access to all
configured hyphenation patterns. `bplain' would do the same, but
there is (currently) no soft link
(I think this has nothing to do with Texinfo, but for TeX Live purposes ...)
`bplain' would do the same, but there is (currently) no soft link to
the `tex' binary.
(Norbert, bplain = babel plain)
Would it useful to have? Although there is a bplain.ini file, I see no
sign that there was
. The basic trick is to process the texinfo file with `eplain'
Wouldn't it work with etex? I don't see that any eplain-specific
features are being used. (\makeat*er being trivial, as we all know.)
texi2dvi already uses etex (or pdf[e]tex) when they are present. So in
this case, I don't
. The basic trick is to process the texinfo file with `eplain'
Wouldn't it work with etex?
No. As outlined in babel.pdf, plain.tex must not be modified, thus
there are only US-English hyphenation patterns available.
Is there a simple table somewhere of the correct
\{left,right
On Do, 02 Okt 2008, Karl Berry wrote:
Is there a simple table somewhere of the correct \{left,right}hyphenmin
values? I don't relish digging into all the babel files.
grep lefthyphenmin Master/tlpkg/tlpsrc/*
??
We added all that is known there for exactely that purpose. In fact it
is
No. As outlined in babel.pdf, plain.tex must not be modified, thus
there are only US-English hyphenation patterns available.
Not so. etex loads all the patterns (and plain.tex remains unmodified,
of course). This was a change in 2008, although it could have been done
earlier
Wouldn't it work with etex?
No. As outlined in babel.pdf, plain.tex must not be modified, thus
there are only US-English hyphenation patterns available.
Sorry, my mistake. It works with etex too if you use this snippet
instead of the previous one:
[EMAIL PROTECTED]
\global
any chance that this gets implemented on the TeX side?
It would be very nice.
Basically, it should be just an interface to the plain TeX
implementation of Babel, right?
I don't know. All we really have to do is set \language. Do we need
Babel for that?
Now that etex (in TL'08)
Basically, it should be just an interface to the plain TeX
implementation of Babel, right?
I don't know. All we really have to do is set \language. Do we need
Babel for that?
Well \language expects a number, doesn't it? Using Babel, we can use
a string instead...
Has
Well \language expects a number, doesn't it?
Yes.
Using Babel, we can use a string instead...
Clearly we have to map from the existing @documentlanguage strings in
Texinfo to the numbers that were dumped in the .fmt file for the various
languages. If Babel can help us do that, and
Folks,
any chance that this gets implemented on the TeX side? Basically, it
should be just an interface to the plain TeX implementation of Babel,
right?
Has someone worked on this already?
Werner
27 matches
Mail list logo