From: Balazs Nagy <js@lsc.hu>
Subject: Too much betas with languages (long)
Date: Tue, 24 Oct 2000 13:03:00 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0010241242220.2759-100000@power.lsc.hu> (raw)
Hi,
I have two versions of teTeX. At work I have a 1.0.6 and at home there is a
1.0.7. Each has Hungarian patch (by me), which contains an
- enco-pdf.tex addition:
\defineaccent H U ^^db
\defineaccent H u ^^fb
\defineaccent H O ^^d5
\defineaccent H o ^^f5
- an enco-whu.tex based on enco-win.tex with the changes of
\~o -> \H o
\~O -> \H O
\^u -> \H u
\^U -> \H U
- Hungarian additions to lang-ura.tex and
- mult-sys.tex addition:
\defineconstant {hungarian} \defineconstant {hu}
- cont-usr.tex addition:
\definesysnonym [lang-hu.pat] [huhyph.tex]
Then, I generated cont-en.efmt.
With the old engine I can get good results, but with the new one I get weird
effects (maybe I neither do background colors but I didn't try it with the
new install): just before a macro places some text, it prints a beta symbol.
Ie. the page numbers look like <beta><beta><number>, other fix running
labels are in the <beta><label> format, the cover has a
\midaligned{\tfa\currentdate} which has the same beta sign and so on. The
tex file generator starts with
print "% interface=english paper=a4\n";
print "\\doublesidedprinttrue\n";
print "\\setupoutput[pdftex]\n";
print "\\mainlanguage[hu]\n";
print "\\useencoding[pdfdoc,whu]\n";
print "\\input ../setup\n";
print "\\def\\modulename{$title}\n";
print "\\def\\moduletype{\\typenovel}\n";
print "\\starttext\n";
print "\\startstandardmakeup\n";
print "\\headline\n";
print "\\blank[6*big]\n";
print "\\midaligned{\\bfd{$title}}\n";
print "\\blank[3*big]\n";
print "\\midaligned{\\tfd{\\moduletype}}\n";
print "\\vfill\n";
print "\\midaligned{\\tfa{$written: $author \\email{$email}}}\n";
print "\\midaligned{\$\\star\$}\n";
print "\\blank[small]\n";
print "\\midaligned{\\tfa\\currentdate}\n";
print "\\stopstandardmakeup\n";
The setup.tex contains
\def\headline{
\switchtobodyfont[ss,10pt]
\midaligned{\tfc i~g~e~n~~k~ö~n~n~y~ű~~s~z~e~r~e~p~j~á~t~é~k}
}
\define[1]\email{\useURL[#1][mailto:#1][][\ss $<$#1$>$]\from[#1]}
Which can be a problem?
--
Nagy Balazs, LSC
http://www.lsc.hu/
next reply other threads:[~2000-10-24 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 11:03 Balazs Nagy [this message]
2000-10-24 12:20 ` Hans Hagen
2000-10-24 18:49 ` Balazs Nagy
2000-10-25 8:08 ` Hans Hagen
2000-10-26 15:48 ` Balazs Nagy
2000-10-27 7:40 ` 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=Pine.LNX.4.21.0010241242220.2759-100000@power.lsc.hu \
--to=js@lsc.hu \
/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).