From: Olya Briginets <bolya@ukrpost.net>
Subject: Re: Getting property values (and problem defining accents)
Date: Thu, 13 Sep 2001 02:01:50 +0300 [thread overview]
Message-ID: <3B9FE95E.7C27E258@ukrpost.net> (raw)
In-Reply-To: <5.1.0.14.1.20010910231125.026abee8@server-1>
Hello Hans,
Hans Hagen wrote:
> >I use the following simple command for debugging purposes:
> >
> > \def\thevalue#1#2#3{\csname @@#1#2#3\endcsname}
> >
> >but maybe there exists a more advanced interface?
>
> thos is probably ok for your purpose, although it depends a bit on what you
> want to show but in most cases this is ok, but keep in mind that low level
> deep down is dutch [still, but it's slowly changing]
>
> \unprotected \def\thevalue#1#2%
> {\csname @@#1\csname\k!prefix!#2\endcsname\endcsname}
>
> is also a way to handle it, in which case the interface is the current one,
>
> why do you need this?
I used it to check some values like \thevalue{la}{ua}{status} or
\thevalue{la}{ua}{encoding} to ensure that language is installed properly,
because I had troubles defining some characters.
Specifically, I have a problem defining accented glyphs. I try to use
\defineaccent command:
\defineaccent " {\cyrillicE} {\cyrillicYO}
But this works only if one writes exactly \"\cyrillicE, which does not make
sense, as symbols are usually entered as 8bit (via different regimes).
Analogously, the example from enco-ini:
\defineaccent ' {\dotlessi} 237
works if used as \'\dotlessi, not as \'\i. But \dotlessi is usually inputed as
\i, which is the intended way to use it?
Is there a way to \defineindirectaccent or something alike, which will expand
the next token?
Olya
PS. I hope to send some working support of russian and ukrainian languages in
couple of days.
next prev parent reply other threads:[~2001-09-12 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 0:40 Getting property values Olya Briginets
2001-09-10 21:14 ` Hans Hagen
2001-09-12 23:01 ` Olya Briginets [this message]
2001-09-13 10:26 ` Getting property values (and problem defining accents) 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=3B9FE95E.7C27E258@ukrpost.net \
--to=bolya@ukrpost.net \
/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).