If English "version" of LO is opened, there is now problem doing File - Send - Create Master Document, file saves as should. But, when LO is set to Croatian UI it is not possible to do that. Error is displayed: The document can't be saved (in Croatian, not English as I put it here since we have translation to 100%.)
Problem exists only if you have new (unsaved) document opend.
Hello Krunoslav, *, I can confirm it with LO Version: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 and installed Germanophone lang- as well as helppack under Debian Testing AMD64 ... :( When I use the Germanophone UI, create a Writer document with only "Test" in it, and send this via "File - Send - Create Master Document", I get the message "Das Dokument konnte nicht erzeugt werden." (roughly translated: The document could not be created.") ... :( HTH Thomas.
I can't reproduce with FR UI, all is ok. My version Version: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 Sophie
I have the same error with English UI too.
(In reply to comment #4) > I have the same error with English UI too. Can you paste your system/ version/ Build ID please? Sophie
2cce78137bbf9810421b9fdedd45127b019b1188 Win 7 x64
There is a problem with exporting odt to doc. Steps: Insert frame, anchor it to paragraph text area, align it most right, then insert text to frame (e.g. [02:05]) and apply a custom style with text aligned right - when odt is exported as doc every thing is just fine but right bracket of "[02:05]" is not showing. Export cause lose of "]" character.
Sory - wonted to report new bug, not comment on this :(
Hi Krunoslav, Thomas, Urmas: could one of you provide example document or detailed steps to reproduce, starting from fresh user profile? When you do, please change status of this report back to NEW. Until then, let's leave it as NEEDINFO. Sophie could not reproduce this issue, I have failed either. Since we don't have consensus here, I think it's better to remove NEW status from report. I have noticed that File -> Send -> Create new master doc will fail if opened file does not have Heading 1 style definition. You can create that definition by either: a) applying Heading 1 style to any paragraph b) changing Heading 1 properties (change interline or whatever) Be aware, that style definition might be inherited from template used to create document. So, this will result in error message: 1. Open LO with new, never used before, profile directory (use -env:UserInstallation=file:// command line switch) 2. Create new Writer document 3. File -> Send -> Create new master doc 4. After specifying filename, LO will show error It doesn't matter whether you save document or not before step 3. Apparently, language and locale settings don't matter either. But if you apply Heading 1 to any paragraph, or change heading 1 properties, before step 3, then LO will successfully create new master document. I think that you might have run into issue mentioned above and mistakenly thought that UI language plays a role here. Which would be understandable, as many master document quirks are not documented.
Reproducible for me with Version 4.2.0.0.beta1 Build ID: f4ca7b35f580827ad2c69ea6d29f7c9b48ebbac7 with a clean new user profile. UI in French -> KO UI in English -> OK Steps to reproduce: 1/ open a new text document with the UI in French 2/ type TEX+F3 (autotext) 3/ Menu Fichier > Envoyer > Créer un document maître 4/ type the name of the new file ==> Error message: Impossible de créer le document UI in English: 2/ type DT+F3 (autotext Dummy Text) 3/ Menu File > Send > Create a Master Document 4/ Type the name of the new file ==> The file is created Set status back to NEW Best regards. JBF
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Still reproducible with LibreOffice 4.4.4.0.0+ built at home under Ubuntu 14.10 x86-64 and French UI. Best regards. JBF
Still present :D Inačica: 5.1.2.2 ID Inačice: d3bf12ecb743fc0d20e0be0c58ca359301eb705f CPU niti: 2; OS inačica: Linux 3.16; Ui crtač: zadano; Jezik: hr-HR (en_US.UTF-8) Linux jessie 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) i686 GNU/Linux
Present in 5.3 alpha (and translating user interface is a hard work).
Changing version back to the earliest affected version.
*** This bug has been marked as a duplicate of bug 113876 ***