ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Dohyun Kim" <nomosnomos@gmail.com>
Subject: please add support for Korean language in unic-cjk.tex
Date: Wed, 22 Nov 2006 18:33:14 +0900	[thread overview]
Message-ID: <bfeb3bf10611220133x37feea5bnf51d4870ebd195de@mail.gmail.com> (raw)

Hi.

Recently I have tried to support typesetting UTF-8 Korean language
along with context-beta. I have uploaded related files
to a temporary server for your reference (3.5Mb):

http://210.94.201.157/~nomos/KTUG/context-korean-test.tar.gz

But as the current unic-cjk.tex does not cover
Korean Hangul Syllables area and CJK Compatibility Ideographs area,
I have to edit that file every time I upgrade context.
It is so an annoying thing to do it every time
that I suggest adding those areas in unic-cjk.tex file,  like this:

%%% Hangul Syllables
\dostepwiserecurse{172}{215}{1}{\expanded{\defineunicodecommand
{\recurselevel}} {\lookaheaduchar}}
%%% CJK Compatibility Ideographs
\dostepwiserecurse{249}{250}{1}{\expanded{\defineunicodecommand
{\recurselevel}} {\lookaheaduchar}}


Additionally, I here report some possible bugs of context-beta
related to CJK (especially Korean language) support.

First, unintended space is inserted when I change font family.
This disappears if I add a comment sign in \enableunicodefont
command in font-uni.tex.

\def\enableunicodefont#1%
  {\definefontsynonym[\s!Unicode][\getvalue{\??uc#1\c!file}]%
   \def\unicodescale             {\getvalue{\??uc#1\c!scale}}%
   \def\unicodeheight            {\getvalue{\??uc#1\c!height}}%
   \def\unicodedepth             {\getvalue{\??uc#1\c!depth}}%
   \def\unicodedigits            {\getvalue{\??uc#1\c!conversion}}%
   \def\handleunicodeglyph       {\getvalue{\??uc#1\c!command}}%
   \doifnot\currentregime{utf}{\enableregime[unicode]}%
   % the following \relax's are realy needed
   \doifvalue{\??uc#1\c!interlinespace}\v!yes
      \setupinterlinespace\relax
   \doifvalue{\??uc#1\c!strut}\v!yes
      {\setunicodestrut\unicodeheight\unicodedepth}% <- HERE
      {\resetunicodestrut}%
   \getvalue{\??uc#1\c!commands}\relax}


Secondly, to deal with special commands in pdf bookmarks,
"\simplifycommands" should be added to \sanitizePDFuniencoding
command in spec-tst.tex.

\long\def\sanitizePDFuniencoding#1\to#2%
  {\enablePDFunicrlf
    \simplifycommands  % <- HERE
   \let\unicodechar\relax % prevent further expansion
   \retainlccodes\lccode32=255 % slooow
   \lowercasestring\PDFunicodetrigger#1\to#2%
   \edef#2{\expandafter\doPDFuni#2\empty\empty}} % slooow


Thirdly, "\definefileinsertion{tpd}{mps}" in spec-dpx.tex
seems to be a typo. I think this should be corrected as follows:

\definefileinsertion{dpx}{mps}


In fact, as an unsubscribed user I have posted a similar message
to the context mailinglist a few weeks ago . But I did not obtain
any response then. Now being subscribed, I repost it.

Best Regards,
-- 
Dohyun Kim
http://people.ktug.or.kr/~nomos/

             reply	other threads:[~2006-11-22  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22  9:33 Dohyun Kim [this message]
2006-11-22 10:02 ` Hans Hagen
2006-11-22 10:16 ` 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=bfeb3bf10611220133x37feea5bnf51d4870ebd195de@mail.gmail.com \
    --to=nomosnomos@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).