killkolor wrote:
>> Does InDesign export broken XML documents? What exactly is your problem?
>
> yes, unfortunately it does. it uses all possible unicode characters,
> though not all are alowed in valid xml (see link in the first post).
Are you sure about this? Could you post a small example?
I
killkolor wrote:
>> Does InDesign export broken XML documents? What exactly is your problem?
>
> yes, unfortunately it does. it uses all possible unicode characters,
> though not all are alowed in valid xml (see link in the first post).
> in any way for my application i should be checking if the
On Mar 21, 8:03 am, "killkolor" <[EMAIL PROTECTED]> wrote:
> > Does InDesign export broken XML documents? What exactly is your problem?
>
> yes, unfortunately it does. it uses all possible unicode characters,
> though not all are alowed in valid xml (see link in the first post).
> in any way for m
> Does InDesign export broken XML documents? What exactly is your problem?
yes, unfortunately it does. it uses all possible unicode characters,
though not all are alowed in valid xml (see link in the first post).
in any way for my application i should be checking if the xml that
comes in is valid
In <[EMAIL PROTECTED]>, killkolor
wrote:
> I am working with InDesign exported xml and parse it in a python
> application. I learned here:
> http://boodebr.org/main/python/all-about-python-and-unicode
> that there actually are sets of illegal unicode characters for xml
> (and henceforth for every
hi!
I am working with InDesign exported xml and parse it in a python
application. I learned here:
http://boodebr.org/main/python/all-about-python-and-unicode
that there actually are sets of illegal unicode characters for xml
(and henceforth for every compliant xml parser). I already implemented
a
