Re: [NTG-context] Error with export=yes
Further, using an example with dingbats: %%% \setupbackend[export=cld-mkiv-export.xml,xhtml=cld-mkiv-export.xhtml,css={cld-mkiv-export.css,mathml.css}] \starttext Hello world! \getnamedglyphdirect{name:dingbats}{a79} \stoptext %%% Produces a broken xhtml (XML Parsing Error: not well-formed), the pdf is fine of course. The end-mark is exported to "������" in xhtml. Not sure if that's anything to fix, just wanted to let you know. Adam
On 9-5-2011 4:57, Reviczky, Adam wrote:
Further, using an example with dingbats:
%%% \setupbackend[export=cld-mkiv-export.xml,xhtml=cld-mkiv-export.xhtml,css={cld-mkiv-export.css,mathml.css}]
\starttext Hello world! \getnamedglyphdirect{name:dingbats}{a79} \stoptext %%%
Produces a broken xhtml (XML Parsing Error: not well-formed), the pdf is fine of course. The end-mark is exported to "������" in xhtml.
I don't get tha there.
Not sure if that's anything to fix, just wanted to let you know.
Anyhow, \setupbackend[export=yes] \definefontsynonym [Dingbats] [name:dingbats] [features=dingbats] \starttext Hello world! (\getnamedglyphdirect{Dingbats}{a79}) (\getnamedglyphdirect{Dingbats*dingbats}{a79}) (\getglyphdirect{Dingbats*dingbats}{\number"2756}) ({\definedfont[Dingbats]\char"2756}) \stoptext (1) will export 'v' (2) ok in next beta (3) ok (4) ok Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Anyhow,
\setupbackend[export=yes]
\definefontsynonym [Dingbats] [name:dingbats] [features=dingbats]
\starttext
Hello world! (\getnamedglyphdirect{Dingbats}{a79}) (\getnamedglyphdirect{Dingbats*dingbats}{a79}) (\getglyphdirect{Dingbats*dingbats}{\number"2756}) ({\definedfont[Dingbats]\char"2756})
\stoptext
(1) will export 'v' (2) ok in next beta (3) ok (4) ok
This is strange, attached my export and log. PDF is still fine. Do I miss something from context? Adam
On 9-5-2011 1:32, Reviczky, Adam wrote:
Anyhow,
\setupbackend[export=yes]
\definefontsynonym [Dingbats] [name:dingbats] [features=dingbats]
\starttext
Hello world! (\getnamedglyphdirect{Dingbats}{a79}) (\getnamedglyphdirect{Dingbats*dingbats}{a79}) (\getglyphdirect{Dingbats*dingbats}{\number"2756}) ({\definedfont[Dingbats]\char"2756})
\stoptext
(1) will export 'v' (2) ok in next beta (3) ok (4) ok
This is strange, attached my export and log. PDF is still fine.
Do I miss something from context?
no clue ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
no clue
So it looks like having the urw zapfding fonts from texlive mess this up (uzdr.afm, uzdr.pfb and uzdr.pfm). Don't you have them? Why is it a problem if context finds those? Without those fonts, I have this in the log: fonts > names > font database has matching configuration and file hashes fonts > defining > font with asked name 'dingbats' is not found using lookup 'name' fonts > defining > unknown font dingbats, loading aborted fonts > defining > unable to define dingbats as \**currentsymbolfont** fonts > names > font database has matching configuration and file hashes fonts > defining > font with asked name 'dingbats' is not found using lookup 'name' fonts > defining > unknown font dingbats, loading aborted fonts > defining > unable to define dingbats as \**currentsymbolfont** fonts > names > font database has matching configuration and file hashes fonts > defining > font with asked name 'dingbats' is not found using lookup 'name' fonts > defining > unknown font dingbats, loading aborted fonts > defining > unable to define dingbats as \**thedefinedfont** But now the export is fine, on the other hand the pdf misses those characters. Adam
On 9-5-2011 2:53, Reviczky, Adam wrote:
no clue
So it looks like having the urw zapfding fonts from texlive mess this up (uzdr.afm, uzdr.pfb and uzdr.pfm). Don't you have them? Why is it a problem if context finds those?
Without those fonts, I have this in the log:
fonts> names> font database has matching configuration and file hashes fonts> defining> font with asked name 'dingbats' is not found using lookup 'name' fonts> defining> unknown font dingbats, loading aborted fonts> defining> unable to define dingbats as \**currentsymbolfont** fonts> names> font database has matching configuration and file hashes fonts> defining> font with asked name 'dingbats' is not found using lookup 'name' fonts> defining> unknown font dingbats, loading aborted fonts> defining> unable to define dingbats as \**currentsymbolfont** fonts> names> font database has matching configuration and file hashes fonts> defining> font with asked name 'dingbats' is not found using lookup 'name' fonts> defining> unknown font dingbats, loading aborted fonts> defining> unable to define dingbats as \**thedefinedfont**
i use a system font ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi, Something else to play with, making an epub archive. At some point I will add support for images etc. At the end of a run you will see: export > saving specification in 'oeps.specification' (mtxrun --script epub --make oeps.specification) The mentioned mtxrun call will make an archive. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Something else to play with, making an epub archive. At some point I will add support for images etc. At the end of a run you will see:
export > saving specification in 'oeps.specification' (mtxrun --script epub --make oeps.specification)
The mentioned mtxrun call will make an archive.
Excellent, didn't expect that so soon. I'm on it! Cheers Adam
export > saving specification in 'oeps.specification' (mtxrun --script epub --make oeps.specification)
Somehow I can't get this working yet, this doesn't get triggered at my end, do I forget something? shouldn't also back-exp.lua line 406: - handle:write(" url='",file,"'") + handle:write(" url='",url,"'") Adam
Am 09.05.2011 um 18:48 schrieb Reviczky, Adam:
export > saving specification in 'oeps.specification' (mtxrun --script epub --make oeps.specification)
Somehow I can't get this working yet, this doesn't get triggered at my end, do I forget something?
Do you set a value for the xhtml key? Wolfgang
participants (3)
-
Hans Hagen -
Reviczky, Adam -
Wolfgang Schuster