From: Hans Hagen <pragma@wxs.nl>
Subject: Re: beginners manual
Date: Mon, 28 Nov 2005 00:26:20 +0100 [thread overview]
Message-ID: <438A409C.8010504@wxs.nl> (raw)
In-Reply-To: <e5d3f2650511261512t7970dc50o20f1ede53c24d8f6@mail.gmail.com>
VnPenguin wrote:
>Hi Hans et al,
>
>Just tried to compile "ma-cb-en" with T5. Here are some remarks:
>
>1. \def\TitlePage#1#2#3 in file "ma-cb-style.tex" does not work with T5.
>Because of
>
>\definedfont[SansBold at 40pt]
>
>I lossed so many vietnamese accented characters. I have to change to
>
>\switchtobodyfont[40pt]\bf
>
>in order to make T5 work. I think the file "ma-cb-style.tex" needs
>more attention for multi-lang support.
>
>
>
sure, the only thing i did so far is split and reorganize;
at your place, it runs with:
\startnotmode[atpragma]
\usetypescriptfile[type-buy]
\usetypescript[palatino][ec]
\setupbodyfont[palatino,10pt]
\stopnotmode
so for vietnamese you need another encoding.
(i added language modes, so we can now do for vietnamese):
\startmode[*vn]
\enableregime[utf]
\setupencoding[default=t5]
\stopmode
\startnotmode[atpragma]
\usetypescriptfile[type-buy]
\usetypescript[palatino][\defaultencoding]
\setupbodyfont[palatino,10pt]
\stopnotmode
(in ma-cb-style.tex)
can you test that?
>2. In file "ma-cb-en-document.tex" :
>...
>\CONTEXT\ expects a plain \ASCII\ input file. Of course you
>can use any texteditor or wordprocessor you want, but you
>should not forget that \CONTEXT\ can only read \ASCII\
>input. Most texteditors or wordprocessors can export your
>file as plain \ASCII.
>...
>What do you think about a plain text input file in UTF-8 charset ?
>It's not ASCII by definition, but the current ConTeXt (pdfetex) can
>work with it no problem. All my works with ConTeXt are prepared in
>UTF-8 input file.
>
>
>
sure, no problem for the vn version
Hans
next prev parent reply other threads:[~2005-11-27 23:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 0:53 Hans Hagen
2005-11-26 8:11 ` VnPenguin
2005-11-26 11:07 ` Taco Hoekwater
2005-11-26 12:57 ` VnPenguin
2005-11-27 23:29 ` Hans Hagen
2005-11-28 7:27 ` VnPenguin
2005-11-28 10:27 ` Hans Hagen
2005-11-26 19:46 ` David Arnold
2005-11-26 23:12 ` VnPenguin
2005-11-27 23:26 ` Hans Hagen [this message]
2005-11-28 20:16 ` VnPenguin
2005-11-27 13:27 ` Vit Zyka
2005-11-27 22:34 ` Hans Hagen
2005-11-28 10:03 ` Vit Zyka
2005-11-28 13:13 ` Mari Voipio
2005-11-28 13:56 ` Taco Hoekwater
2005-11-28 14:08 ` Wolfgang Zillig
2005-11-28 15:09 ` Hans Hagen
2005-11-28 19:45 ` VnPenguin
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 22:03 Hans Hagen
2005-11-22 16:00 ` VnPenguin
2005-11-22 16:39 ` Olivier
2005-11-23 10:33 ` Hans Hagen
2005-11-22 16:56 ` Jose Antonio Rodriguez
2005-11-22 17:15 ` Mikael Persson
2005-11-24 15:38 ` Johan Sandblom
2005-11-22 19:32 ` Taco Hoekwater
2005-11-22 20:51 ` Tobias Burnus
2005-11-23 20:15 ` Mojca Miklavec
2005-11-24 22:39 ` Maurice Diamantini (dom)
2005-11-25 9:47 ` Wolfgang Zillig
2005-11-24 11:18 ` Otared Kavian
2005-11-24 22:29 ` Otared KAVIAN
2005-11-25 4:41 ` Xiao Jianfeng
2005-11-25 13:10 ` Patrick Gundlach
2005-11-25 14:05 ` Xiao Jianfeng
2005-11-28 11:46 ` Mari Voipio
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=438A409C.8010504@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).