Re: [NTG-context] ec-lmr12 not loadable: Metric (TFM) file

2007-11-06 Thread Mojca Miklavec
On 11/5/07, Dalyoung Jeong wrote:
 Dear Mojca,

 Thank you for the reply. As you did, I send my problem to the list. I
 think that I am a problem maker.

 I wonder why the output of XeTeX+ConTeXt was changed after the upgrade
 to Leopard.
 I didn't change anything in TeX system. I just upgraded the OSX.
 But nicely working XeTeX+ConTeXt had a problem with the korean
 commercial fonts.(no korean letters were  appeared.)

 I installed TeXlive using i-installer(gwTeX) with Mac OSX Leopard,
 Latest stable ConTeXt, XeTeX 0.996

 I made a short test file and a typescript file for the test.
 I have tested in several ways.

 4. I used typescript file type-xkor2.tex

 No error message. English letters are OK.
 But  korean letters(except the manually defined korean font) and the
 greek capitals are appeared as blanks.

I cannot test on Leopard, but I can comment about problems I
experience on Tiger:

1.) Capital Greek letters:

\starttypescript[myface]
 \definetypeface[Myface][rm][serif][testrm][default]

% you definitely need this line, really:
% note the word modern in the last bracket!!!
% (I had quite some problems at this point as well)
 \definetypeface [Myface][mm][math][modern][modern]
\stoptypescript

2.) You have typos in your typescript file:
 \starttypescript[serif][tesetrm][name]
should be testrm, not tesetrm

3.) This only applies to the *latest stable version* (please upgrade
to 29.09.2007!) of ConTeXt: you should rewrite your typescript
definitions to:

\starttypescript[serif][testrm]
% Regular variant:
 \definefontsynonym[MyungjoRegular][file:smGothicR W35][features=default]
 \definefontsynonym[MyungjoLight][file:smHangSer Medium]
 \definefontsynonym[MyungjoBold][file:smJohabP Medium]
\stoptypescript

[features=default] at the end is kind-of-optional (I'm not sure about
which features should be applied to Korean fonts, that's why I'm not
sure if features=default is OK or not, but you should eiter apply it
to all font instances or to none of them).

3.a) the prefix file: is not needed. I have placed the font files in
the same folder where the tex file is. Actually, if you have your font
installed, you might need to use other names. If you're referring to a
font in file, you can provide a file: prefix and need to suppy file
name. If you're referring to an installed font, you need to provide
the font name (which might be different from file name - I didn't
check the font name of the fonts you provided), and you might provide
name: prefix (optional, but more efficient).

3.b) There seems to be a bug in ConTeXt (if you don't provide file:
prefix, ConTeXt puts spurious FontName at 9pt over all the place).
But I will report that problem to Hans separately.

 I think that Leopard has a problem with xdvipdfmx. It is just my guess.


Can you try to use the latest ConTeXt (install ConTeXt updater package
in gwTeX) and the attached typescript file? (Your file doesn't work on
Tiger without modifications either.)

Can you try to compile your plain XeTeX files with
xetex -output-driver=xdvipdfmx -E -d 4 -V 5 filename.tex
That way it will be easier to test if the problem lies in xdvipdfmx
than if you try to convince ConTeXt to use the xdv2pdf driver.

Mojca

 I attached test file and a typescript file. I used some commercial
 fonts but they are freely distributed as demo at the following site: 
 www.softmagic.co.kr
   After connecting it, you can see otf sm font in the third
 rectangle at the right side of the frame. You can download 5 fonts. I
 used three of them in the typescript file and one of them in the test
 file.


type-xkor3.tex
Description: TeX document
___
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
___


Re: [NTG-context] ec-lmr12 not loadable: Metric (TFM) file

2007-11-05 Thread Dalyoung Jeong

Dear Mojca,

Thank you for the reply. As you did, I send my problem to the list. I  
think that I am a problem maker.


I wonder why the output of XeTeX+ConTeXt was changed after the upgrade  
to Leopard.

