From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: mkiv
Date: Sat, 8 Dec 2007 21:48:04 +0100 [thread overview]
Message-ID: <6faad9f00712081248y6e0da03fuef45d13da24bb988@mail.gmail.com> (raw)
In-Reply-To: <47598E33.4050201@wxs.nl>
On Dec 7, 2007 7:17 PM, Hans Hagen wrote:
> Hi,
>
> As a prelude to an independent language mechanism for mkiv (the tex
> part) I removes a few thingies. I was wondering ... is anyone using
> language specifics? Active quote stuff? Does that still make sense for
> mkiv? After all we can have more advanced exceptions and we have utf ...
enco-fsl can go away (in mkii as well), but not lang-sla.mki* :)
When looking into enco-fde (the same is true for Slovenian and Croatian):
\def\setupDElanguage
{\setuplanguage
[\s!de]
[\c!leftsentence=\leftguillemot,
\c!rightsentence=\rightguillemot,
\c!leftsubsentence=\leftsubguillemot,
\c!rightsubsentence=\rightsubguillemot]}
I have suggested another way of handling that a few days ago (no
conclusions met).
Discretionaries should be handled by LuaTeX itself, right? So I guess
that they're not really needed if they find their way into mkiv.
Then only "a, "o, "u, "s are left for German. (I already wanted to ask
for "c -> č, "s -> š and "z ->ž mappings for Slovenian once, but I
have changed my mind. I find it extremely ugly, although I used to
write that way before someone has told me about
\usepackage[cp1250]{inputenc}
I would vote against supporting them ("a, "o, "u) in LuaTeX, but it's
not up to me.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-08 20:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 18:17 mkiv Hans Hagen
2007-12-07 23:31 ` mkiv Henning Hraban Ramm
2007-12-08 9:18 ` mkiv Wolfgang Schuster
2007-12-12 9:34 ` mkiv Steffen Wolfrum
2007-12-08 22:47 ` mkiv Hans Hagen
2007-12-08 20:48 ` Mojca Miklavec [this message]
2007-12-09 15:39 ` mkiv Willi Egger
2007-12-11 22:07 ` mkiv Hans Hagen
2007-12-12 6:50 ` mkiv Peter Münster
2007-12-12 8:26 ` mkiv Thomas A. Schmitz
2007-12-12 20:02 ` mkiv Peter Münster
2007-12-12 21:34 ` mkiv Hans Hagen
2007-12-12 21:39 ` mkiv Mojca Miklavec
2007-12-12 21:46 ` mkiv Hans Hagen
2007-12-13 6:20 ` mkiv Peter Münster
2007-12-12 9:42 ` mkiv Steffen Wolfrum
-- strict thread matches above, loose matches on Subject: below --
2022-04-01 16:20 mkiv Hans Hagen via ntg-context
2022-04-01 18:19 ` mkiv Rik Kabel via ntg-context
2022-04-01 18:37 ` mkiv Pablo Rodriguez via ntg-context
2022-04-01 19:19 ` mkiv Denis Maier via ntg-context
2022-04-02 7:40 ` mkiv Hans Hagen via ntg-context
2022-04-02 11:46 ` mkiv Pablo Rodriguez via ntg-context
2009-03-17 17:21 mkiv Hans Hagen
2008-10-17 8:41 mkiv Hans Hagen
2008-10-17 17:37 ` mkiv Peter Münster
2008-10-17 19:32 ` mkiv Hans Hagen
2008-10-21 10:35 ` mkiv Wolfgang Schuster
2008-10-21 11:05 ` mkiv Hans Hagen
2007-08-13 9:49 mkiv Hans Hagen
2007-08-13 10:26 ` mkiv fdu.xiaojf
2007-08-13 11:05 ` mkiv Hans Hagen
2007-08-13 10:36 ` mkiv luigi scarso
2007-08-15 14:07 ` mkiv Aditya Mahajan
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=6faad9f00712081248y6e0da03fuef45d13da24bb988@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).