[ http://jira.jboss.com/jira/browse/GPD-184?page=comments#action_12388864 ] Matthias Hanisch commented on GPD-184: -------------------------------------- I faced the same problem today. processdefinition.xml is managed by WST directly and they do it correct. gpd.xml is managed manually in designer plugin (AbstractContentProvider) and there is nowhere the encoding taken into account. For the short term, I hard-coded reading and writing of gpd.xml to UTF-8 encoding. To achieve this, you have to add the encoding in getBytes() call in saveToInput() and in InputStreamReader constructor in addNotationInfo(). Of course, a complete fix would analyze the encoding of the gpd.xml file and respect that, but that's beyond my knowledge. Probably it works by just using wst methods. Note: after this change, you cannot get the notation info from already corrupted files. So it is better to remove non-ascii characters from node name attributes before applying. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/GPD-184?page=all ] Matthias Hanisch updated GPD-184: --------------------------------- Attachment: gpd-184.diff Here it is. As I said, it is only a 95% fix, because it completely ignores the encoding line of the gpd.xml file. But , for most (if not all) cases it should work, because the file has encoding "UTF-8", if created by the designer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/GPD-184?page=com.atlassian.jira.plugin... ] Koen Aers updated GPD-184: -------------------------- Fix Version/s: jBPM jPDL Designer 3.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira