I have posted a patched version, 0.0.1a, at http://ignotus.com/ignocodelib/

If you have a moment, please give it a try.

When I set the Locale of the decimal formatting to FRANCE, numbers have commas. When I set the Locale to US, I get periods. No surprise, but I am glad to have caught this--I'm going to Paris in a week.

merci,

-- Paul

Many applications that "open" Adobe files actually access the PDF content that is saved by default in newer versions of AI. They don't parse the AI markup, since that is proprietary. Still, there was an off chance that Inkscape might parse the last public version of the file format.

Thanks for checking.

-- Paul

Hm. That's a little odd, but there are more quirks to avoiding localization than I thought.

I've uploaded a new version. It has a better chance of working. Here's the critical code:

1.     // DecimalFormat sets formatting conventions from the local system, unless we tell it not to
2.     // make sure we use "." for decimal separator, as in US, not a comma, as in many other countries
3.     static {
4.         Locale loc = Locale.US;
5.         NumberFormat nf = NumberFormat.getNumberInstance(loc);
6.         DecimalFormat fourPlaces = (DecimalFormat)nf;
7.         DecimalFormatSymbols dfSymbols = new DecimalFormatSymbols(loc);
8.         dfSymbols.setDecimalSeparator('.');
9.         fourPlaces.applyPattern("0.0000");
10.         fourPlaces.setDecimalFormatSymbols(dfSymbols);
11.     }

For the previous patch I had just:

1. static {
2.         Locale loc = Locale.US;
3.         DecimalFormatSymbols dfSymbols = new DecimalFormatSymbols(loc);
4.          fourPlaces = new DecimalFormat("0.0000", dfSymbols);
5. }

The odd thing is, setting loc = Locale.FRANCE would give me commas, so I thought that setting Locale was all that was necessary. The documentation on DecimalFormat seemed to suggest that. I sample code on the Java Tutorial ( http://download.oracle.com/javase/tutorial/i18n/format/decimalFormat.html) that suggested it wasn't quite that simple--though if it isn't, it's a puzzle why my setting the locale to FRANCE would result in comma-separated numbers.

Odd also that Java would not respond to your control panel change. Exactly the sort of thing you would expect localized code to do. I guess it's getting its cues from some other part of your system.

Anyhow, I have hopes that this new version will work so I can move this library out the door.

Another general design issue has come to mind, but I'll start a new thread for that.

thanks,

-- Paul

OOps. Forget the new version. There's a flaw. I'll have to try again.

The code suggested by the Java tutorial ( http://download.oracle.com/javase/tutorial/i18n/format/decimalFormat.html)) crashes.

1. static {
2.       Locale loc = Locale.US;
3.       NumberFormat nf = NumberFormat.getNumberInstance(loc);
4.       DecimalFormat fourPlaces = (DecimalFormat)nf;
5.       fourPlaces.applyPattern("0.0000");
6. }
7. fourPlaces.format(some_number);

It initializes just fine, but the call produces a NullPointer Exception. I thought I could trust the code from an "official" site. Hah!

So I'm back to this:

1.     static {
2.         Locale loc = Locale.US;
3.         DecimalFormatSymbols dfSymbols = new DecimalFormatSymbols(loc);
4.         dfSymbols.setDecimalSeparator('.');
5.         fourPlaces = new DecimalFormat("0.0000", dfSymbols);
6.     }

Where I have only added the setDecimalSeparator call.

I've uploaded the (non-crashing) patch now. http://ignotus.com/ignocodelib

I hope it works.

Well, hooray!

I've written a patched version of the PointText class and uploaded the distribution to http://ignotus.com/ignocodelib.

thanks,

-- Paul

Thanks to you!

I think I just need to redo the constructors to accept PApplet (easy) and modify the documentation a litlle (tedious but easy) and I should be set. Probably will do one more sample code piece on step-by-step creation of Bézier path objects and let this library out to wander.

cheers,

-- Paul

I hope it will be useful. I haven't implemented everything that Illustrator offers (and I may never write a text on a path class, given that the sample code in the AI 7.0 specification simply doesn't work), but I think the library captures a good chunk of Processing's graphics capability.

As for SVG--I had the advantage of working with some of this code over many years, in various languages, and I've never read the SVG spec. But I agree, it would be great to have an output library for a robust vector graphics format that wasn't proprietary. Just don't think I'm the one likely to do it. .