Bug 100792 - Language files are not transported in Library export and import
Summary: Language files are not transported in Library export and import
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Macro-UI
  Show dependency tree / graph
 
Reported: 2016-07-06 20:32 UTC by Regina Henschel
Modified: 2023-04-29 11:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Includes Basic library with Language files (23.07 KB, application/vnd.oasis.opendocument.graphics)
2016-07-06 20:32 UTC, Regina Henschel 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2016-07-06 20:32:29 UTC 
Created attachment 126094 [details]
Includes Basic library with Language files

Open attached file. It contains a macro library with macros to set the handles of a 'block arc' shape or a 'circular arrow' shape numerically in a dialog. This dialog has localized strings for English(USA) and German. If you call the macros with LO in a German UI you get German strings in the dialog, if you call the macros with LO in an English UI you get English strings in the dialog.

To test it, draw a block arc and while it is selected call the macro "EditBlockArc" from module 'Arc' in the library 'BlockArrowEditor'.

Now export the library either as Basic or as extension. When you import this exported library to some other file or in your 'My Macros' folder and then call the macros again, you will notice, that the dialog has no strings, but the references.

If you look into the exported library, you will notice, that the files 'DialogStrings_de_DE.properties' , 'DialogStrings_en_US.default' and 'DialogStrings_en_US.properties' are missing. If you extract these file from the source document and copy them over to the target "BlockArrowEditor"-folder, then the dialog will show localized strings as it should.

To test, that the import is broken too, copy the files manually into the exported library and then import the library to your target.

Export and Import is done with the Macro Organizer.
Comment 1 Joel Madero 2016-07-08 05:04:34 UTC 
@Regina - not going to test myself. Confident this is a valid report.

Marking as NEW.

If this is a new problem can you add "regression" to keyword. Also, if I'm not mistaken, seems like a minor problem (slows down but does not prevent high quality work)? If so, can you mark it as such? 

Thanks!
Comment 2 Regina Henschel 2016-07-08 13:25:06 UTC 
Those, who are able to write macros with support for different languages, are likely able to copy paste the needed files manually. Therefore I agree with "low".
Comment 3 QA Administrators 2017-09-01 11:15:57 UTC Comment hidden (obsolete)
Comment 4 Regina Henschel 2017-09-01 13:13:38 UTC 
I have tested it with Version: 6.0.0.0.alpha0+
Build ID: 4c99b8a9de59f3c5280ff2944d9f828822897f4a
CPU threads: 4; OS: Windows 6.1; UI render: default; 
Locale: de-DE (de_DE); Calc: group

Export works now.
Import works with extension.
But Import is still broken with Basic library.

Import as Basic library is needed, if you will include the library in a document.
Comment 5 QA Administrators 2018-09-02 02:50:20 UTC Comment hidden (obsolete)
Comment 6 Regina Henschel 2018-09-02 11:13:40 UTC 
Import of Basic library into a document is still broken in Version: 6.1.0.3 (x64)
Build-ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard; 
Gebietsschema: de-DE (en_US); Calc: CL
Comment 7 Regina Henschel 2018-09-02 15:40:36 UTC 
And in Version: 6.2.0.0.alpha0+ (x64)
Build ID: a201c5c8c3e7ea14001b5634f330dbce2b1f4314
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
Locale: en-US (en_US); Calc: CL

the export is broken again, both for BASIC library and for extension.
Comment 8 QA Administrators 2019-09-03 16:12:15 UTC Comment hidden (obsolete)
Comment 9 Regina Henschel 2019-12-04 13:47:40 UTC 
The error still exists in Version: 6.5.0.0.alpha0+ (x64)
Build ID: 800b6f095f95ccfb8a7ba9755292332bf97f97ad
CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; 
Locale: de-DE (en_US); UI-Language: en-US
Calc: threaded
Comment 10 QA Administrators 2021-12-06 04:04:49 UTC Comment hidden (obsolete)
Comment 11 Regina Henschel 2021-12-06 15:17:29 UTC 
Import and Export as extension works again. Export as Library works. But importing the library is still broken.

Tested with Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 4ac9032163cf55c160145373e7c41741c9c339ca
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: CL