Hi, Jeong Dalyoung wrote:
Both current version and "ConTeXt ver: 2010.05.24 13:05 MKIV fmt: 2010.5.27 int: english/english" version work same.
Why isn't it able to define "unbatangRegular" while it can use the "unbatangBold"?
Drop the [uc] and '[encoding=uc]' from your typescript: \starttypescript[serif][unbatang] \definefontsynonym[unbatangRegular][file:UnBatang.ttf] \definefontsynonym[unbatangBold][file:UnBatangBold.ttf] \definefontsynonym[unbatangItalic][file:UnGraphic.ttf] \definefontsynonym[unbatangBoldItalic][file:UnGraphicBold.ttf] \stoptypescript Explanation: The extra encoding arguments you had meant that mkiv did not actually interpret that block of code. As a result, it only saw \definefontsynonym[Serif][unbatangRegular] and that is interpreted as 'name:unbatangRegular', which is a non-existing font name. unbatangBold worked ok because name:unbatangBold actually *is* a valid font name. Best wishes, Taco