I didn't change anything in TeX system. I just upgraded the OSX.
But nicely working XeTeX+ConTeXt had a problem with the korean  
commercial fonts.(no korean letters were  appeared.)


I installed TeXlive using i-installer(gwTeX) with Mac OSX Leopard,  
Latest stable ConTeXt, XeTeX 0.996


I made a short test file and a typescript file for the test.
I have tested in several ways.

1. In XeTeX, everything is OK.  Korean letters and greek capitals are  
appeared well. I thinkt that it used xdv2pdf.


This is XeTeXk, Version 3.141592-2.2-0.996 (Web2C 7.5.6)
 file:line:error style messages enabled.
entering extended mode
(./test-font.tex [1] )
(see the transcript file for additional information)
Mon Nov  5 16:56:15 graph.ssu.ac.kr xdv2pdf[21489] Error: WARNING:  
Type1 font data returned by OFAStreamPSDownload isn't in the correct  
format required by the Adobe Type 1Font Format specification.

...
Output written on test-font.pdf (1 page).
Transcript written on test-font.log.

after adding \starttext and \stoptext
2. In XeTeX+ConTeXt, no ouput because of the korean commercial font.

[1
** NOTICE: This document contains a `Preview  Print only' licensed  
font **

]
** ERROR ** CFF: Invalid character.

Output file removed.
Output written on test-font.pdf (1 page).
Transcript written on test-font.log.

3.In XeTeX+ConTeXt without the definition of the korean commercial font:

No error messeges, defined korean font and greek capitals are appeared  
well.
But korean letters(except the manually defined korean font) are  
appeared as blanks. English letters are OK.


4. I used typescript file type-xkor2.tex

No error message. English letters are OK.
But  korean letters(except the manually defined korean font) and the  
greek capitals are appeared as blanks.


I think that Leopard has a problem with xdvipdfmx. It is just my guess.

I attached test file and a typescript file. I used some commercial  
fonts but they are freely distributed as demo at the following site: www.softmagaic.co.kr 
  After connecting it, you can see otf sm font in the third  
rectangle at the right side of the frame. You can download 5 fonts. I  
used three of them in the typescript file and one of them in the test  
file.


Thank you again.
Best regards,

Dalyoung


test-font.tex
Description: Binary data


type-xkor2.tex
Description: Binary data
___
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
___


Re: [NTG-context] ec-lmr12 not loadable: Metric (TFM) file ... not found

2007-03-13 Thread Hans Hagen
Mojca Miklavec wrote:
 On 3/9/07, Akira Kakuto wrote:
   
 Hi Mojca,

 
 Well, OK, that's understandable. That's just an accidental mix-up with
 otf files in ConTeXt. Line 73 of font-ini.mkii should read
 \def\fontfilesome#1{#1}
 instead of
 \def\fontfilesome#1{[#1]}
   
 Please check my previous mail with care
  \def\fontfilesome#1{#1}
 should be
  \def\fontfilesome#1{#1}
 (note that there is no quotation).

 If you use \def\fontfilesome#1{#1}, XeTeX tries to find
 OpenType or TrueType font #1 by using fontconfig, and fails.
 

 I was blindly looking to the right point, but didn't notice the most
 obvious thing. I'm sorry for the noise and thanks for pointing this
 out again.

 Hans, can you please replace the following block of code in
 font-ini.mkii? (Please also include lm-ec.map into the ConTeXt zip if
 possible - you may throw it out again as soon as the typescripts for
 OpenType LM are ready.)


 \def\fontfilename#1{#1}
 \def\fontfilefile#1{#1}
 \def\fontfilesome#1{#1} % I don't know about the two above, but  doesn't work

 \beginXETEX

 \def\fontfilename#1{#1}
 \def\fontfilefile#1{[#1]}
 \def\fontfilesome#1{#1}

 \endXETEX

 Or perhaps:

 \def\fontfilename#1{#1}
 \def\fontfilefile#1{#1}
 \def\fontfilesome#1{#1}

 \beginXETEX
 \def\fontfilefile#1{[#1]}
 \endXETEX

   
sure, as long as you do the testing

Hans 

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context