What steps will reproduce the problem? 1.Export a specific bundle (bundleX) including the defined keywords and strings of the "All" bundle 2.Export as Java properties file

What is the expected output? What do you see instead? 1. I expected 1 output file: bundleX.properties 2. The bundleX.properties file contains the keywords of "BundleX" and "All", but...

During the export I get 2 seperate files: "All.properties" "BundleX.properties"

But the BundleX.properties does not contain the keywords and strings defined in the "All" bundle.

What version of the product are you using? On what operating system? TongueTied 1.1.0 on Linux MySQL 5.0 on Windows.

Please provide any additional information below. When I export the bundles to a comma seperated file the information of bundleX and All are combined.

At the moment the bundle "All" is a bit of misnomer. Any translation put in the "All" bundle is treated as belonging only to that bundle. I had the idea that there could be a global bundle(s). The name of the bundle "All" is a throw back to that idea. I was not sure if this would cause too much confusion to users and the use case for a global bundle was not clear in my mind, so I took that functionality out. I had too many open questions, for instance: - how would an import work? - how would a user exclude the global bundle? - should users even be allowed to select the global bundle for export, or should it just happen and end users be unaware?

However, maybe this is a feature that can be used optionally and I like the idea of common keywords, but I need to give the design and implementation more thought and come up with a proper use case that answers my questions.

As for CSV (and excel) the concept of a bundle to delimit output files is a bit arbitrary, so these file types will export all matching translations into one export file.

I understand the problem. Maybe you can solve it for the user by adding additional checkboxes in the export window...

Rene

It will be up to the user to decide how to handle imports. They can choose the bundle if they so wish.

Exports will be performed the same way, but the user now has an option to merge global translations. If a global translations exist for the same translation as a non-global (i.e. same language and country) then the non-global value takes preference.