\stopluacode
\definehyphenationfeatures
[underscore]
[righthyphenchar="FE000]
\setuphyphenation
[method=traditional]
\sethyphenationfeatures
[underscore]
\starttext
\hsize\zeropoint
hyphenation
\stoptext
Is there no way to define a language
)
end
context(table.concat(out, '\\discretionary{_}{}{}'))
end
\stopluacode
\starttext
% \hsize\zeropoint
\hyphenation
%%8b2f3c087046c3943ace0dc4f958ef2138e58a51b40eef6fab6fa1aeb845cc25%
%%7a410ab1b914bc399b4293f31c76fc2c73e5be5ea4d329f9e6820984688efec2
\ctxlua{sha
Dear list,
I have the following sample:
\starttext
\hsize\zeropoint
hyphenation
8b2f3c087046c3943ace0dc4f958ef2138e58a51b40eef6fab6fa1aeb845cc25%
7a410ab1b914bc399b4293f31c76fc2c73e5be5ea4d329f9e6820984688efec2
\stoptext
I plan to use underscore hyphenation. How can I
).}
\input Knuth\footnote{Distance between columns bad hyphenation.}
\input ward\footnote{Draw a line between the columns. Default is off.}
\input Knuth\footnote{FreeBSD tire ses origines de l'UNIX de Berkeley.}
\input ward\footnote{Draw a line between the columns. Default is off.}
\input hawking
the error --
perhaps because the problem doesn't exist in context or perhaps
because I didn't manage to reproduce/add the needed hyphenation
patterns.
if it relates to patterns, then using \discretionary{}{}{} with
something in it should also fail .. maybe it eventually becomes some
disc node at th
--
perhaps because the problem doesn't exist in context or perhaps
because I didn't manage to reproduce/add the needed hyphenation
patterns.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your questi
an.
>
>> Den 13. apr. 2017 kl. 22.10 skrev Hans Hagen <pra...@wxs.nl
>> <mailto:pra...@wxs.nl>>:
>>
>> On 4/13/2017 9:37 PM, Florian Grammel wrote:
>>> The \hyphenation{}-command is ignored in the texlive 2016 version (ver:
>>> 2016.05.17 1
}
on the standalone (last word in the margin) to TL16 (properly hyphenated)
Can this be fixed?
Best
Florian.
> Den 13. apr. 2017 kl. 22.10 skrev Hans Hagen <pra...@wxs.nl>:
>
> On 4/13/2017 9:37 PM, Florian Grammel wrote:
>> The \hyphenation{}-command is ignored in the texl
On 4/13/2017 9:37 PM, Florian Grammel wrote:
The \hyphenation{}-command is ignored in the texlive 2016 version (ver:
2016.05.17 19:20 MKIV). This has obviously been fixed since, as it works in the
standalone.
For other reasons I’d prefer to keep working with the TL16-version
The \hyphenation{}-command is ignored in the texlive 2016 version (ver:
2016.05.17 19:20 MKIV). This has obviously been fixed since, as it works in the
standalone.
For other reasons I’d prefer to keep working with the TL16-version -- is it
possible to patch the hyphenation easily in TL 16
blank line between paragraphs
>>
>> \version[temporary]% show overful hboxes
>>
>> \startcolumns[n=4, distance=3em]
>> (English hyphenation)
>>
>> Önundur hét maður. Hann var Ófeigsson burlufóts Ívarssonar beytils.
>> Önundur var bróðir Guðbjar
paragraphs
\version[temporary]% show overful hboxes
\startcolumns[n=4, distance=3em]
(English hyphenation)
Önundur hét maður. Hann var Ófeigsson burlufóts Ívarssonar beytils.
Önundur var bróðir Guðbjargar, móður Guðbrands kúlu, föður Ástu, móður
Ólafs konungs hins helga. Önundur var upplenskur
inface] [rm] [Palatino Linotype]
\setupbodyfont[mainface,10pt]
\setupwhitespace[big] % blank line between paragraphs
\version[temporary]% show overful hboxes
\startcolumns[n=4, distance=3em]
(English hyphenation)
Önundur hét maður. Hann var Ófeigsson burlufóts Ívarssonar beytils. Önund
The Icelandic hyphenation and language settings, though present in the
installation (lang-is.lua), don’t seem to work on ConTeXt ver: 2016.05.17
19:20 MKIV current fmt: 2017.3.21
I’ve tried both \language[is] / \language[icelandic] and \mainlanguage[is] but
the result is identical to English
t; - We added a build_page_insert callback for inserts so that one can
> for instance adapt
> spacing on demand.
>
> - On the agenda has been some more control over word start and end in
> hyphenation and
> this is now possible via hyphenationbounds. We also updated the
>
.
- On the agenda has been some more control over word start and end in
hyphenation and
this is now possible via hyphenationbounds. We also updated the
manual with some more
details.
- An old tracker item with respect to control over spacing around math
was revived and
has resulted in mathsurroundmode
On 11/20/2016 6:17 PM, Rik Kabel wrote:
On 2016-11-20 11:51, Rik wrote:
On 2016-11-20 05:52, Hans Hagen wrote:
On 11/20/2016 3:39 AM, Rik wrote:
On 2016-11-19 20:58, Rik Kabel wrote:
Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs
show the same font files and typescript
On 2016-11-20 11:51, Rik wrote:
On 2016-11-20 05:52, Hans Hagen wrote:
On 11/20/2016 3:39 AM, Rik wrote:
On 2016-11-19 20:58, Rik Kabel wrote:
Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs
show the same font files and typescript files.
Sorry, I did not mean to say
On 2016-11-20 05:52, Hans Hagen wrote:
On 11/20/2016 3:39 AM, Rik wrote:
On 2016-11-19 20:58, Rik Kabel wrote:
Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs
show the same font files and typescript files.
Sorry, I did not mean to say the same files, but files identical
On 11/20/2016 3:39 AM, Rik wrote:
On 2016-11-19 20:58, Rik Kabel wrote:
Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs
show the same font files and typescript files.
Sorry, I did not mean to say the same files, but files identical in
content. The TL files are all from
On 2016-11-19 20:58, Rik Kabel wrote:
Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs
show the same font files and typescript files.
Sorry, I did not mean to say the same files, but files identical in
content. The TL files are all from the TL directory. The standalone
\input zapf \par
\input zapf \par
\input zapf \par
\input zapf \par
\stoptext
Bug, or error on my part?
Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs
show the same font files and typescript files.
--
Rik
ile to put back the discretionary_code
>> argument, the output is same with new beta.
>
> Hi Joseph,
>
> French hyphenation is unknown to me, but I have a different approach.
When messing with disc nodes one can argue if some of then need to
become discretionary nodes or keep their other type. Th
,
French hyphenation is unknown to me, but I have a different approach.
When messing with disc nodes one can argue if some of then need to
become discretionary nodes or keep their other type. This change keeps
it more original (of course one can argue about it) which has some
consequence
On 10/13/2016 11:56 AM, josephcan...@gmail.com wrote:
> Apparently this difference comes from this change in font-ots.lua near
> line 603. If I edit the file to put back the discretionary_code
> argument, the output is same with new beta.
Hi Joseph,
French hyphenation is unknown to
6 19:12:30
Objet: Re: [NTG-context] Hyphenation on apostrophe and proper noun
Bonjour Jean-Pierre,
excellent ! Votre solution corrige le problème de l'apostrophe.
Toutefois j'ai rencontré un message d'erreur avec la commande :
\mainlanguage[fr]
Est-ce la version de ConTeXt que j'utilis
with the \mainlanguage [fr]
Is the version of ConTeXt I use? (ConTeXt worm: 2016.05.17 7:20 p.m.
MKIV current fmt: 2016.8.29 int: English / English)
But removing this command, the hyphenation works well.
If I could manage the proper noun, it would be even better.
Thanks again !
Alain Auger
Le 16-09-30 à 12:29
) :
\setuplanguage[fr][patterns={fr,agr}]
\mainlanguage[fr]
\setcharacterspacing[frenchpunctuation]
- Mail original -
De: "Alain Auger" <aau...@diffusionvie.com>
À: ntg-context@ntg.nl
Envoyé: Vendredi 30 Septembre 2016 15:45:53
Objet: [NTG-context] Hyphenation on apostrophe and pr
Dear list,
There is a way to prevent hyphenation to occur on a apostrophe "L'-...",
and also on proper noun?
\language[fr]
\setcharacterspacing[frenchpunctuation]
\setupalign[stretch,verytolerant]
---
L’un des critiques, Dean Farrar, écrivit : « L’-
histoire n’a jamais entendu p
nfiguration.
\definebreakpoints[hyphen]
\definebreakpoint [hyphen] [-] [nleft=3,nright=3,type=6,range=yes]
\setbreakpoints[hyphen]
>
> to the preamble of your documents, and you get both hyphenation and ma
|-|.
Just add
\setbreakpoints[compound]
to the preamble of your documents, and you get both hyphenation and
margin kerning, no need for |-|.
Thomas
___
If your question is of interest to others as well, please add
---
\showframe
\setuppapersize[A6][A6]
\definefontfeature
[default][default]
[protrusion=quality]
\setupalign[hanging]
\starttext
% this is margin kerned
Hyphenation of compound words is non-trivial
% this should be margin kerned but isn't
Hyphenation of compound words is non|-|trivial
% this does
Dear list,
when writing compound words I want the second part to be eligible for
hyphenation to avoid bad breaks. Therefore, instead of »non-trivial« I write
»non|-|trivial«. However, I noticed that when I make dash compound aware it is
no longer kerned into the margin. MWE is below. How
of \quad.
3) The underline should allow for line breaks and hyphenation, but not such
that only empty space is broken into the next line of left in the previous (see
MNWE).
In this way, the student’s and teacher’s versions of the script will look
exactly the same, except for the visible solution
for line breaks and hyphenation, but not such
that only empty space is broken into the next line of left in the previous (see
MNWE).
In this way, the student’s and teacher’s versions of the script will look
exactly the same, except for the visible solution in the teacher’s version.
The macro
given by Wolfgang for paired boxes with align
footnotes through French language commands. And I have substitute 2
French texts to 'Content' (after removing previous \input tufte and
\input ward), and fill the tables titles with my own. All is fine,
except hyphenation which seems to be an issu
texts to 'Content' (after removing previous \input tufte and
\input ward), and fill the tables titles with my own. All is fine,
except hyphenation which seems to be an issue here : see in the first
text the word 'automatiquement'.
The missing hyphentation has nothing to do with floats, foo
),
and fill the tables titles with my own. All is fine, except hyphenation
which seems to be an issue here : see in the first text the word
'automatiquement'.
I have added the following commands :
\mainlanguage[fr]
\setcharacterspacing[frenchpunctuation]
\defineparagraphs[n=1, align={hz,hanging
\input
tufte and \input ward previously given), and fill the tables titles
with words of my own. All is fine, except hyphenation which doesn't
appear here.
\mainlanguage[fr]
\setcharacterspacing[frenchpunctuation]
\defineparagraphs[n=1, align={hz,hanging}]
\setupalign[hyphenated]
You m
with words of
my own. All is fine, except hyphenation which doesn't appear here.
\mainlanguage[fr]
\setcharacterspacing[frenchpunctuation]
\defineparagraphs[n=1, align={hz,hanging}]
\setupalign[hyphenated]
You may try with this text (in place of 'Content') :
« Dans la société présente, où le jeu de
well. I found no more hyphenation issues, nor punctuation ones, even
within text defined by \definefallbackfamily setup.
\setuplanguage[fr][patterns={fr,agr}]
\mainlanguage[fr]
\setcharacterspacing[frenchpunctuation]
Le 09/08/2016 à 23:21, josephcan...@gmail.com a écrit :
Dear all,
Combining
On 8/10/2016 2:15 PM, Arthur Reutenauer wrote:
I see:
languages > initialization > language 'fr', patterns 'agr,fr',
discarding conflict (0-9)'(0-9)
so, the ' is used differently between the languages
As I remember, French has 2'2 while Ancient Greek has 8'8 which are
not exactly
> I see:
>
> languages > initialization > language 'fr', patterns 'agr,fr',
> discarding conflict (0-9)'(0-9)
>
> so, the ' is used differently between the languages
As I remember, French has 2'2 while Ancient Greek has 8'8 which are
not exactly contradictory ;-) We could of course
nguage[fr]
\starttext
\hyphenatedword{l'homme}
\stoptext
-
The above prints : l’-homme
If so, what is the alternative to specify hyphenation in a text
containing both french and ancient greek (the minority) words.
Thanks a lot for advising,
Best regards
Joseph
/English
\setuplanguage[fr][patterns={fr, agr}]
\mainlanguage[fr]
\starttext
\hyphenatedword{l'homme}
\stoptext
-
The above prints : l’-homme
If so, what is the alternative to specify hyphenation in a text containing both
french and ancient greek (the minority) words.
Thanks
On 08/08/2016 05:41 PM, luigi scarso wrote:
> Il 08/ago/2016 17:28, "Pablo Rodriguez" ha scritto:
>>
>> Dear Luigi,
>>
>> would it be possible to have version 0.98.0 binaries in the linux
>> (32bit) platform for ConTeXt Standalone?
>>
>&g
Il 08/ago/2016 17:28, "Pablo Rodriguez" <oi...@gmx.es> ha scritto:
>
> Dear Luigi,
>
> would it be possible to have version 0.98.0 binaries in the linux
> (32bit) platform for ConTeXt Standalone?
>
> This may fix a nasty bug with US English hyphenation.
>
&g
Dear Luigi,
would it be possible to have version 0.98.0 binaries in the linux
(32bit) platform for ConTeXt Standalone?
This may fix a nasty bug with US English hyphenation.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
On 7 August 2016 at 10:44, Pablo Rodriguez wrote:
> Dear ConTeXt maintainers,
>
> would it be possible that ConTeXt Standalone for the linux platform had
> the latest LuaTeX binaries?
>
> Besides the update, I think it is important to confirm whether English
> hyphenation i
Dear ConTeXt maintainers,
would it be possible that ConTeXt Standalone for the linux platform had
the latest LuaTeX binaries?
Besides the update, I think it is important to confirm whether English
hyphenation is fixed in the latest binary.
The following sample:
\starttext
hy I asked you to test the Linux 32bit ConTeXt Standalone
with hyphenation.)
Create a new directory in in your /home/ directory and there you can
download and update the latest beta.
This won’t break your existing TL 2016 installation. And so you can have
the latest source and you may even use it.
I use the
nations. [...]
Hi Henri,
could you try the hyphenation with ConTeXt Standalone for 32bit?
The issue might be related to 32bit architecture.
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as w
On 08/01/2016 06:13 PM, Pablo Rodriguez wrote:
> On 08/01/2016 02:39 PM, Ulrike Fischer wrote:
>> Am Mon, 01 Aug 2016 11:52:11 +0200 schrieb Wolfgang Schuster:
>>
>>> The wrong hyphenation happens also with the default font.
>>>
>>> %\startexceptions[e
On 1 Aug 2016, at 14:40 , Hans Hagen <pra...@wxs.nl>
> To: ntg-context@ntg.nl
> Subject: Re: [NTG-context] Hyphenation errors (again or still) in
> recent mkiv
> Message-ID: <d887e5a3-1195-b141-623f-897f7540f...@wxs.nl>
> Content-Type: text/plain; charset=utf-8
On 08/01/2016 02:39 PM, Ulrike Fischer wrote:
> Am Mon, 01 Aug 2016 11:52:11 +0200 schrieb Wolfgang Schuster:
>
>> The wrong hyphenation happens also with the default font.
>>
>> %\startexceptions[en]
>> %would syn-the-size enu-mer-ate
>> %\stopexceptions
.
hyphenator |
mtx-patterns| us 3 3 : schematic : schematic
I used an online hyphenation tool (English US) because it’s too tricky
for me too!
Using English UK the words maintenance and integrated are indeed
correctly hyphenated. So I jumped to conclusions there.
What remains
| 1m0a0 0 2 0 2 2 0 0 0 0 0
hyphenator |0a0t1i0c0 0 2 0 2 2 0 0 1 0 0
hyphenator | .0s2c0h2e2m0a0t1i0c0. . s c h e m a t-i c .
hyphenator |
mtx-patterns| us 3 3 : schematic : schematic
I used an online hyphenation tool (English US) because it’s
Am Mon, 01 Aug 2016 11:52:11 +0200 schrieb Wolfgang Schuster:
> The wrong hyphenation happens also with the default font.
>
> %\startexceptions[en]
> %would syn-the-size enu-mer-ate
> %\stopexceptions
>
> \starttext \hsize=1mm
> would synthesize enumerate
On 1 Aug 2016, at 12:00 , Hans Hagen <pra...@wxs.nl>
>>>
>>> On 7/31/2016 12:57 PM, Robert Blackstone wrote:
>>>> Dear all,
>>>>
>>>> In the setupfile of my project I have \mainlanguage[en]. The font used is
>>>> Verda
font[Verdana]
\setupbodyfont[10pt]
\contextversion
\showgrid
\starttext
\input knuth
\medskip
\input tufte
\stoptext
The wrong hyphenation happens also with the default font.
%\startexceptions[en]
%would syn-the-size enu-mer-ate
%\stopexceptions
\starttext \hsize=1mm
would synthesize enumera
on
\showgrid
\starttext
\input knuth
\medskip
\input tufte
\stoptext
The wrong hyphenation happens also with the default font.
%\startexceptions[en]
%would syn-the-size enu-mer-ate
%\stopexceptions
\starttext \hsize=1mm
would synthesize enumerate
\stopte
r 2015 the hyphenation of English words was
always correct.
The same files compiled with mkiv of july 2016 (version 2016.07.18 16;26) give
hyphenations that are definitely wrong.
Some examples: begi-nning, pr-ocedure, adequ-ately, st-yle
I made some tests with Linux Libertine sans and here also the e
On 31 Jul 2016, at 21:06 , Hans Hagen <pra...@wxs.nl>
>
> On 7/31/2016 12:57 PM, Robert Blackstone wrote:
>> Dear all,
>>
>> In the setupfile of my project I have \mainlanguage[en]. The font used is
>> Verdana.
>> With mkiv versions till oct
On 8/1/2016 9:22 AM, Jan Willem Flamma wrote:
Hi Pablo,
I wasn’t aware of the \hyphenatedword feature. Thanks for sharing.
I used an online hyphenation tool (English US) because it’s too tricky for me
too!
Using English UK the words maintenance and integrated are indeed correctly
hyphenated
tor | .0s2c0h2e2m0a0t1i0c0. . s c h e m a t-i c .
hyphenator |
mtx-patterns| us 3 3 : schematic : schematic
I used an online hyphenation tool (English US) because it’s too tricky for me
too!
Using English UK the words maintenance and integrated are indeed correctly
hyphenated. So I jum
Hi Pablo,
I wasn’t aware of the \hyphenatedword feature. Thanks for sharing.
I used an online hyphenation tool (English US) because it’s too tricky for me
too!
Using English UK the words maintenance and integrated are indeed correctly
hyphenated. So I jumped to conclusions there.
What remains
d integrated
beginning procedure adequately style}
\uk\hyphenatedword{schematic, maintenance and integrated
beginning procedure adequately style}
\stoptext
Sorry, but English hyphenation is too tricky for me.
Just in case it helps,
Pablo
--
http://
bert Blackstone wrote:
>> Dear all,
>>
>> In the setupfile of my project I have \mainlanguage[en]. The font used is
>> Verdana.
>> With mkiv versions till october 2015 the hyphenation of English words was
>> always correct.
>>
>> The same
On 7/31/2016 12:57 PM, Robert Blackstone wrote:
Dear all,
In the setupfile of my project I have \mainlanguage[en]. The font used is
Verdana.
With mkiv versions till october 2015 the hyphenation of English words was
always correct.
The same files compiled with mkiv of july 2016 (version
Dear all,
In the setupfile of my project I have \mainlanguage[en]. The font used is
Verdana.
With mkiv versions till october 2015 the hyphenation of English words was
always correct.
The same files compiled with mkiv of july 2016 (version 2016.07.18 16;26) give
hyphenations
anquille !}}
>
> You may also (in the above example) replace « fleuve » by « fleu||ve » in
> order to get a hyphenation.
>
> Best regards: OK
>
> > On 15 Jul 2016, at 16:19, Fabrice Couvreur <fabrice1.couvr...@gmail.com>
> wrote:
> >
> > Hi Wolfgang,
>
Hi Fabrice,
You can give an option to \framed, as in:
\placerecipe{}{\framed[align=justify,offset=2pt]{La vie n'est pas un long
fleuve tranquille !}}
You may also (in the above example) replace « fleuve » by « fleu||ve » in order
to get a hyphenation.
Best regards: OK
> On 15 Jul 2
vironment even in MkII? I thought there
>> were translated labels for Farsi somewhere.
>> 2) In the following MWE, ad-hoc hyphenation using \- works and leads to
>> hyphenation. However, specifying the pattern at the beginning does not
>> have any effect. Am I m
an/fa or anything like
> that but it has several arabic variants. was this dropped in MkIV or was
> there never a persian language environment even in MkII? I thought there
> were translated labels for Farsi somewhere.
> 2) In the following MWE, ad-hoc hyphenation using \- wo
riants. was this dropped in
MkIV or was there never a persian language environment even in MkII?
I thought there were translated labels for Farsi somewhere.
2) In the following MWE, ad-hoc hyphenation using \- works and leads
to hyphenation. However, specifying the pattern at the beginning does
not ha
in MkII? I thought there
were translated labels for Farsi somewhere.
2) In the following MWE, ad-hoc hyphenation using \- works and leads to
hyphenation. However, specifying the pattern at the beginning does not
have any effect. Am I missing something?
\usemodule[simplefonts]
\setmainfont[dejavusans
On 07/01/2016 01:59 AM, Hans Hagen wrote:
> On 6/30/2016 8:15 PM, Pablo Rodriguez wrote:
>> [...]
>> Is this a bug or is there no way to load French and ancient Greek
>> hyphenation patterns?
>
> it's not a bug ... the patterns conflict ... it took me a while but
(or with stable from 2015.05.18 12:26).
The error message reads:
error on line 2 in file a.tex: ! Conflicting pattern ignored
Is this a bug or is there no way to load French and ancient Greek
hyphenation patterns?
it's not a bug ... the patterns conflict ... it took me a while but the
next beta
with latest beta (or with stable from 2015.05.18 12:26).
>
> The error message reads:
>
>error on line 2 in file a.tex: ! Conflicting pattern ignored
>
> Is this a bug or is there no way to load French and ancient Greek
> hyphenation patterns?
&
message reads:
error on line 2 in file a.tex: ! Conflicting pattern ignored
Is this a bug or is there no way to load French and ancient Greek
hyphenation patterns?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
to add such option
> but do not have enough knowledge in nodes manipulation in luatex,
> especially those related to hyphenation. Would it be very difficult to
> add such option please ?
depends on what one finds 'difficult' ... by now i can probably do most
i want at that level in which
in nodes manipulation in luatex,
especially those related to hyphenation. Would it be very difficult to
add such option please ?
depends on what one finds 'difficult' ... by now i can probably do most
i want at that level in which difficult is replace by 'just takes time';
also, one needs to keep
those related to hyphenation. Would it be
very difficult to add such option please ?
I post a MWE showing some extreme non real non sensible case, to double check
that hyphenation is never performed.
\definefirstline[FirstLine][alternative=line, style=\tfd] % exegerate size
\starttext
c should be preferred.
>
> There are two layers, actually (at least in LaTeX; not sure how much
> of this is reproduced in ConTeXt): 1. Spelling conventions, 2. Hyphenation.
> For the latter, a classification by historical periods clearly makes no
> sense, but there is some trut
lassical or ancient vs. modern are misleading
> adjectives when referred to Latin.
>
> In my opinion, etymological or phonetic vs. syllabic should be preferred.
There are two layers, actually (at least in LaTeX; not sure how much
of this is reproduced in ConTeXt): 1. Spelling conv
ai 2016 15:13:16
Objet: Re: [NTG-context] LaTeX reledmac: what about ConTeXt ?
> But aren’t \la and \ala synonyms?
They are two variants of Latin with completely different sets of
hyphenation patterns: the original one, activated by \la, is about
twenty years old, targets a "modern"
> But aren’t \la and \ala synonyms?
They are two variants of Latin with completely different sets of
hyphenation patterns: the original one, activated by \la, is about
twenty years old, targets a "modern" spelling of Latin (characterised
principally by a u/v and i/j distinction), a
ght 2014 Claudio Beccari
% [classical latin hyphenation patterns]
%
% -
% IMPORTANT NOTICE:
%
% This program can be redistributed and/or modified under the terms
% of the LaTeX Project Public License Distributed from CTAN
% a
ng for through CTX doc and never found.
3. I understand why I have to load either 'agr' ith 'la' pattern.
You may also consider ala
lang-ala.rme:
% generated by mtxrun --script pattern --convert
%
% ** hyph-la-x-classic.tex *
%
% Copyright 2014 Claudio Beccari
%
Copyright 2014 Claudio Beccari
% [classical latin hyphenation patterns]
%
% -
% IMPORTANT NOTICE:
%
% This program can be redistributed and/or modified under the terms
% of the LaTeX Project Public License Distributed from CTAN
or -halt-on-error "untitled-3.tex"
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (MiKTeX 2.9 64-bit)
entering extended mode
(untitled-3.tex
LaTeX2e <2015/10/01> patch level 2
Babel <3.9n> and hyphenation patterns for 69 languages loaded.
untitled-3.tex:2: Undefined control s
fTeX, Version 3.14159265-2.6-1.40.16 (MiKTeX 2.9 64-bit)
entering extended mode
(untitled-3.tex
LaTeX2e <2015/10/01> patch level 2
Babel <3.9n> and hyphenation patterns for 69 languages loaded.
untitled-3.tex:2: Undefined control sequence
untitled-3.tex:2: ==> Fatal error occurr
ode into \stopnotmode.
context did not complain for that mismatch,
but --mode=Info made the \mainlanguage[it] ignored,
because \startnotmode[Info] was not closed.
Everything else seemed to work just fine, and the missing
italian hyphenation looked like a mistery.
Before that I used \doifmode{I
I apologize for the noise.
\mainlanguage[it] before \starttext solves the problem.
> Hello list,
> I'm typesetting XHTML italian text with Context (version 4/4/16).
>
> I've put a \language[it] just after \starttext, but I get words
> with a wrong hyphenation.
>
> A
Hello list,
I'm typesetting XHTML italian text with Context (version 4/4/16).
I've put a \language[it] just after \starttext, but I get words
with a wrong hyphenation.
As a patch, I just put \language[it] at the beginning of the xmlsetup
that processes the tag, and now words are hyphenated
is still too short:
because there is more involved, like hyphenation, badness of other
lines, etc ... after all it is stretch, not absolute
i'm not going to waste time too much on figuring out some heuristic that
works in one case but not in the other
\starttext
\hsize 15.37cm
\input tufte
of the aspects ... so, your last line + following first line might look
okay (according to whatever rules and criteria) but then, as you also
need to increase the tolerance and enable stretch to permit that
solution to be found, the rest might look like crap
it's the same for successive hyphenation
" but don't know how to fix this.
Warnings fron pdftex will dissapear when you switch to MkIV :-).
"Underfull \hbox" may be caused by wrong hyphenation?
Would it be possible that you were compiling a German (or non-English text)?
In such case, please add "\mainlanguage[de]&qu
on't know how to fix this.
Warnings fron pdftex will dissapear when you switch to MkIV :-).
"Underfull \hbox" may be caused by wrong hyphenation?
Would it be possible that you were compiling a German (or non-English text)?
In such case, please add "\mainlanguage[de]" i
it.
> and what is meant with bad boxes? i read "Underfull \hbox (badness
> 1) in paragraph..." but don't know how to fix this.
Warnings fron pdftex will dissapear when you switch to MkIV :-).
"Underfull \hbox" may be caused by wrong hyphenation?
Would it be possible that you
401 - 500 of 1768 matches
Mail list logo
