I see your point, but I would not expect to approach the problem by looking around at the xml for internal labels to see how the pattern is made. To see why I say this, I suggest an exercise:
- open TAPE. Load any file of individual measurements. For example, load this one McCunn_sample.vit.vit (3.3 KB)
Observe the first two measurement names in the originator’s language. In this case, they are “height_waise_side” and “height_knee”. Those are in the language (American English) used by the creator of this file.
With the file still loaded, click the “file” menu at the top of the TAPE window, and click “Preferences” from the drop down menu. You should see something like this"
(I added the red arrow to draw your attention). If you click on the GUI language, you can select any of the supported languages. I did this with my (american english measurement) file and I clicked “Italiano”, then clicked “apply”. Most of the measurement names were instantly translated to something that I assume would be more legible to an Italian speaker than it was to me.
I suggest you try this experiment with your example file. Without having done it, I would predict that if you were to load your (Italian) pattern and its measurement file, then change the GUI language in the measurement file to English and save it then go into the preferences menu in valentina and do the same for the pattern (.vit) file and save it… I would expect you to end up with a pattern file with all english alias names in the resulting XML file.
@slpencer, could you comment and let me know whether this is an accurate expectation based on the localization features built in to TAPE and Valentina.
@KeithFromCanada this link is one explanation for the concept that I expect to apply here. Localization vs. Internationalization If I am mistaken I would like to know that