Created attachment 179218 [details] .bau file with two AutoText fragments, created in 7.3.0.0_alpha 1. I'll attach a bau-file, created in LO 7.3.0.0 alpha something. 2. Adding that .bau to the user configuration of LO 6.4.5.2 or LO 6.2.8.2 makes the AutoText category and the AtoText names visible in the dialog AutoText (Ctrl+F3), but there is no content shown. (config/lo/4/user/autotext/) 3. Adding that .bau to the user configuration of LO 7.0.0.3, gives the expected result. Conclusion: AutoText from LO > 7.3 is incompatible with older versions.
NB: it may be that the incompatibility started with AutoText created in 7.0.x. I did not check that.
I'm not familiar with AutoText, so I couldn't reproduce it without more detailed steps, but i would like to ask, why somebody should create AutoText in LO 7 and use it in LO 6? So where is the use case for the described problem in real life?
Hi Dieter, (In reply to Dieter from comment #2) > I'm not familiar with AutoText, so I couldn't reproduce it without more > detailed steps, - Text document with some content - select - Ctrl+F3 or Tools>AutoText (dialog AutoText) - Chose category to create a category - it will be stored in your user profile under /user/autotext/ - Choose Autotext > New to create an AutoText, select your category and give a name - Close LO - Copy the <myCategory>/bau to the user profile of an older LO version.... > ... but i would like to ask, why somebody should create AutoText > in LO 7 and use it in LO 6? So where is the use case for the described > problem in real life? Not something you expect indeed. Unless you have a .bau that you share with someone else who turns out to have that older version :) HTH & thanks for looking at this, Cor
Cor, thank you for explanation. I confirm it with Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 83d0f2eebae41d431d9a5bfd1a918523977752d0 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Auto-Text created in LO 7.4 has no content in LO 6.1
Dear Cor Nouws, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug