ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Willi Egger <w.egger@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX ligatures in XeTeX/LuaTeX: ``who needs them''?
Date: Mon, 10 Dec 2007 09:49:38 +0100	[thread overview]
Message-ID: <AB63332F-31AB-4F13-8D41-C700BDC61420@boede.nl> (raw)
In-Reply-To: <6faad9f00712091048y578ddf47g7cd36cc2f6bdc8a8@mail.gmail.com>

Hi Mojca,

On Dec 9, 2007, at 7:48 PM, Mojca Miklavec wrote:

> On Dec 9, 2007 5:07 PM, Willi Egger wrote:
>>> or even more weird ones:
>>>   !` -> inverted exclam
>>>   ?` -> inverted question
>>
>> For Spanish this is definitevely necessary. Again if coded in UTF
>> there is no problem.
>
> Do Spansh users still key them in like that (apart from old TeX-ies
> who have never heard abot anything beyond \v, \", \')? I mean: would
> anyone miss those two ligatures? (I assume that people need to use
> inverted quotation marks in Word as well ...)
>
I was not to the point on this and I misinterpreted your question.   
Sorry.
Indeed the well known coding of umlauts and alike with \"... should  
be there for sake of compatibility. - If those would vanish, this  
would mean for me to re-encode a couple of thousand pages ...
Coming back to the quotation-marks. IMHO one should stick to the  
\quote and \quotation constructs. This and only this allows you to  
change the appearance of the marks depending on a given language or  
adjust them to the style of a print-house/publisher. I would suggest  
not to make provisions in order to automatically convert ,, into „ .  
There will be consistency problems and the behaviour of Word i.e.  
that things happen while you have difficulty to control them.

> Ono problem is that that's a "well known" TeX behaviour though
> (documented in beginner's manual as well).
>
>>> Some ligatures are handy indeed:
>>>   -- -> endash
>>>   --- -> emdash
>>>   ' -> right single quote (I'm, isn't etc.)
>>
>> Sure this is important, I suggest to add the horizontal ellipsis
>
> \dots? But what if one decides to use, say, 10 dots in a row? That
> might lead to weird effects (non-evenly spaced dots). -- and --- have
> been well established, so one would be careful enough before writing
> "----------". And there's \dots, so that one could have been mapped to
> ellipsis if needed.
>
The ellipsis is typographically an important 'character'. So todays  
solution with \dots or \unknown is fine to me. When necessary one can  
adjust the kerning of the dots for style-purposes. Otherwise one  
could discuss to convert three consecutive dots (and only those) to  
the horizontal ellipsis in Unicode, which would look always better  
than three dots from the keyboard. Also here it is questionable  
whether to have automatic conversion. Again this is resembling Word  
and how to keep grip on what is happening.
IMHO the user who places an x-number of dots or dashes must know what  
he does. There might not be a generic solution for such cases.

Willi

> Thanks,
>     Mojca
> ______________________________________________________________________ 
> _____________
> 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
> ______________________________________________________________________ 
> _____________




___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2007-12-10  8:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08 22:04 Mojca Miklavec
2007-12-08 22:26 ` Aditya Mahajan
2007-12-08 23:10   ` Mojca Miklavec
2007-12-09 14:45     ` Henning Hraban Ramm
2007-12-08 23:11   ` Wolfgang Schuster
2007-12-09 16:07 ` Willi Egger
2007-12-09 18:48   ` Mojca Miklavec
2007-12-10  8:46     ` Wolfgang Schuster
2007-12-10  8:49     ` Willi Egger [this message]
2007-12-10  5:55 ` Maurí­cio
2007-12-10  8:41   ` Hans Hagen
2007-12-10 12:24     ` Maurí­cio
2007-12-10 12:38       ` Mojca Miklavec

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=AB63332F-31AB-4F13-8D41-C700BDC61420@boede.nl \
    --to=w.egger@boede.nl \
    --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).