ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: problems with \lcommaaccent
Date: Wed, 2 Aug 2006 03:13:18 +0200	[thread overview]
Message-ID: <6faad9f00608011813k197f03e2ye0e9595a6647eef8@mail.gmail.com> (raw)

Hello,

I've been trying to use \lcommaaccent, but with no success until I
commented out the following line in enco-cas:

% \defineULcharacter Lcommaaccent lcommaaccent

Any ideas how to solve that problem (otherwise the temporary
workaround will disappear as soon as I update ConTeXt)? The only
remedy that came to my mind was adding additional two lines to
enco-def. (Hans, would it be possible to add them to the distribution
as well?)


\definecharacter lcommaaccent     {\buildtextbottomcomma l}
\definecharacter Lcommaaccent     {\buildtextbottomcomma L}

\starttext
\lcommaaccent\Lcommaaccent
\stoptext

Thanks,
  Mojca

             reply	other threads:[~2006-08-02  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02  1:13 Mojca Miklavec [this message]
2006-08-02  8:39 ` Hans Hagen

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=6faad9f00608011813k197f03e2ye0e9595a6647eef8@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).