OK, so if looks as if I am going to have to use \loop \if \repeat
in conjunction with \XeTeXcharclass ‹char slot› [=] ‹interchar class›
to set up the XeTeX char class for polytonic Greek, but looking
at Charmap for Palatino Linotype it would seem as if at least
two non-contiguous ranges will be
Here is my interim solution : better solutions welcomed !
\XeTeXinterchartokenstate = 1
\newXeTeXintercharclass \English
\newXeTeXintercharclass \Greek
\newXeTeXintercharclass \Hebrew
\newXeTeXintercharclass \Latin
\newcount \charclass
\charclass = 0380
\loop
\XeTeXcharclass
Arthur Reutenauer wrote:
Since you'll be using XeTeX, you can take advantage of the fact that
the two languages you'll be working with use disjoint character sets,
and make the language switch automatic using XeTeX's inter-character
token mechanism.
Thank you again, Arthur. This will
Robin Fairbairns wrote:
from this i learn (a) that at the time the post
http://listserv.tau.ac.il/cgi-bin/wa?A2=ind0011L=ivritexP=591 was
written, there was no hebrew hyphenation patterns, even among those
whose main language is hebrew.
that hebtex list is a closed one, so (apart from
Philip Taylor wrote:
Thank you VERY much, Heiko. Very much appreciated.
What I found interesting is that identical code works
for \XeTeXpdffile but not for \XeTeXpicfile (see my
later message to Ross for details).
** Phil.
And the following trivial change to the original source
code
. It
is no more (and no less) ambiguous than english, which may refer
to British English, Australian English, American English and so on.
Philip Taylor
in stand-alone
mode rather than as a generic term (meaning [the] [national] language
[of]) followed by a country name. Thus I suspect that UNESCO were
in fact using the word elliptically in the context quoted.
Philip Taylor
Jonathan Kew wrote:
On 27/11/13 19:21, Scott Kostyshak wrote:
There appear to be 742 languages of Indonesia
[1]. Are those languages not Indonesian?
While there are many hundreds of other languages spoken in Indonesia
(see also http://www.ethnologue.com/country/ID/languages), which
Mojca Miklavec wrote:
If a dummy user provides
text with ligatures, there is no way to hyphenate that word properly.
Well, yes; but what if a real user does the same ?! :-)
Right, but if you have the same values of \LHM and \RHM
for Am.E and Br.E, do you still get the hyphenation
you adduced earlier ?
** Phil.
Arthur Reutenauer wrote:
Because of the patterns, or because of \LHM \RHM ?
Because of the combination of all these settings. I just wanted
Arthur Reutenauer wrote:
You should. Characters such as U+FB01 are deprecated and shouldn't be
used in text.
/Characters/ ... : yes. But consider a Unicode-in/Unicode-out
preprocessor; might it not generate fi in the output stream,
since it thinks it is generating glyphs, yet in a
b...@ams.org wrote:
(and a hyphen that ought to be there,
before the n, is missing. into the
exception list that goes.)
/Before/ the n ? You say Aye-koh-nogg-rə-phee and
not Aye-konn-ogg-rə-fee ?
** Phil.
-ciates
...
ret-ri-bu-tion
ta-ble
}
modulo a tiny amount of TeX markup. Can you say more about what
exactly a pure text version would be to your mind, Stephen ?
Philip Taylor
Stephan Hennig wrote:
modulo a tiny amount of TeX markup. Can you say more about what
exactly a pure text version would be to your mind, Stephen ?
I mean a file without that TeX mark-up, comments etc. Package
hyph-utf8 distributes such pure pattern files (ending .pat.txt),
but I can't see
Mojca Miklavec wrote:
No, the patterns should work just fine with a large alphabet.
This part I do not understand, Mojca; surely the patterns /define/ the
size of the alphabet, do they not ? If letter xqqyn is not in the
patterns, then TeX cannot hyphenate a word containing letter xqqyn,
can
Jörg Knappen wrote:
TeX can hyphenate such a word, depending on the patterns available. E.g.,
given the pattern a1 (There is always a good break point after the letter a)
it will happily hyphenate the a word containing the sequence axqqyn.
Ah, ys, so it can. I had overlooked that. Thank
Thank you, Arthur (and all others who have helped to identify the
cause). As an interim work-around, I had added :
\def ͵{\char `\͵ \penalty 1 \relax}
\def ʹ{\penalty 1 \char `\ʹ \relax}
which worked but which /may/ have had undesirable side-effects (none
noticed so
Dear Claudio --
Claudio Beccari wrote:
The problem is not LaTeX, but the program used for transforming XML
source into LaTeX code.
There is no such program. The XML is processed directly by XeTeX (see
http://www.eutypon.gr/eutypon/pdf/e2013-31/e31-a02.pdf).
The additional characters and
Werner LEMBERG wrote:
Example, please. It's not clear to me what you want to achieve.
Even if LHM = 2 and RHM = 2, do not hyphenate any word of less than
five letters.
Philip Taylor
Pablo Rodríguez wrote:
What contains the list of exceptions: words with more than
\totalhyphenmin letters which contain hyphenations that should be avoided?
It /can/; but more usually it contains a list of words that would be
hyphenated incorrectly were the patterns the only source of
Élie Roux wrote:
If I understand correctly, from TeX point of view, this would mean
adding the following penalties:
- \hyphenpenaltyweighttwo
- \hyphenpenaltyweightthree
- \hyphenpenaltyweightfour
- \hyphenpenaltyweightfive
- \hyphenpenaltysuffix
- \hyphenpenaltyprefix
-
arguably so
(depending on whether or not one regards the u as syllabic) and
toothache is indeed wrong.
Philip Taylor
Hans Hagen wrote:
- Is there any convention as how hyphenation files should be named?
Apparently most of them follow the pattern (load)hyph-LL (LL
= lang iso code) and (load)hyph-LL- ( = script iso code),
but not all. (And of course, the encoding in the form .ec.)
In
ee with Karl, but on this occasion I agree
100%. TeX is about /stability/, not about 'change'/'improvement'.
Philip Taylor
and probably no
> reader would notice the difference.
Of /course/ they would notice if pagination were affected. As I wrote
in an earlier reply, TeX is about stability, not about
change/improvement. Tastes in hyphenation may change over time; the
behaviour of TeX should not.
Philip Taylor
Reinhard Kotucha wrote:
> And pdftex is 100% backwards compatible with DEK's TeX.
Well, not really : compare the result of expanding (e.g.,)
\expandafter \ifx \csname pdfximage\endcsname \relax UNDEFINED\else
DEFINED\fi
in the two engines ...
** Phil.
Philip Taylor wrote:
> Reinhard Kotucha wrote:
>
>> And pdftex is 100% backwards compatible with DEK's TeX.
>
> Well, not really : compare the result of expanding (e.g.,)
>
> \expandafter \ifx \csname pdfximage\endcsname \relax UNDEFINED\else
> DEFINED
Martin Schröder wrote:
> Just to be pedantic: I seriously doubt that he uses TeX 2.x (that would
> be TeX82), but beli[e]ve he uses TeX 3.14159265, i.e. TeX90 - most likely
> a binary from the latest TeXLive.
I agree w.r.t. TeX 3+; no idea whether he uses the TeX Live version, though.
**
Reinhard Kotucha wrote:
> I suppose that TeX 3 is 100% downwards compatible with TeX82. Phil,
> can you confirm?
Knuth described the differences that affect compatibility (I have
removed those that apply only to METAFONT) in a message sent to Barbara
Beeton during October 1989 :
> 12.
e you writing on behalf of Google, or on
behalf of an independent group of contributors who are trying to write
something to run under Android, or what ... ?
Philip Taylor
epresents a horizontally segmentable unit of text,
Why not, I wonder, just a /segmentable/ unit of text; are there no
grapheme clusters in vertically-written languages ?
Philip Taylor
Pablo Rodríguez wrote:
> You are right, Barbara. I was actually testing "LibreOffice" and I get
> "Li-bre-Office" when using ConTeXt fonts and "Li-bre-Of-fice" with
> MinionPro (installed on my OS, not in ConTeXt).
As far as I am aware, there is no connection (other than co-incidental)
between
Barbara Beeton wrote:
> i agree with "Open-Office", but nothing
> will persuade me to hyphenate "Libre"
Collins-Robert indicates that the final schwa is optional, and without
it I cannot see it being bisyllabic, so I go along with Barbara here (as
usual ...).
** Phil.
Arthur Reutenauer wrote:
> On Thu, Mar 17, 2016 at 05:32:55PM +0000, Philip Taylor wrote:
>> Which many (perhaps most) search utilities and editors do not.
>
> If you say so. What's your point?
That "ancient Greek is not a true superset [of modern Greek]; modern
Greek con
Arthur Reutenauer wrote:
> That's not a very good point, then.
Thank you for your opinion, Arthur.
Arthur Reutenauer wrote:
> On Thu, Mar 17, 2016 at 10:58:22PM +0000, Philip Taylor wrote:
>> That "ancient Greek is not a true superset [of modern Greek]; modern
>> Greek contains where ancient Greek would contain
>> <oxeîa>, <bareîa> or character><pe
Arthur Reutenauer wrote:
> On Thu, Mar 17, 2016 at 05:26:35PM +0000, Philip Taylor wrote:
>> Tonos and oxia /look/ the same; search a file for character+oxia when
>> the file has been created with character+tonos and the former will not
>> be found.
>
> The
Arthur Reutenauer wrote:
> Tonos and oxia are the same character.
Tonos and oxia /look/ the same; search a file for character+oxia when
the file has been created with character+tonos and the former will not
be found.
Philip Taylor
Mojca Miklavec wrote:
>> Question : What does ".yaml" mean ?
>
> "YAML Ain't Markup Language" / "Yet Another Markup Language"
>
> See: https://en.wikipedia.org/wiki/YAML#Examples
>
> It's human-readable and computer-parsable format that would replace
> free-form text in the "headers" of
is for the verb, the form with "c" is for the noun; cf.
adviSe/adviCe.
Question : What does ".yaml" mean ?
Philip Taylor
d contain <oxeîa>,
<bareîa> or character><perispōménē>.
Philip Taylor
et giving
the appropriate \hyphenation rule for ны́не using XeLaTeX and polyglossia does
/not/ result in correct output. Also a pattern ы1 may not be relevant if the
word in question contains ы́ (with diacritic) -- that probably requires a
separate pattern.
Philip Taylor
idden using
\hyphenation when using XeLaTeX & polyglossia ?
Philip Taylor
Annexe 1 : MWE (XeTeX) :
% !TeX Program = XeLaTeX
\font \thisfont = "Palatino Linotype"
\uselanguage {russian}
\thisfont
\hsize = 1pt
\overfullrule = 0 pt
\XeTeXinputnormalization = 0
\hyphena
only one
> specified after polyglossia, becomes active only after \begin{document};
> before that the default language is language 0, that is english.
Philip Taylor
lutely no changes to your copy.
If the Debian authorities choose to rule that tex.web can no longer
be included in Debian distributions, then the accompanying loss of
the British English hyphenation patterns will be of zero concern.
--
Philip Taylor
the potential breakpoints when so written as
Běi-jīng-rén, not Běijīn-grén.
** Phil.
--
Philip Taylor
David Carlisle wrote:
> would suggest that he
is (very wisely) using Xe[La]TeX rather than an 8-bit engine
But then I'm not sure that there is a suitable version of
patgen
clude all links
to files with such a licence from my product", and what exactly you need
to "look out for" when considering licences other than GPL.
--
/Philip Taylor
/Christopher Camacho wrote:
Hello,
I am coding an app that uses Knuth-Liang algorithm for hyphenation
Dominik Wujastyk wrote:
[...]
The breaks made by the British TeX patterns normally agree
with The Oxford Minidictionary of
Spelling and Word-Division (1990). What I have now
49 matches
Mail list logo
