We are trying to open xlf 2.0 files on Studio 2015 SR 3 and 2017 and we have found a bug related to the decimals. Apparently, when numbers inside the files are in this format: "100.0", we are not able to open the files. We need to manually change the number to "100" using NotePad or any other editor, removing the ".0" part and making them editable.
Is there a way we can automatically change all those ".0" numbers to whole, non-decimal numbers?
Thank you.
This looks indeed like a bug... Studio apparently tries to read the file using the UI language locale settings and therefore expects the number to use comma as decimal separator. Which is incorrect since XLIFF 2.0 specification expects decimal point: http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#similarity
I would say it has similar roots as the long-standing bug with Studio not remembering the window size when running on locale settings with different list separator than comma (e.g. Czech locale uses semicolon) - despite being set to English UI language, Studio reads the window coordinates/size from UserSettings.xml using Czech settings, thus fails to understand the values separated by comma in the XML and falls back to default window position and size.
This problem started appearing with Studio 2015 (apparently due to some internal coding screwup when parts of the application were refactored/rewritten) and was just ignored since then...
EDIT: Studio 2017 CU10 seems to finally restore the window position/size correctly. Studio 2015 CU10 still doesn't.
This looks indeed like a bug... Studio apparently tries to read the file using the UI language locale settings and therefore expects the number to use comma as decimal separator. Which is incorrect since XLIFF 2.0 specification expects decimal point: http://docs.oasis-open.org/xliff/xliff-core/v2.0/os/xliff-core-v2.0-os.html#similarity
I would say it has similar roots as the long-standing bug with Studio not remembering the window size when running on locale settings with different list separator than comma (e.g. Czech locale uses semicolon) - despite being set to English UI language, Studio reads the window coordinates/size from UserSettings.xml using Czech settings, thus fails to understand the values separated by comma in the XML and falls back to default window position and size.
This problem started appearing with Studio 2015 (apparently due to some internal coding screwup when parts of the application were refactored/rewritten) and was just ignored since then...
EDIT: Studio 2017 CU10 seems to finally restore the window position/size correctly. Studio 2015 CU10 still doesn't.
Translate
