https://bugs.documentfoundation.org/show_bug.cgi?id=166802
--- Comment #3 from Alfred Novacek <[email protected]> --- First of all: I tried to build the latest version of LibreOffice using the instructions on https://wiki.documentfoundation.org/Development/GenericBuildingHints; however, make stops after a short time with a last line containing "Fehler 2" (error 2). >From previous lines, I conclude that the problem relates to meson.py (which is installed on my system and I used autogen.input to access it). I've taught myself some C at the time of MS-DOS (Windows predecessor OS), but that did not include make and similar concepts. Learning these is on my ToDo-list, but there are mayn other (presently more important items, too. So, I will not continue this approach, and I will work with the version of LibreOffice (still 24.8.6.2) that comes with my Linux distribution, which is OpenSuSe Leap 15.6 (the latest release of this distribution). I've managed to switch the language of the user interface to US English, so now I am using the original English terms rather than translating them back from German. Using slide names containing commas worked for me too, as long as I did not continue with the following steps: (1) In the "Slide Show" menu item, select the "Custom Slide Show ..." submenu item. (2) In the dialog ("Custom Slide Shows") appearing, click on the "New" button. (3) In the dialog ("Define Custom Slide Show") appearing, (3a) enter a name (I simply used "t") (3b) select slides on the left side and add them to the right side by pressing the ">>" button (I added "Hoja 1", "Hoja 2, de 3", and "Hoja 3, of 3", in that sequence). (3c) close the "Define Custom Slide Show" dialog by pressing the "OK" button. (4) In the "Custom Slide Shows" dialog, now "t" appears in the list on the left, and if You press the "Edit" button (reopening the "Define Custom Slide Show" dialog), the slides selected still are in the list on the right (as they should be); close the "Define Custom Slide Show" dialig again by pressing either the "Ok" or the "Cancel" button. (5) Now, press "Ok" to close the "Custom Slide Shows" dialog. (6) Save Your work. (7) Close the document. (8) Open the document again. (9) Now, if You open the "Custom Slide Shows" dialog again (by selecting the "Custom Slide Show ..." submenu item of the "Slide Show" menu), select slide show "t" in the list on the left and reopen the "Define Custom Slide Show" dialog by pressing the "Edit" button, in the right list the names of the slides containing commas (in my example, "Hoja 2, de 3" and "Hoja 3, of 3") are gone. These slides also are not shown when the custom slide show is invoked by pressing the "Start" button in the "Custom Slide Shows" dialog. After verifying that the problem is linked to slide names containig commas (by removing this character), I continued by extracting the "content.xml" component from the LibreOffice presentation document (a *.zip archive) saved in step (6) (now attached to this report). Near the end of the document, I found the following XML element: <presentation:show presentation:name="t" presentation:pages="Hoja 1,Hoja 2, de 3,Hoja 3, of 3"/> Thus, the presentation:pages of this element seems to be the list of slide names contained in the custom presentation, separated by commas; upon reopening the saved document, LibreOffice Impress seems to try to recreate the slide names in the custom presentation by splitting the value of this attribute on commas, giving following slide names: (1) Hoja 1 (2) Hoja 2 (3) de 3 (4) Hoja 3 (5) of 3 and, trying to access slides (2) to (5) and finding they don't exist, they are silently ignored (again, I did not dig into LibreOffice Impress's code to verify this). So, the problem seems to be linked to the file format LibreOffice Impress uses to save its document; as this is formally defined by an OASIS standard (which in the long term should be fixed by fixing the definition), anything should be done in the short term to prevent users from running in this problem by fixing the documentation (for those users who RTFM) and alerting the users whenever they take steps that make them run into this problem (for thos who don't, which I guess is the majority). Hope this update to the problem description helps. Sincerely Yours - Alfred Novacek -- You are receiving this mail because: You are the assignee for the bug.
