ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: how to change 'figure 1.1' to '?? 1.1'
Date: Fri, 7 Dec 2007 16:51:21 +0100	[thread overview]
Message-ID: <6faad9f00712070751u1b67cc91uc0868650e8f3fffb@mail.gmail.com> (raw)
In-Reply-To: <D2CA3CF7-3C5E-4CCF-8BD8-97907201F024@mac.com>

On Dec 7, 2007 9:26 AM, Dalyoung Jeong wrote:
> Dear Mojca and Wolfgang,
>
> Thank you for the comments on lang-kor.tex.
>
>
> I didn't test, but I would say: forget the dirty hacks and simply write
> \setuplabeltext [\s!ko]       [\v!figure=??]
> It might not work in pdfTeX, but for XeTeX and LuaTeX it should do the job.
> Once you do those changes, feel free to ask again if you have problems (and
> don't forget to ask Hans to include the translations).
>
> I modify the files following your advice.
> It removes the middle variable "\koencoding" and make the file simpler. And
> I don't need to use "\koencoding{\enableencoding[cjk-uni]}".  It worked
> fine, also.

Nice to hear.

> But I'd like to use \setuphead for chapter, section, etc because
> our writing style of head is different from that of english.

Was that a question? What exactly would you like to achieve?

> I uploaded it in KTUG board to be checked by them, since it may be need more
> corrections.

Thans for the effort.

> By the way, do you completely resolve the "lmtypewriter10-regular" problem?
> which was discussed before in the list?

No. Perhaps \nullfont hnstead of lmtypewriter10-regular would help ... :)
I have no idea when the default font is triggered at all.

> Yesterday, after I reinstalled TeXlive and updated ConTeXt, I got "kpathsea:
> Running mktextfm lmtypewriter10-regular " message. As a temporary method,  I
> renamed mktextfm.

Just change
    MKTEXTFM = 0
in texmf.cnf

> I confirmed that such font file is in texlive opentype font folder  and
> lm*.map files in map/dvipdfm folder.

It's a weird situation. ConTeXt checks if tfm file is present first,
then, if a font with that name exists, and finally if an otf file
exists. So two failures are needed before the "dummy" useless font has
been found. That should be fixed, but ...

However, this still only affects the speed (slows it down), not the
functionality itself.

> Is there anything that I have to do more? I couldn't see the solution in the
> list.

To achive what?

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2007-12-07 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07  8:26 Dalyoung Jeong
2007-12-07 15:51 ` Mojca Miklavec [this message]
2007-12-11  0:51 Jeong Dalyoung
2007-12-11  8:36 ` Dalyoung Jeong
2007-12-11  9:33   ` Wolfgang Schuster

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=6faad9f00712070751u1b67cc91uc0868650e8f3fffb@mail.gmail.com \
    --to=mojca.miklavec.lists@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).