> 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 ___________________________________________________________________________________ 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 ___________________________________________________________________________________
