an interesting
book simply because there is that inconsistent (letter)spacing and
stretching combined with avoiding hyphenation going on (ok, th ebenefit
is that my reading backlog grows a bit slower)
I do not know about others, but I find it extremely difficult to read
newspapers (or much anything else
On 2/6/2016 9:19 PM, Alan BRASLAU wrote:
ConTeXt has troubles hyphenating chemical names, which in organic
chemistry can be funny things such as
N-(4-n-alkoxybenzylidene)-4’-alkylaniline.
The names can get much worse...
The rules for hyphenating in chemistry are well defined. Without
putting
ConTeXt has troubles hyphenating chemical names, which in organic
chemistry can be funny things such as
N-(4-n-alkoxybenzylidene)-4’-alkylaniline.
The names can get much worse...
The rules for hyphenating in chemistry are well defined. Without
putting specific hyphenating hints into the names
On 2/5/2016 8:47 AM, Pablo Rodriguez wrote:
On 02/04/2016 10:13 PM, Hans Hagen wrote:
On 2/4/2016 9:27 PM, Pablo Rodriguez wrote:
[...]
The ff-ligature prevents hyphenation with TeX Gyre Pagella, but not with
MinionPro. (This is the opposite of what I reported before.)
it depends
On 2/4/2016 9:27 PM, Pablo Rodriguez wrote:
On 02/03/2016 02:18 PM, Hans Hagen wrote:
On 2/2/2016 12:28 PM, Pablo Rodriguez wrote:
Dear list,
[...]
Hyphenation is wrong with fonts that don’t come with the ConTeXt
distribution. TeX Gyre Pagella is hyphenated right, but MinionPro or
even TeX
On 02/04/2016 10:13 PM, Hans Hagen wrote:
> On 2/4/2016 9:27 PM, Pablo Rodriguez wrote:
>> [...]
>> The ff-ligature prevents hyphenation with TeX Gyre Pagella, but not with
>> MinionPro. (This is the opposite of what I reported before.)
>
> it depends on the compl
On 02/03/2016 02:18 PM, Hans Hagen wrote:
> On 2/2/2016 12:28 PM, Pablo Rodriguez wrote:
>> Dear list,
>> [...]
>> Hyphenation is wrong with fonts that don’t come with the ConTeXt
>> distribution. TeX Gyre Pagella is hyphenated right, but MinionPro or
>> eve
On 2/2/2016 12:28 PM, Pablo Rodriguez wrote:
Dear list,
just accidentally I discovered the following issue:
\definefontfamily[mainface][rm][MinionPro]
\definefontfamily[anotherface][rm][TeX Gyre Pagella]
% wrong hyphenation too with TeX Gyre Pagella Math
\setupbodyfont
to me that I was mistaken in my
initial supposition that the problem was related to the importing
mechanism of a separate file containing the exceptions' list. The
difficulty seems now to lie deeper into the hyphenation machinery itself.
I would be glad if it could be of any help to solve it.
fixed
supposition that the problem was related to the importing mechanism
of a separate file containing the exceptions' list. The difficulty seems
now to lie deeper into the hyphenation machinery itself.
I would be glad if it could be of any help to solve it.
Kind regards
Francisco
mis-hyph.7z
Description
On 1/27/2016 1:18 PM, Francisco Gracia wrote:
This is to report a problem I am presently experiencing with Context.
The symptom is that the contents of an hyphenation list, implemented as
an outstanding file, I use for typesetting a lating text are no longer
taken into account when performing
This is to report a problem I am presently experiencing with Context.
The symptom is that the contents of an hyphenation list, implemented as an
outstanding file, I use for typesetting a lating text are no longer taken
into account when performing the hyphenation operations.
This happens
hyphenation. You could inject just a \nzwj .
Btw, keep in mind that in context this kind of manipulations happens in
ways that don't interfere too much with macro expansion and other trickery.
Hans
> I have no clue what a package is supposed to do but any solution has to come
> up with a list if words.
I think the point is that often in German, breakpoints for hyphenation
also break ligatures. I mentioned that in Nasbinals.
Best,
think the point is that often in German, breakpoints for hyphenation
also break ligatures. I mentioned that in Nasbinals.
Best,
Arthur
The guts of the selnolig package just call \hyphenation{...}:
http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/luatex/latex/selnolig/se
On 19 January 2016 at 09:05, Arthur Reutenauer
<arthur.reutena...@normalesup.org> wrote:
>> I have no clue what a package is supposed to do but any solution has to come
>> up with a list if words.
>
> I think the point is that often in German, breakpoints for hyphenatio
> The guts of the selnolig package just call \hyphenation{...}:
> http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/luatex/latex/selnolig/selnolig-english-hyphex.sty
That's not the core part of the package, it just sets a list of
hyphenation exceptions (that's what \hyphenatio
I think the point is that often in German, breakpoints for hyphenation
>> also break ligatures. I mentioned that in Nasbinals.
>>
>> Best,
>>
>> Arthur
>
> The guts of the selnolig package just call \hyphenation{...}:
> http://anorien.csc.wa
ard (from i to f) ... as all is
technically possible/permitted nothing is a bug (but there might be
occasional differences between hyphenation although quite some effort
went into getting that kind of right ... and it makes a good topic for
complex hard to follow boring presentations (see attachm
ing to terminal (a matter of taste)
- the (current) lc codes are now saved with the (current) language when
patterns are
loaded unless one hs used \hjcode instead of \lccode; overloading of
\hjcodes is
possible (but of course goes ahead of hyphenation which is delayed till
parbuild
ted?
Replying to myself, there is no bug in hyphenmin. The Spanish patterns
don’t add "bue-no" (I haven’t asked yet, but I guess this is to avoid
starting a line with a negative particle). I have to add an hyphenation
exception.
But there is an issue with hyphenmin shown in
On 2015-11-09 07:34, Thomas A. Schmitz wrote:
On 11/09/2015 08:42 AM, Christoph Reller wrote:
MWE:
\setuptagging[state=start] %<- correct when commenting this line
\starttypescript[sans][myfont]
\definefontsynonym[Sans][file:MyriadPro-Regular]
\stoptypescript
On 11/09/2015 08:42 AM, Christoph Reller wrote:
MWE:
\setuptagging[state=start] %<- correct when commenting this line
\starttypescript[sans][myfont]
\definefontsynonym[Sans][file:MyriadPro-Regular]
\stoptypescript
\definetypeface[Body][ss][sans][myfont]
\setupbodyfont[Body,ss,10pt]
\starttext
Hi,
I have a strange behavior with the latest beta:
- OpenType Font "Myriad"
- Tagging enabled
Result: Hyphenation is not working, i.e., the hyphens disappear.
Example output correct (when disabling tagging):
[...] If I had not partici-
pated fully [...]
Example output defect (whe
or
even Auf|*|lage. However, I typeset from xml and would much rather have
a general solution so I can leave my generated xml files alone.
Something like a list where I could list "ligature exceptions" the way
we have a file with hyphenation exceptions. Is anything like this possible
prevent a ligature with something like Auf\/lage or even
Auf|*|lage. However, I typeset from xml and would much rather have a general
solution so I can leave my generated xml files alone. Something like a list
where I could list "ligature exceptions" the way we have a file with
h
this. It is from
ConTeXt MKII. Next, modify the definefontfeature and definefontfamily commands
as shown. (The default features for the font are in the file
type-imp-ebgaramond.mkiv.) That should be it to get started.
\language[fr] % french hyphenation
\definefontfeature[myfeatures][ss02=yes,cv01=yes
. However, I typeset from xml and would much rather
have a general solution so I can leave my generated xml files alone.
Something like a list where I could list "ligature exceptions" the way
we have a file with hyphenation exceptions. Is anything like this
possible?
Take a look
and
definefontfamily commands as shown. (The default features for the font
are in the file type-imp-ebgaramond.mkiv.) That should be it to get started.
\language[fr] % french hyphenation
*\definefontfeature[myfeatures][ss02=yes,cv01=yes,cv03=yes,ss05=yes,cv91=yes]*
*\definefontfamily[mainfont][serif
On 09/23/2015 05:45 PM, Andres Conrado wrote:
> [...]
> This maybe is not very important to you, but, as a designer, I see
> \ConTeXt as a logotype, so, it's not supposed to be hyphenated.
Hi Andrés,
\ConTeXt is also a word and sometimes hyphenation is required:
%~ \def\ConTeXt{
On 09/22/2015 01:53 PM, Hans Hagen wrote:
> On 9/21/2015 9:44 PM, Pablo Rodriguez wrote:
>> [...]
>> Sorry, Hans, but I’m afraid I don‘t get it.
>>
>> The issue is that hyphenation takes place even when nothyphenated should
>> prevent it.
>>
On 9/21/2015 9:44 PM, Pablo Rodriguez wrote:
On 09/21/2015 06:55 PM, Hans Hagen wrote:
On 9/13/2015 7:59 PM, Pablo Rodriguez wrote:
\def\abc{Con\-\TeX{}t}
\hyphenation{Con-TeXt}
\starttext
\startTEXpage[offset=1em, align={right, nothyphenated}]
\hyphenatedword
On 9/13/2015 7:59 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\def\abc{Con\-\TeX{}t}
\hyphenation{Con-TeXt}
\starttext
\startTEXpage[offset=1em, align={right, nothyphenated}]
\hyphenatedword{legibility}\\
\hyphenatedword{\abc}\\
\abc
On 09/21/2015 06:55 PM, Hans Hagen wrote:
> On 9/13/2015 7:59 PM, Pablo Rodriguez wrote:
>>
>> \def\abc{Con\-\TeX{}t}
>> \hyphenation{Con-TeXt}
>> \starttext
>> \startTEXpage[offset=1em, align={right, nothyphenated}]
>> \hyphenatedwor
Dear list,
I have the following sample:
\def\abc{Con\-\TeX{}t}
\hyphenation{Con-TeXt}
\starttext
\startTEXpage[offset=1em, align={right, nothyphenated}]
\hyphenatedword{legibility}\\
\hyphenatedword{\abc}\\
\abc\\
\hyphenatedword{\ConTeXt}
\stopTEXpage
other letters.
more in conjunction with hyphenation
Can somebody else reproduce the problem. For the record, this is running
on Windows 10 Pro 64-bit.
The problem document:
\definefontfeature [ff:ebg][default][
clig=yes,hlig=yes, %% 1
I guess that there is no built-in functionality of semantical
switching between ligatures and normal characters.
The official way to do this is:
\starttext
shel\noligature{ff}ul
\stoptext
which also preserves hyphenation and kerning as well as other tricky
features that a font provides
\noligature{ff}ul
\stoptext
which also preserves hyphenation and kerning as well as other tricky
features that a font provides.
The best place to incorporate such a feature is in the hyphenator but I
have no time now to do that. So, instead I added a few lines to an
existing (probably unknown
Hi,
In the code below, how to make the line hyphenation is in the first column and
not in the second.
Thank You.
Fabrice
\setupcolors[state=start]
\definemixedcolumns
[mycolumn]
[
n=2,
separator=rule,
rulecolor=gray,
rulethickness=1pt,
balance=yes,
]
\setuppapersize[A4
On 07/30/2015 07:37 PM, Fabrice Couvreur wrote:
Hi,
In the code below, how to make the line hyphenation is in the first
column and not in the second.
Hi Fabrice,
you could replace \column with \column\setupalign[nothyphenated].
It does the job, although it seems not very elegant to me
Fabrice Couvreur mailto:fabrice1.couvr...@gmail.com
30. Juli 2015 19:37
Hi,
In the code below, how to make the line hyphenation is in the first
column and not in the second.
You can add
\setuptolerance[verytolerant]
to give ConTeXt more freedom where it breaks the lines.
Wolfgang
Am 25.07.2015 um 17:36 schrieb Pablo Rodriguez:
I guess it should be something related to the font cache. Try:
mtxrunjit --script fonts --reload
BTW, I would add \mainlanguage[deo] to improve the hyphenation.
Thanks a lot. Now it works.
juh
your sample with contextjit from latest beta (released
2015.07.24 13:58) and font is included.
I guess it should be something related to the font cache. Try:
mtxrunjit --script fonts --reload
BTW, I would add \mainlanguage[deo] to improve the hyphenation.
I hope it helps,
Pablo
\startbuffer
On 7/20/2015 6:49 PM, Pablo Rodriguez wrote:
Hans,
I have the following sample (it includes Lua code for underscore
hyphenation):
\startluacode
function document.addfunnyhyphen(tfmdata)
local underscore = utf.byte(_)
local char = tfmdata.characters
at the the second one for \variant, or the counter (and
still don’t fully understand it). Thanks again.
Dear Talal,
well, both macros come from Hans... I’m afraid I’m not smart enough for
that code ;-).
BTW, I just accidentally discovered a possible fix for the hyphenation
issue (although I’m not sure
].
\stoplinenumbering
\stoptext
It seems that locating \prewordbreak before the text to be hyphenated
(and not after it) enables hyphenation in body.
Is this a bug or is it actually the way \prewordbreak should work?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
\normalexpanded{\doVariant{Varia:\countvariants}}}
\starttext
\startlinenumbering
\dorecurse{20}{\variant{donald e knuth}{herman zapf} }
\stoplinenumbering
\stoptext
BTW, it has a “minor issue”: hyphenation doesn’t work in the body text
It works fine in the notes. I
:\countvariants}}}
\starttext
\startlinenumbering
\dorecurse{20}{\variant{donald e knuth}{herman zapf} }
\stoplinenumbering
\stoptext
BTW, it has a “minor issue”: hyphenation doesn’t work in the body text
It works fine in the notes. I reported this, but I’m afraid it hasn’t
Hans,
I have the following sample (it includes Lua code for underscore
hyphenation):
\startluacode
function document.addfunnyhyphen(tfmdata)
local underscore = utf.byte(_)
local char = tfmdata.characters[underscore]
if not char then return
On 07/07/2015 05:41 PM, Arthur Reutenauer wrote:
[...]
That's because the word you're trying to hyphenate is
Amsterdam-Buitenveldert, not Amsterdam. Compound words are by
default hyphenated only at the hyphen in TeX.
\setbreakpoints[compound] works in the following sample:
On Tue, Jul 07, 2015 at 03:29:11PM +, Meer, H. van der wrote:
The \hyphenatedword works here too. But it does not work out when the word
Amsterdam occurs in the text. See tthe two examples. In the first Amsterdam
is not broken according to the \hyphenation{Am-ster-dam}-rule. In the second
Indeed, the combination Amsterdam-Buitenveldert is the culprit.
The solution therefore is to use (it is ConTeXt afterall)
Amsterdam|-|Buitenveldert, then the word Amsterdam doesn't even needs an
exception.
Thanks for the help.
Hans van der Meer
On 07 Jul 2015, at 18:00, Pablo Rodriguez
The \hyphenatedword works here too. But it does not work out when the word
Amsterdam occurs in the text. See tthe two examples. In the first Amsterdam is
not broken according to the \hyphenation{Am-ster-dam}-rule. In the second
example the linebreak is forced by the explicit use of Am\-ster
Has something happened to hyphenation?
The following does not work
\language[nl]
\startexceptions[nl]
Am-ster-dam
\stopexceptions
Neither does \hyphenation{Am-ster-dam}
Only in the context-source Am\-ster\-dam is working.
How to load a series of hyphenation exceptions instead of explicitely
On 07/07/2015 03:33 PM, dr. Hans van der Meer wrote:
Has something happened to hyphenation?
The following does not work
\language[nl]
\startexceptions[nl]
Am-ster-dam
\stopexceptions
Neither does\hyphenation{Am-ster-dam}
Hi Hans,
using latest beta from 2015.07.01 21:40, both options
are the linebreaks identical, i.e. same hyphenation?
Many thanks for your reply, Hans.
Hyphenation is the same in both documents.
btw, brokenpenalty 1 gives a different result
Page break is wrong when any of the three values (brokenpenalty,
widowpenalty or clubpenalty) is 0 or above
hyphenation?
Many thanks for your reply, Hans.
Hyphenation is the same in both documents.
btw, brokenpenalty 1 gives a different result
Page break is wrong when any of the three values (brokenpenalty,
widowpenalty or clubpenalty) is 0 or above .
I replacing \subsection with \section
for widow and
orphan lines move the two last lines to the next page.
Could anyone confirm this bug?
i wonder if it's a bug or just tex's decision ... you can use
\showmakeup[penalty]
and see what penalties get injected
are the linebreaks identical, i.e. same hyphenation?
Many thanks for your
get injected
are the linebreaks identical, i.e. same hyphenation?
btw, brokenpenalty 1 gives a different result
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
=hyphenated,...]
works as expected. Even single words are broken then.
I will currently stick with option 1, since option 3 has a negative side
effect: it inserts hyphen marks (-), which looks weird in source code.
All in all I have two wishes regarding wordwrap and hyphenation, and
hope they aren't
a negative side
effect: it inserts hyphen marks (-), which looks weird in source code.
I know. That is why, as I say in the documentation, option 3 is a last
case resort.
All in all I have two wishes regarding wordwrap and hyphenation, and
hope they aren't too hard to grant :-)
1. Add an option
On 5/5/2015 2:42 PM, Csikos Bela wrote:
Hello list members:
I would like to disable hyphenation in headings (chapter, section, etc. titles)
while allow it in body text. Is there a setting for this? Or do I have to adjust
all the headings manually by inserting line breaks?
... align={flushleft
Hello list members:
I would like to disable hyphenation in headings (chapter, section, etc. titles)
while allow it in body text. Is there a setting for this? Or do I have to adjust
all the headings manually by inserting line breaks?
Thanks,
bcsikos
Hans Hagen írta:
On 5/5/2015 2:42 PM, Csikos Bela wrote:
Hello list members:
I would like to disable hyphenation in headings (chapter, section, etc.
titles)
while allow it in body text. Is there a setting for this? Or do I have to
adjust
all the headings manually by inserting line breaks
Hi,
I have to typeset a Bulgarian document but the hyphenation doesn’t work. The
lang-bg.lua file is not loaded, according to the log. (All four lang-bg files
are present in /tex/texmf-context/tex/context/patterns/)
\usetypescriptfile[type-gentium]
\usetypescript[gentium]
\setupbodyfont
,
leftquotation=\leftguillemot,
rightquotation=\rightguillemot,
date={day,\space,month,\space,year}]
I needed hyphenation in order to typeset the first revision of a translated
book. I have to wait for feedback from the translator to tell if these settings
are OK for bg.
--
Tom
On 5/3/2015 6:58 PM, Thomas Floeren wrote:
Do I have to do anything special, in addition to \mainlanguage [bg] ?
In reply to my own question:
It seems I must add
\installlanguage
[bg]
[lefthyphenmin=2,
righthyphenmin=2,
patterns=bg,
…
…]
so what is the complete bulgarian setup then?
to typeset a Bulgarian document but the hyphenation doesn’t work. The
lang-bg.lua file is not loaded, according to the log. (All four lang-bg files
are present in /tex/texmf-context/tex/context/patterns/)
\usetypescriptfile[type-gentium]
\usetypescript[gentium]
\setupbodyfont[gentium,12pt
hyphenator and hyphenation methods
which are imo document properties and not language specific. Actually
the values *min in the language blob are there mostly because patterns
can have these limitations.
Hans
On 04/13/2015 07:41 PM, Hans Hagen wrote:
On 4/13/2015 7:17 PM, Pablo Rodriguez wrote:
[...]
Would it be possible to have hyphenmin in \setuplanguage?
I think it also makes sense there, besides lefthyphenmin and righthyphenmin.
It relates more to the alternative hyphenator and hyphenation
of the file or the project information in the footer, and some black
rules where the hyphenation of words has not been done.
Is there any command which does what is needed for having informations about
cross-referencing?
In LaTeX for example, there is a package which puts the name of each
in small print
the name of the file or the project information in the footer, and some
black rules where the hyphenation of words has not been done.
Is there any command which does what is needed for having informations about
cross-referencing?
In LaTeX for example, there is a package which
not that: it prints only in small print
the name of the file or the project information in the footer, and some black
rules where the hyphenation of words has not been done.
Is there any command which does what is needed for having informations about
cross-referencing?
In LaTeX for example
On 4/2/2015 1:21 AM, Pablo Rodriguez wrote:
On 03/30/2015 10:33 PM, Hans Hagen wrote:
On 3/30/2015 5:19 PM, Pablo Rodriguez wrote:
[...]
For some reason unknown to me, the only way to compile the sample is to
remove the luacode snippet.
I need the lua code to have underscore hyphenation
On 03/30/2015 10:33 PM, Hans Hagen wrote:
On 3/30/2015 5:19 PM, Pablo Rodriguez wrote:
[...]
For some reason unknown to me, the only way to compile the sample is to
remove the luacode snippet.
I need the lua code to have underscore hyphenation in type commands. And
I need two extra
For some reason unknown to me, the only way to compile the sample is to
remove the luacode snippet.
I need the lua code to have underscore hyphenation in type commands. And
I need two extra \definehyphenationfeatures and \sethyphenationfeatures
to invoke it.
Have I hit a bug or what am I missing
}{\CoverImageFile}{\CoverImageFont}}
\starttext
\CoverImage
\stoptext
For some reason unknown to me, the only way to compile the sample is to
remove the luacode snippet.
I need the lua code to have underscore hyphenation in type commands. And
I need two extra \definehyphenationfeatures
(when alone, they look fine). See MWE, if you
remove the comment in the \mainlanguage command, ligatures get screwed up:
Hi Andrés,
I’m afraid this is a proper bug.
It isn’t related to Spanish as language. The bug is triggered when a the
ligature has a hyphenation point at the end.
Here
remove the comment in the \mainlanguage command, ligatures get screwed up:
Hi Andrés,
I’m afraid this is a proper bug.
It isn’t related to Spanish as language. The bug is triggered when a the
ligature has a hyphenation point at the end.
Here is another mininmal example with German as main
\my_way\ScanCSV\t-scancsv_ConTeXt_module\2PabloRod
riguez5\dddpdflatex --shell-escape latex
This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014/W32TeX)
(preloaded
format=pdflatex)
\write18 enabled.
entering extended mode
(./latex.tex
LaTeX2e 2014/05/01
Babel 3.9k and hyphenation patterns
On 2/12/2015 5:10 PM, Axel Kielhorn wrote:
Am 12.02.2015 um 16:10 schrieb Hans Hagen pra...@wxs.nl:
for the moment use
\setuphyphenation[method=expanded]
This works in the current beta, but not with the stable version in TeXLive 2014.
indeed, as there is new hyphenation related code
Hi!
I'm trying to use Context to export a document to epub.
Following the instructions on Contextgarden everything works up to a point:
When I add manual hyphenation for the word Trennalgorithmus and
\setupbackend[export=yes,xhtml=yes]
I get:
lua errorerror on line 1 in file /Volumes
On 2/12/2015 11:13 AM, Axel Kielhorn wrote:
Hi!
I'm trying to use Context to export a document to epub.
Following the instructions on Contextgarden everything works up to a point:
remark: in your example you say:
Auch wenn der Trennalgorithmus von LaTeX nicht schlecht ist, gibt es
wieder
On 2/12/2015 11:13 AM, Axel Kielhorn wrote:
Hi!
I'm trying to use Context to export a document to epub.
Following the instructions on Contextgarden everything works up to a point:
When I add manual hyphenation for the word Trennalgorithmus and
\setupbackend[export=yes,xhtml=yes]
I get:
lua
Am 12.02.2015 um 16:10 schrieb Hans Hagen pra...@wxs.nl:
for the moment use
\setuphyphenation[method=expanded]
This works in the current beta, but not with the stable version in TeXLive 2014.
It doesn't matter since I need the beta to create epub, just wanted to mention
it.
Thanks for
Of course, language of the cited publication. Nothing else makes sense
at all. This field is also to be used for hyphenation of the title
field.
BUT, the author of the TeX document must control and decide if the
bibliography will use an eventual language= field or rather use the
language rule
first lines to start on the very left of the
textfield.
If I use \hyphenation to prevent e.g. names from being hyphenated those
words might be driven into the right margin.
Hanging punctuation doesn’t seem to work as well.
Is there anything that can be done about that? Or how can
.
The respectively hanging first lines of each entry in the publications
list are not properly aligned on the left. (The indented lines are). I
would like all of those first lines to start on the very left of the
textfield.
If I use \hyphenation to prevent e.g. names from being hyphenated those
words
defaults with hanging indents in the publications list.
The respectively hanging first lines of each entry in the publications
list are not properly aligned on the left. (The indented lines are). I
would like all of those first lines to start on the very left of the
textfield.
If I use \hyphenation
of each entry in the publications
list are not properly aligned on the left. (The indented lines are). I
would like all of those first lines to start on the very left of the
textfield.
If I use \hyphenation to prevent e.g. names from being hyphenated those
words might be driven into the right
in
the paragraph.
Fixed, thanks for noticing, it had to do with picking up the right
settings after a change in alternative (we operate on several axis:
language, glyph and hyphenation properties).
Many thanks for having fixed it, Hans.
Pablo
\startluacode
function
On 12/10/2014 10:58 PM, Hans Hagen wrote:
On 12/10/2014 8:15 PM, Pablo Rodriguez wrote:
On 12/09/2014 12:07 AM, Hans Hagen wrote:
On 12/8/2014 5:47 PM, Pablo Rodriguez wrote:
[..]
And sorry for asking this again, but I need underscore hyphenation with
the underscore character from the font
On 12/09/2014 12:07 AM, Hans Hagen wrote:
On 12/8/2014 5:47 PM, Pablo Rodriguez wrote:
[..]
And sorry for asking this again, but I need underscore hyphenation with
the underscore character from the font and only for the \tex and
\hyphenatedurl commands (not for the rest of the text
Hans,
the sample below hyphenates right what comes before \TexC in the
paragraph. Also the contents of \TexC are hyphenated right.
But hyphen is removed from standard text after the last \TexC command in
the paragraph.
I have just accidentally discovered it.
Many thanks for your help,
Pablo
discovered it.
Fixed, thanks for noticing, it had to do with picking up the right
settings after a change in alternative (we operate on several axis:
language, glyph and hyphenation properties).
Many thanks for your help,
Pablo
\startluacode
function document.addfunnyhyphen(tfmdata
On 12/10/2014 8:15 PM, Pablo Rodriguez wrote:
On 12/09/2014 12:07 AM, Hans Hagen wrote:
On 12/8/2014 5:47 PM, Pablo Rodriguez wrote:
[..]
And sorry for asking this again, but I need underscore hyphenation with
the underscore character from the font and only for the \tex and
\hyphenatedurl
[Nietz-sche] will work).
This differs from the \hyphenation command. Is this intended?
And sorry for asking this again, but I need underscore hyphenation with
the underscore character from the font and only for the \tex and
\hyphenatedurl commands (not for the rest of the text).
How could
in capitals (only
\registerhyphenationexception[Nietz-sche] will work).
This differs from the \hyphenation command. Is this intended?
And sorry for asking this again, but I need underscore hyphenation with
the underscore character from the font and only for the \tex and
\hyphenatedurl commands
On 12/03/2014 09:36 PM, Hans Hagen wrote:
On 12/3/2014 7:48 PM, Pablo Rodriguez wrote:
With the new hyphenator, \hyphenation isn’t honored, such as in this sample:
[...]
Has the command been deprecated with the new hyphenator?
The next version will have:
[...]
(the functionality
On 12/04/2014 10:00 PM, Hans Hagen wrote:
On 12/4/2014 8:21 PM, Pablo Rodriguez wrote:
[...]
The text from Knuth needs to have the standard hyphenation character,
although the other two commands need to have underscore hyphenation.
Which is the best way to do it?
it's no big deal
501 - 600 of 1768 matches
Mail list logo
