Sapling tree gen error when objects have åäö in the name #51157

New Issue

Novice · 2017-04-08T15:43:22+02:00

Novice commented

2017-04-08 15:43:22 +02:00

System Information
Windows 10 Home (Swedish language)
GTX 1070

Blender Version
Broken: 2.78c
Worked: 2.77a (on windows 7)

Short description of error
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x85 in position 3: invalid start byte

Exact steps for others to reproduce the error
Start blender. Rename default cube to Låda (any name with lowercase åäö will do). User preferences->Addons-> Add Curve: Sapling Tree Gen.
Shift-A->Curve->Sapling Tree Gen.

blender_sapling_error.blend

**System Information** Windows 10 Home (Swedish language) GTX 1070 **Blender Version** Broken: 2.78c Worked: 2.77a (on windows 7) **Short description of error** UnicodeDecodeError: 'utf-8' codec can't decode byte 0x85 in position 3: invalid start byte **Exact steps for others to reproduce the error** Start blender. Rename default cube to Låda (any name with lowercase åäö will do). User preferences->Addons-> Add Curve: Sapling Tree Gen. Shift-A->Curve->Sapling Tree Gen. ![blender_sapling_error.png](https://archive.blender.org/developer/F539517/blender_sapling_error.png) [blender_sapling_error.blend](https://archive.blender.org/developer/F539519/blender_sapling_error.blend)

Novice commented

2017-04-08 15:43:22 +02:00

Changed status to: 'Open'

Novice commented

2017-04-08 15:43:22 +02:00

Added subscriber: @BlenderAmateur

Aaron was assigned by Aaron Carlisle

2017-04-08 20:04:49 +02:00

Aaron commented

2017-04-09 20:58:51 +02:00

I was able to replicate this, but inconsistently. Can anyone confirm if this is a blender issue or something addons need to handle themselves. If it's the addon then how do I fix it?, because I do not know what's causing this.

Aaron Carlisle commented

2017-04-10 02:39:46 +02:00

Added subscriber: @mont29

mathieu menuet commented

2017-04-10 08:10:45 +02:00

Added subscriber: @bliblubli

mathieu menuet commented

2017-04-10 08:10:45 +02:00

@Abpy Blender and Python both can handle UTF-8 correctly. But maybe see https://developer.blender.org/T50926, because python on windows by default doesn't use UTF-8 encoding everywhere.

Brendon Murphy commented

2017-04-21 01:59:03 +02:00

Added subscriber: @BrendonMurphy

Brendon Murphy commented

2017-04-21 01:59:03 +02:00

hi, I was under the impression that py does not handle special text characters.
possibly we could add the unicode block to the addon?
https://wiki.blender.org/index.php/Dev:Doc/Code_Style says to avoid special characters

hi, I was under the impression that py does not handle special text characters. possibly we could add the unicode block to the addon? https://wiki.blender.org/index.php/Dev:Doc/Code_Style says to avoid special characters

Aaron Carlisle commented

2017-04-21 05:32:40 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2017-04-21 05:32:40 +02:00

@BrendonMurphy that is in the code, not as a user.

Brendon Murphy commented

2017-04-22 12:17:20 +02:00

@Blendify, I'll seek clarify adding priority normal,

Aaron commented

2017-05-15 03:13:57 +02:00

I have a workaround that uses base64 to pass the string through the addon. It lets you choose the objects but still doesn't show the correct object name in the menu.

Brendon Murphy commented

2017-05-28 05:18:57 +02:00

hi testing this (following exact reproduce from op) I was able to get the error using the presets & also in ui.
adding

# -*- coding: utf-8 -*-

to the file header (line1) in init.py & utils.py
& I cannot reproduce the issue

will commit fix soon

hi testing this (following exact reproduce from op) I was able to get the error using the presets & also in ui. adding ``` # -*- coding: utf-8 -*- ``` to the file header (line1) in __init__.py & utils.py\ & I cannot reproduce the issue will commit fix soon

blender-admin commented

2017-05-28 09:40:06 +02:00

This issue was referenced by ba6a119db2

This issue was referenced by ba6a119db23a04dadf52c7f46bc4c62926c60625

Brendon Murphy commented

2017-05-28 09:40:51 +02:00

Changed status from 'Open' to: 'Resolved'

Brendon Murphy closed this issue

2017-05-28 09:40:51 +02:00

Aaron commented

2017-05-28 18:26:48 +02:00

awesome, I didn't know file encodings could cause things like this. Its a lot better than my ugly workaround. thanks.