*printf() exhibits locale-dependent behavior on win32; we need to replace it with our own code for generating correct SVG measurements regardless of locale.
If not for this problem, does printf satisfy our requirements or are there any other problems with it? If it's OK, maybe we could just include the "standard" printf right into our codebase, instead of linking to a library? Just an idea.
_________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...
On Fri, 2003-12-12 at 17:56, bulia byak wrote:
*printf() exhibits locale-dependent behavior on win32; we need to replace it with our own code for generating correct SVG measurements regardless of locale.
If not for this problem, does printf satisfy our requirements or are there any other problems with it? If it's OK, maybe we could just include the "standard" printf right into our codebase, instead of linking to a library? Just an idea.
Possibly, but if we do one ourselves we can be more clever with e.g. rounding behavior. Anyway, Bryce said he alraedy had some code somewhere, as I recall...
-mental
On Fri, 12 Dec 2003, MenTaLguY wrote:
On Fri, 2003-12-12 at 17:56, bulia byak wrote:
*printf() exhibits locale-dependent behavior on win32; we need to replace it with our own code for generating correct SVG measurements regardless of locale.
If not for this problem, does printf satisfy our requirements or are there any other problems with it? If it's OK, maybe we could just include the "standard" printf right into our codebase, instead of linking to a library? Just an idea.
Possibly, but if we do one ourselves we can be more clever with e.g. rounding behavior. Anyway, Bryce said he alraedy had some code somewhere, as I recall...
Yes, I do. I've added a task for myself to add this to the codebase.
Bryce
participants (3)
-
Bryce Harrington -
bulia byak -
MenTaLguY