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.

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.