.resx files

I've reviewed the translated bundle I sent to the translator, but when I look at the .resx files in the original folder, they have the current date but the file size for all of the .resx files are 6 KB. What am I doing wrong? Thanks

  • Hi Dawn,

    What was the file size for the source resx files? Have you looked in the files with an editor to see if they look ok?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Hi Paul, how are you? Thank you for responding. The original .resx files had size (various KB were displayed). After I bundled the project the .resx files all changed to 6 KB. I sent the bundles to the translators and they finished them. Now, when I look at the translated strings in Passolo, I can see the various sizes of the strings. I've validated the translations and saved them but the size of the original .resx files still say 6KB even though there was size to them originally and in Passolo. (I'm still fairly new to managing software translations for our software.) I've only done this process a few times before so I have a feeling there's a step I'm missing. I've searched the documentation and various sites but I haven't been able to find any suggestions or steps to fix my problem. I hope this makes sense.
  • There is no relation between RESX files and bundles within the workflow. So I assume that you really send bundles to translators not the RESX files. After re-importing the bundles from the translators you generate the target files on your system and they seem to be smaller than the original, right?

    According to the standard localization concept for RESX files that was created by Microsoft this behavior is correct. Don’t worry. Only changed (translated) entries will be stored in the translated RESX files. This explains the smaller size. Nevertheless your client that generates the translated software will be able to work with these smaller files. The missing content is automatically taken from the source (fallback option) which again is part of Microsoft's localization concept.

    If necessary you can create a full translated RESX file if the client is requesting it by deactivating the .NET parser option Write only changed information.

    Hope this helps.