Re: [mdt-bpmn2.dev] BPMN2 file encoding

[Antoine Toulme <antoine@xxxxxxxxxxxxxxx>]

I am creating models programmatically, so I might be missing something. If we define a content type, we should be able to set the default encoding.

I also have seen some weird things when creating models programmatically, it looks like the wrong local name is used and the type of the object is passed in a xsi attribute. I'll open a bug with a test case.

On Fri, Jul 16, 2010 at 00:20, Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx> wrote:

Absolutely. I assume that you talk about the fact that I removed the second page of the “New BPMN 2” Wizard. In this page the user can choose the root element and the encoding of the new file. I have set the root element fixed to DocumentRoot, containing a Defintions. I also assumed that encoding will default to UTF-8, which is obviously not the case. I will fix it.

 

Von: mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] Im Auftrag von Antoine Toulme
Gesendet: Freitag, 16. Juli 2010 00:57
An: BPMN2 Developers Mailing List
Betreff: [mdt-bpmn2.dev] BPMN2 file encoding

 

Just a side note, I'm seeing the encoding of the resources we create is ASCII by default.

 

I suggest we move it to UTF-8 to avoid issues with characters. Does that seem reasonable ?

 

Thanks,

 

Antoine