UTF8 encoding bug in part u588p02c03.dat?

[Roland Melkert]

During fixing of utf8 handling in LDCad I stumbled on this part: "u588p02c03.dat".

One of the keyword lines seems mangled. Even in utf8 editors (it comes out partly Korean or something).

This can't be right?

The line above it (with elephant etc) does contains valid utf8 coding though.

[Steffen]

no, the file is correct :-)

it contains these characters:
エドワードエレファント

Try pasting them into Google translate :-)

we took them from a Korean Fabuland book...

Now that our LDRAW files are UTF-8 there's no reason that we stick to the English-speaking world ;-)

You can e.g. confirm that the file is correct by opening it with a good UTF-8 capable tool.

Microsoft Word for example will recognize the file as UTF-8 encoded and show all characters correctly.

[Jim DeVona]

Huh, cool. Looks correct in Bricksmith, FWIW:



I had no idea I had elephant-men in my LDraw library.

[Roland Melkert]

Steffen Wrote:
-------------------------------------------------------
> no, the file is correct :-)
>
> it contains these characters:
> エドワードエレファント
>

Ah ok, for some reason it didn't look 'completely' Korean to me, probably because of the 'I' en '-' looking chars I guess.

Just wanted to be sure my code handles it correctly.

Thanks

[Steffen]

...for the proper UTF-8 handling of this forum :-)

[Steffen]

sorry: not Korean. instead: Japanese.

I had remembered wrongly what we did on the PT when releasing the part.

[Jean-Philippe Ouellet]

Is there someplace where the old PT votes and comments are stored for currently official parts, just for reference to see how things were resolved in the past in order to establish precedent, etc. (for those of us who weren't around at the time and thus can't simply remember).

[Chris Dee]

Yes, but I don't think this would be useful to provide access to this - the Parts Tracker should not become a discussion forum. Library-wide decisions that are taken during review on the Parts Tracker should be documented elsewhere.