ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Dohyun Kim" <nomosnomos@gmail.com>
Subject: bugs found while trying to support utf-8 Korean Hangul under ConTeXt
Date: Sat, 21 Oct 2006 13:19:42 +0900	[thread overview]
Message-ID: <bfeb3bf10610202119l342a32ech41e16ca76cc58521@mail.gmail.com> (raw)

Hi,

http://210.94.201.157/~nomos/KTUG/context-korean-test.tar.gz (3.4Mb)

Recently I have tried to support typesetting UTF-8 Korean document
under ConTeXt.

In the course of that trying, I found some possible bugs of recent
ConTeXt beta.
You can see most of the bugs (or missing features) I found in the file
named `testme.tex',
which is contained in the tarball linked above.

For those who do not want to download that large tarball,
I here replicate those bugs or missing features:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% should be added to unic-cjk.tex
% Hangul Syllables
\dostepwiserecurse{172}{215}{1}{\expanded{\defineunicodecommand {\recurselevel}}
  {\lookaheaduchar}}
% CJK Compatibility Ideographs
\dostepwiserecurse{249}{250}{1}{\expanded{\defineunicodecommand {\recurselevel}}
  {\lookaheaduchar}}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% modify \enableunicodefont 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}% <- `%' inserted by nomos
      {\resetunicodestrut}%
   \getvalue{\??uc#1\c!commands}\relax}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% modify \sanitizePDFuniencoding in spec-tst.tex
\long\def\sanitizePDFuniencoding#1\to#2%
  {\enablePDFunicrlf
   \simplifycommands                         % <- this line inserted by nomos
   \let\unicodechar\relax % prevent further expansion
   \retainlccodes\lccode32=255 % slooow
   \lowercasestring\PDFunicodetrigger#1\to#2%
   \edef#2{\expandafter\doPDFuni#2\empty\empty}} % slooow


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% modify mps file insertion code in spec-dpx.tex
\definefileinsertion{dpx}{mps}       % tpd -> dpx modified by nomos
  {\hbox
     {\convertMPtoPDF\@@DriverImageFile{1}{1}%
      \global\let\PDFimagereference\empty}}


Certainly, the last is not problem confined to Hangul typesetting.
As you know, however, CJK peoples do use heavily dvipdfmx to obtain PDF.

Anyway, I hope these four files be modified in the near future.

In addition, when I compiled LaTeX2ConTeXt.tex by Berend de Boer
( http://www.berenddeboer.net/tex/LaTeX2ConTeXt.tex ),
I found there being inserted unintended large vertical whitespace
in page 27 of resulting PDF.
Though it seems to be a bug related to \setupbackground,
I could not find the cause of problem as the code related to that command
is too complicated for me.

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

                 reply	other threads:[~2006-10-21  4:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bfeb3bf10610202119l342a32ech41e16ca76cc58521@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).