Daz Genesis Vintage Wetsuit - english file name error

ScoopeyScoopey Posts: 190
edited December 1969 in Daz Studio Discussion

Just thought I'd warn people about this seeing as though there's an offer on at the moment.
When I unzip the file using 7 zip the UV folders are renamed as

J÷rg B³sching

I've no idea how to correct the problem but I guess the original file names used special characters.
This make the product totally unusable and needs fixing!

Comments

  • DZ_jaredDZ_jared Posts: 1,316
    edited December 1969

    Tested and confirmed. I'm going to do some more messing around and see if I can find a viable work around.

  • DZ_jaredDZ_jared Posts: 1,316
    edited December 1969

    So I just tested by installing with DIM and with a DIM installation the product works fine.

  • DZ_jaredDZ_jared Posts: 1,316
    edited January 2014

    Using Windows 8 default decompression leads to the same problem. I will report this as a bug.

    *Edit* In the meantime you can rename the folders for the UV's and you won't get the missing file errors.

    If you can't type special characters you can copy this and paste this: Jörg Büsching

    Post edited by DZ_jared on
  • ScoopeyScoopey Posts: 190
    edited January 2014

    I have Windows 7 and it flags up straightaway that it uses special characters. I was already renaming them to test it and report the result but you beat me to it!
    **************************
    Confirmed - manually changing the folder name works

    Post edited by Scoopey on
  • DZ_jaredDZ_jared Posts: 1,316
    edited December 1969

    The bug has been reported, so it should be fixed fairly soon.

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    Sounds more like an OS level problem, really...what is the base/default character encoding for your system?

  • ScoopeyScoopey Posts: 190
    edited January 2014

    English - British key set!
    If I purchase a file and it refuses to decompress properly on that character set then we have real problems here.
    If DAZ_jared is using the English American key set then that will rule out the majority of users around here.
    Also the problem exists on Windows 7 and 8

    Its not the key encoding that the problem, its that the folder uses what Windows regards as illegal character. Though you can manually change it, as soon as you decompress it Windows will change the folder names.

    Post edited by Scoopey on
  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    Scoopey said:
    English - British key set!
    If I purchase a file and it refuses to decompress properly on that character set then we have real problems here.
    If DAZ_jared is using the English American key set then that will rule out the majority of users around here.
    Also the problem exists on Windows 7 and 8

    Its not the key encoding that the problem, its that the folder uses what Windows regards as illegal character. Though you can manually change it, as soon as you decompress it Windows will change the folder names.

    A UTF8/Unicode encoding wouldn't have that problem...

    And yes, Windows, by default, in the US/English speaking countries doesn't default to Unicode...but does in some others.

    And, yes, that should be something caught by QA.

    Actually, it's an out of range character, because if it were an 'illegal'/restricted character, Windows wouldn't allow you to change the name or possibly even delete it...either.

  • Richard HaseltineRichard Haseltine Posts: 102,254
    edited December 1969

    I just created a folder called Jörg Büsching in a test folder, added a text file and compressed with 7Zip. I then extracted with both Windows Compressed folders and with 7Zip - both preserved the name. That's with the UK version of Windows 7 64 bit.

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    I just created a folder called Jörg Büsching in a test folder, added a text file and compressed with 7Zip. I then extracted with both Windows Compressed folders and with 7Zip - both preserved the name. That's with the UK version of Windows 7 64 bit.

    Change your default font and try uncompressing it again...Verdana and Arial would probably be fine, NTR too...but some of the other ones, maybe not. Where the Unicode versions of them should always work...

  • Richard HaseltineRichard Haseltine Posts: 102,254
    edited December 1969

    I'm sure it can be broken - I was expecting the Windows built in archive tool to fail - but just pointing out that it isn't broken with default settings, at least in Windows 7.

  • DZ_jaredDZ_jared Posts: 1,316
    edited December 1969

    The product has been updated, so whether or not the issue was caused by the OS doesn't matter as the product will work if you download the latest version.

Sign In or Register to comment.