I'm having same error message with FME 2019, my layer names contain scandinavic letters ä and ö. Using RealDWG reader, group entities: by layer this error appears, but with grouping by geometry, its fine.
Hi @oscard
I'm using the FME 2019 and I tried to inspect this error with layers in Portuguese language - for example layer name: Numeração.
The read action was perfect in my machine.
Thanks,
Danilo
Hi @oscard
I'm using the FME 2019 and I tried to inspect this error with layers in Portuguese language - for example layer name: Numeração.
The read action was perfect in my machine.
Thanks,
Danilo
Did you use the "Single Merged Feature" in the Reader?
Did you use the "Single Merged Feature" in the Reader?
Yes, I used it
If you get rid of the feature type public parameter or if you switch to fixed list (reimporting the layer names from your dataset there) then fme protects those characters.
Did you use the "Single Merged Feature" in the Reader?
Could you share this data that I can do test here in my machine, if you want.
Thanks
Danilo
Hi @oscard
I'm using the FME 2019 and I tried to inspect this error with layers in Portuguese language - for example layer name: Numeração.
The read action was perfect in my machine.
Thanks,
Danilo
Hi Danilo
Please have a look at case C144251. It's similar to this and contains our findings (issue is with Feature Types to Read parameter)
Kind regards,
Petri
Could you share this data that I can do test here in my machine, if you want.
Thanks
Danilo
Thanks for offering, but I can't share the data. I will work with FME 2018 for this project.
Thanks for offering, but I can't share the data. I will work with FME 2018 for this project.
Ok. No problem.
Thanks,
Danilo
Hi @oscard, hi @kino
this sounds like a bug to me. I have filed FMEDESKTOP-8904 bug report asking to investigate the problem. We do have some non-English data samples, so we do have something to test with, however, if you could provide us with your actual data samples it would be helpful too.
Sorry for the inconvenience. I hope we will find the root of the problem and will be able to fix in 2019.1 release.
Hi @oscard, hi @kino
this sounds like a bug to me. I have filed FMEDESKTOP-8904 bug report asking to investigate the problem. We do have some non-English data samples, so we do have something to test with, however, if you could provide us with your actual data samples it would be helpful too.
Sorry for the inconvenience. I hope we will find the root of the problem and will be able to fix in 2019.1 release.
I will ask if I can provide you with the data. Where should I send it to?
I will ask if I can provide you with the data. Where should I send it to?
Hi @oscard We'd created a case and sent you an email, so you can respond to it with the data. Thanks very much!
Hi @oscard
I'm using the FME 2019 and I tried to inspect this error with layers in Portuguese language - for example layer name: Numeração.
The read action was perfect in my machine.
Thanks,
Danilo
Hello @danilo_fme
I ran into the same issue, this worked fine in FME 2018.
Seems like 2019 (Build 19246) doesn't like German very much.
It's complaining about "_zum Abkl\\xC3\\xA4ren", which is probaby "_zum Abklären"?
Especially on feature names.
Super easy to reproduce, I attached a DWG with a Layer "_zum Abklären": FME 2019 String Test.dwg
Could you take a look?
Hello @danilo_fme
I ran into the same issue, this worked fine in FME 2018.
Seems like 2019 (Build 19246) doesn't like German very much.
It's complaining about "_zum Abkl\\xC3\\xA4ren", which is probaby "_zum Abklären"?
Especially on feature names.
Super easy to reproduce, I attached a DWG with a Layer "_zum Abklären": FME 2019 String Test.dwg
Could you take a look?
Hi @ras, Thank you for letting us know about this. It does sound quite suspicious. One of our experts is looking into it. We'll try to get back to you in the next few days.
In the meanwhile, can you please tell us what is the System Locale setting you are using? (In case you've not checked it before, this quick video shows you how). This info will help us investigate the issue.
Thank you!
Hi @ras, Thank you for letting us know about this. It does sound quite suspicious. One of our experts is looking into it. We'll try to get back to you in the next few days.
In the meanwhile, can you please tell us what is the System Locale setting you are using? (In case you've not checked it before, this quick video shows you how). This info will help us investigate the issue.
Thank you!
@xiaomengatsafe
Ok, thanks. My system locale settings say "German (Germany)".
Hello @danilo_fme
I ran into the same issue, this worked fine in FME 2018.
Seems like 2019 (Build 19246) doesn't like German very much.
It's complaining about "_zum Abkl\\xC3\\xA4ren", which is probaby "_zum Abklären"?
Especially on feature names.
Super easy to reproduce, I attached a DWG with a Layer "_zum Abklären": FME 2019 String Test.dwg
Could you take a look?
Hi @ras
I have tried reading your data with
- Autodesk AutoCAD DWG/DXF,
- Autodesk AutoCAD RealDWG DWG/DXF,
- Autodesk AutoCAD Map 3D Object Data, and
- Autodesk AutoCAD Civil 3D
Readers using FME 2019.0 build 19246 and was not able to reproduce the problem. On German (Germany) locale, every Reader added _zum Abklären layer and read the single feature placed on this layer successfully.
Could you please create a workspace with one (or all) DWG Reader(s) added and run the workspace attempting to read 26710-fme-2019-string-test.dwg? If you could then share the workspace and the translation log with us, it would be very helpful. I hope we will solve this mystery.
Hi @ras
I have tried reading your data with
- Autodesk AutoCAD DWG/DXF,
- Autodesk AutoCAD RealDWG DWG/DXF,
- Autodesk AutoCAD Map 3D Object Data, and
- Autodesk AutoCAD Civil 3D
Readers using FME 2019.0 build 19246 and was not able to reproduce the problem. On German (Germany) locale, every Reader added _zum Abklären layer and read the single feature placed on this layer successfully.
Could you please create a workspace with one (or all) DWG Reader(s) added and run the workspace attempting to read 26710-fme-2019-string-test.dwg? If you could then share the workspace and the translation log with us, it would be very helpful. I hope we will solve this mystery.
@lenaatsafe
Hello, thanks for the effort so far, I appreciate it.
This is a bit of a puzzle.
- Just to confirm, in FME 2018 (Build 18592), no issues:
- In FME 2019 (19246), doesn't matter which DWG reader:
ACAD reader: The encoded string is not a valid fme-wwjd string: '_zum Abkl\\xC3\\xA4ren'
MULTI_READER(MULTI_READER): Skipping to next Reader
REALDWG reader: The encoded string is not a valid fme-wwjd string: '_zum Abkl\\xC3\\xA4ren'
MULTI_READER(MULTI_READER): Skipping to next Reader
AUTOCAD_OD reader: The encoded string is not a valid fme-wwjd string: '_zum Abkl\\xC3\\xA4ren'
MULTI_READER(MULTI_READER): Skipping to next Reader
I'm out of ideas.
I have similar problems with German layer- and filenames. I just installed the latest built (19608) but the problems are still the same:
Is there any progress?
I have similar problems with German layer- and filenames. I just installed the latest built (19608) but the problems are still the same:
Is there any progress?
Hi @florian,
Unfortunately, no update just yet. If you would like to be notified via email when there is an update to the status of FMEENGINE-59779, please submit a case using out
Report a Problem webform and reference FMEENGINE-59779 in the comments box.
Hi @oscard, hi @kino
this sounds like a bug to me. I have filed FMEDESKTOP-8904 bug report asking to investigate the problem. We do have some non-English data samples, so we do have something to test with, however, if you could provide us with your actual data samples it would be helpful too.
Sorry for the inconvenience. I hope we will find the root of the problem and will be able to fix in 2019.1 release.
Hi! Any news about this issue?
Hi! Any news about this issue?
I encounter the same problems with french accents.
Unicode programming error, looks like.
Hi! Any news about this issue?
Unfortunately there is no solution yet, but I will do what I can to increase the priority for this issue. Apologies for the inconvenience and thanks for your patience.
Hey folks, just to let you know that I got in touch with the development team responsible for this. Ironically (if that's the word) I missed their weekly meeting this morning by a few minutes, so we'll have to wait until next week for them to look at the issue. But I'm told it is now a "priority fix" and so I hope to see some action on it shortly. I've asked for it to go into a 2019.2.x service pack, so we'll see if that can happen.
In short: things are moving and I'm hopeful of (though don't guarantee) a fix in the coming weeks.
Hi all. Good news. I am told that this issue is fixed. The fix is in FME 2019.2 as of build 19806. You may have to re-add the reader (I'm not sure) and if for some reason it still causes a problem, then please let us know.
Regards
Mark
