ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Too much betas with languages (long)
Date: Tue, 24 Oct 2000 14:20:14 +0200	[thread overview]
Message-ID: <3.0.6.32.20001024142014.015b3680@pop.wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.21.0010241242220.2759-100000@power.lsc.hu>

At 01:03 PM 10/24/00 +0200, Balazs Nagy wrote:
>Hi,

>- enco-pdf.tex addition:
>	\defineaccent  H U ^^db
>	\defineaccent  H u ^^fb
>	\defineaccent  H O ^^d5
>	\defineaccent  H o ^^f5

If this does not conflict with any other language I can add it permanently. 

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

Same for this. 

>- Hungarian additions to lang-ura.tex and
>
>- mult-sys.tex addition:
>	\defineconstant {hungarian}   \defineconstant {hu}

i've added this 

>- cont-usr.tex addition:
>	\definesysnonym [lang-hu.pat]  [huhyph.tex]

and this

>Then, I generated cont-en.efmt.

are all the hungarian labels okay? 

>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

to what extend is it related to backgrounds? 

>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";

What is this? Looks pretty low level to me: \doublesidedprinttrue is not a
user command

>        print "\\setupoutput[pdftex]\n";
>        print "\\mainlanguage[hu]\n";
>        print "\\useencoding[pdfdoc,whu]\n";

Pdfdoc encoding is never to be activated since it is only needed for low
level pdf where it happens automatically! So, no [pdftex] 

>        print "\\input ../setup\n";

you may try \environment setup 

>        print "\\def\\modulename{$title}\n";
>        print "\\def\\moduletype{\\typenovel}\n";

no lowercase names since it may clash! 

>        print "\\starttext\n";
>        print "\\startstandardmakeup\n";
>        print "\\headline\n";

same for \headline

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

\def\stretched% slightly adapted to handle spaces
  {\ifvmode\hbox to \hsize\else\ifinner\else\hbox\fi\fi
   \processtokens\relax\hss\relax{\hss\hss}}

\hbox to 5cm{\stretched{Hi There}}

there is also: 

\stretcheduppercase{Hi There}

and in the next release: \stretchedlowercase and \stretchednormalcase

>\define[1]\email{\useURL[#1][mailto:#1][][\ss $<$#1$>$]\from[#1]}
>
>Which can be a problem?

I don't know. Your file runs ok here. In order to check it I need a minimal
example + log + pdf file. 

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  reply	other threads:[~2000-10-24 12:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-24 11:03 Balazs Nagy
2000-10-24 12:20 ` Hans Hagen [this message]
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=3.0.6.32.20001024142014.015b3680@pop.wxs.nl \
    --to=pragma@wxs.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).