ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ntg-context Digest, Vol 113, Issue 2
Date: Fri, 1 Nov 2013 16:16:42 +0100	[thread overview]
Message-ID: <0401D503-08AD-461B-AAFB-3CC114EE8FE6@gmail.com> (raw)
In-Reply-To: <E507DC33-C2F7-47F6-9E5E-CCCD8424C878@mac.com>

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]


Am 01.11.2013 um 16:01 schrieb Jeong Dal <haksan@mac.com>:

> Yes, there is an hanbatanglvt.lfg file.
> 	ConTeXt/tex/texmf-context/tex/context/fonts/hanbatanglvt.lfg
> But the installed font's name is "HANBatang-LVT.ttf". 
> So I changed the font name in your file from "hanbatanglvt" to "HANBatang-LVT", also I copied the above lfg file as "HANBatang-LVT.lfg" in the same folder. 

This change isn’t necessary, context refers from the normalized font name (lowercase and without hyphens etc.) to the real font with a table entry in the font database.

> Is it OK to use another Korean font?

This shouldn’t be a problem, Hans needed for his example only a font which is available for all system.

Attached is also Hans original example, this should allow you to test the feature.

Wolfgang

[-- Attachment #2: koreandemo.tex --]
[-- Type: application/octet-stream, Size: 1142 bytes --]

\starttext

\definefontfeature
 [korean-composed]
 [goodies=hanbatanglvt,
  colorscheme=default,
  mode=node,
  ljmo=yes,
  tjmo=yes,
  vjmo=yes,
  script=hang,
  language=kor]

\definefont[KoreanJMO] [hanbatanglvt*korean-composed]

\startbuffer
   % Hunminjeongeum: http://en.wikipedia.org/wiki/Hunminjeongeum
   나랏말ᄊᆞ미中듕國 귁에달아문ᄍᆞᆼ와로서르ᄉᆞᄆᆞᆺ디아니ᄒᆞᆯᄊᆡ%
   사ᄅᆞᆷ마다ᄒᆡᅇᅧ수ᄫᅵ니겨날로ᄡᅮ메便뼌安 ᅙᅡᆫ킈ᄒᆞ고져ᄒᆞᇙᄯᆞᄅᆞ미니라
\stopbuffer

\definecolor[colorscheme:100:1][r=.75]
\definecolor[colorscheme:100:2][g=.75]
\definecolor[colorscheme:100:3][b=.75]

\definecolor[colorscheme:101:1][g=.75,b=.75]
\definecolor[colorscheme:101:2][r=.75,b=.75]
\definecolor[colorscheme:101:3][r=.75,g=.75]

\startTEXpage[offset=5pt,foregroundstyle=\KoreanJMO]
                           \getbuffer \par
   \setfontcolorscheme[100]\getbuffer \par
   \setfontcolorscheme[101]\getbuffer \par
\stopTEXpage

\stoptext

[-- Attachment #3: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2013-11-01 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.97.1383316761.2136.ntg-context@ntg.nl>
2013-11-01 15:01 ` Jeong Dal
2013-11-01 15:16   ` Wolfgang Schuster [this message]
2013-11-02  7:59     ` Hans Hagen
2013-11-02  7:57   ` 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=0401D503-08AD-461B-AAFB-3CC114EE8FE6@gmail.com \
    --to=wolfgang.schuster@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).