ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Matthias Wächter" <matthias@waechter.wiz.at>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Composed Words
Date: Wed, 28 Jan 2009 12:36:54 +0100	[thread overview]
Message-ID: <49804356.4000804@waechter.wiz.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

Greetings,

First question: I thought that composing words using || should break
after the hyphen/dash, but for whatever reasons, this does not
always work correctly and breaks such that the hyphen/dash is in the 
next line — see attached picture. Processed by luatex,
updated today.

The source code is not fancy in any way:

\language[de]%
%[…]

Die Ausgabe einer komplexen Netzwerkkomponente wie einem
TTEthernet||Switch kann am leichtesten von einer einfachen
Vergleichsschaltung überprüft werden, wenn die paarweise
angeordneten Komponenten Bit für Bit synchron arbeiten
%[…]


Second question: Why did you choose the «En dash» as the default 
intra word dash for at least English and German, whereby this is 
wrong in most cases and should be the hyphen instead?

http://en.wikipedia.org/wiki/Dash#En_dash lists the uses of the En 
dash. It is limited to number ranges, relationships and connections 
and compound adjectives.

for me, \setuphyphenmark[sign=normal] fixed the issue, but the 
“correct” way (hyphen) should be the default, IMHO.

– Matthias


[-- Attachment #2: thesis-break.png --]
[-- Type: image/png, Size: 68418 bytes --]

[-- Attachment #3: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2009-01-28 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 11:36 Matthias Wächter [this message]
2009-01-29 12:38 ` Taco Hoekwater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49804356.4000804@waechter.wiz.at \
    --to=matthias@waechter.wiz.at \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).