Re: [NTG-context] Unicode Character Problem

2007-01-16 Thread Johannes Graumann
Mojca Miklavec wrote:

 I'm having trouble defining a new unicode character:

 'versuch.tex' reads:
   \defineXMLentity[\#9633]  {\symbol[8]}
 
 It should be
  \defineXMLentity[9633]  {\symbol[8]}
That's not right. I verify my xml with kxmleditor and '#9633;' is accepted,
while '9633;' causes an error to be thrown.

 XeTeX is already there (and your square sample is also working there
 out-of-the-box once you set a proper font).
I'll look into that. 

Thanks, Joh

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


Re: [NTG-context] Unicode Character Problem

2007-01-16 Thread Mojca Miklavec
On 1/16/07, Johannes Graumann wrote:
 Mojca Miklavec wrote:

  I'm having trouble defining a new unicode character:
 
  'versuch.tex' reads:
\defineXMLentity[\#9633]  {\symbol[8]}
 
  It should be
   \defineXMLentity[9633]  {\symbol[8]}
 That's not right. I verify my xml with kxmleditor and '#9633;' is accepted,
 while '9633;' causes an error to be thrown.

No, you don't need to modify XML, only the definition in ConTeXt:

This example works here:

\defineXMLentity[9633]{\symbol[8]}
\starttext
\startXMLdata
#9633;
\stopXMLdata
\stoptext

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


Re: [NTG-context] Unicode Character Problem

2007-01-11 Thread Mojca Miklavec
On 1/8/07, Johannes Graumann wrote:
 Hello,

 I'm having trouble defining a new unicode character:

 'versuch.tex' reads:
   \defineXMLentity[\#9633]  {\symbol[8]}

It should be
 \defineXMLentity[9633]  {\symbol[8]}

 'versuch.xml' reads:
   #9633;

 Trying to compile this like so:
   texmfstart texexec --environment=versuch.tex versuch.xml

 I think I figured this out: '9633' is not in a unicode block as predefined in
 unic-xxx.tex

 So this doesn't work ... looks like I have to wait for LuaTeX ...

XeTeX is already there (and your square sample is also working there
out-of-the-box once you set a proper font).

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


Re: [NTG-context] Unicode Character Problem

2007-01-09 Thread Johannes Graumann
I think I figured this out: '9633' is not in a unicode block as predefined in
unic-xxx.tex

So this doesn't work ... looks like I have to wait for LuaTeX ...

Joh


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


[NTG-context] Unicode Character Problem

2007-01-08 Thread Johannes Graumann
Hello,

I'm having trouble defining a new unicode character:

'versuch.tex' reads:
  \defineXMLentity[\#9633]  {\symbol[8]}

'versuch.xml' reads:
  #9633;

Trying to compile this like so:
  texmfstart texexec --environment=versuch.tex versuch.xml

Yields the error below. What am I doing wrong (this works for other things like
'\defineXMLentity[\#8211]{--}')?

Thanks for your insights!

Joh

kpathsea: Running mktexmf UnicodeRegular25
! I can't find file `UnicodeRegular25'.
* ...mag:=1; nonstopmode; input UnicodeRegular25

Please type another input file name
! Emergency stop.
* ...mag:=1; nonstopmode; input UnicodeRegular25

Transcript written on mfput.log.
grep: UnicodeRegular25.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input
UnicodeRegular25' failed to make UnicodeRegular25.tfm.
kpathsea: Appending font creation commands to missfont.log.

! Font \unicodefont=UnicodeRegular25 at 12.0pt not loadable: Metric (TFM) file
not found.
recently read \bodyfontsize

\unicodeglyph ... \currentfontscale \bodyfontsize
  \unicodestrut \unicodefont...

\uchar ...+\unicodetwo \relax \handleunicodeglyph
  \endgroup
l.1 #9633;

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