> Done. But there is a problem with all the png in Dia's cvs. To be readable
> on win32 they need to be marked as binary files in cvs. Otherwise the nice
> LF -> CR,LF translation takes place ...
Oh, (sorry, I sorely lacked time to report this) ; when exporting files with
ISO8859-1 characters (such as éèàâê) (\'e\`e\'a\^a\^e in latexish) into WMF,
it looks like something in the process converts stuff into UTF8, but doesn't
do it all the way: in the final printout, you see two characters for each
original accented character (ie, you get éèà âê for the previous
string).
Looks to me that there's a conversion to wide chars somewhere, then the WMF
still thinks the result is 8859-1 [OS was NT 4.0 with whatever SP du jour,
same results with Win2K]
Hmmm.... I sense some evil between the use of ANSI_CHARSET in
wmf.cpp/set_font(), and the call to W32::TextOut in draw_string()... Which
version of TextOut is called ?
BTW, did anyone compile dia under (!msvc) ? (cygnus ?) There are a few things
I'd like to check, especially w.r.t printing and utf8 [in particular, I'd
like to make charconv.[ch] work in Win32, even if we're not going to turn
this code on for general use.
> All your signal code isn't compileable with msvc, but it is not needed on
> windoze anymore anyway. I've changed the - never working - pipe execution
> to something more appropriate for windoze. Direct writing to the default
> printer.
> [
> It is to introduce the next Win User FAQ:
> Q: When printing I get many pages of text starting with:
> %!PS-Adobe-2.0. What to do?
> A: Buy a postscript printer or implement GDI printing ... :-)
> ]
Could we instead require GhostScript and pipe stuff to it (okay, batch stuff
to it. something like:
s = tempfile.mktemp()+'.bat'
open(s,"w").write( \
"""c:\path\to\gs\gs --whatever --to --make --it --print c:\temp\foo.ps
del c:\temp\foo.ps
del s""")
#then call the regular postscript export to c:\temp\foo.ps, and finally
spawn(s)
??
-- Cyrille
--
Grumpf.
