tngreene

I'm curious what is going to happen on non-Windows builds. Curious = terrified.

Steps: Make a new 2.49 file, make a cube with the name `abcdé`. Conversion gives ``` for search_obj in sorted(list(filter(lambda obj: obj.type == "MESH", search_objs)), key=lambda x: x.name): UnicodeDecodeError: 'utf-8'...

In the python editor, typing in `bpy.data.objects[` then pressing to auto complete it gives this monster. ``` Traceback (most recent call last): File "C:\Users\Ted\utils\Media\blender-2.79b-windows64\2.79\scripts\modules\console_python.py", line 264, in autocomplete private=bpy.app.debug_python) File...

When the whole text is typed out by hand, `bpy.data.objects["abcdé"]` it gives a KeyError. When starting with a new 2.79, all works completely fine. Somehow 2.49 data is tainted (who...

This bug is so spooky my computer literally Blue Screen'd while working on this. :ghost: I'm tempted to put off the alpha on that bad omen alone.

There is another idea, Test string datablock of datablock for UnicodeDecodeError, if it happens, make a copy of the datablock. Blender automatically copies everything and strips out any bad unicode...

I'd support this, but, it would be very useful if we didn't have to update all 75 callsites to make it happen. I'd like to hear if other artists would...

This would be good to solve along with #329

See also litFactor

Now that we're not deleting old idprops this bug is really just deleting lines of text