Description: Writer should can import autotext items from not only MS Word files but from ODT/OTT files too Steps to Reproduce: 1. Open Writer 2. Select Tools -> Autotext 3. In the dialog press drop-down list Autotext and select Import there 4. Look at file format available in the Open file dialog -> there are only MS Word formats there! Actual Results: I can't import autotext items from ODT/OTT document Expected Results: I can import autotext items from ODT/OTT document Reproducible: Always User Profile Reset: No Additional Info: Latest master LO 26.2
We store AT in special *.bau files similar to extensions. There is no such thing as 'import from a document' (and all ATs are of course not stored in a single document). MSO has "quick parts" including AT but way less flexible without any shortcuts. The ATs are stored in my case at C:\Users\heiko\AppData\Roaming\Microsoft\Templates\Normal.dotm. This file is not accessible (doubt anyone uses a MSO version < 2007). So my take is to remove the function.
> So my take is to remove the function. It's not something I use myself, but we inherited a "import autotext from DOC" function from OOo and a while ago Szymon was tasked to create the DOCX equivalent of that, see the code in sw/source/filter/docx/. People even have large collection of autotexts, I was asked to even optimize that import in commit 87670fa998a26ab059e40bbe8f5e0acf0ad6ea04 I agree it's strange to put a list of autotexts into documents, but if that's how MSO users distribute these autotext lists and we currently have a way to read that from DOC/DOCX, then it sounds a bit fast to just remove it. I agree that .bau files are good enough for ODF-based autotext sharing, so probably doing an ODT equivalent is not needed. Perhaps close this as won't fix, but don't remove the existing import functionality?
You need a desktop version of Word to create a custom autotext. Steps are: 1. Write the desired content in a new docx document and select the text. 2. Press Alt+F3. You get the "Create New Building Block" dialog. 3. Field Name: Enter the name, that you will use later when inserting the auto text. 4. Gallery: The default entry "AutoText" is OK. 5. Category: Open the drop-down. There you can use the entry "Create New Category...". A new category makes it easier to distinguish your autotext from the build-in ones, when you are using the autotext in Word. 6. Description: Add a short description 7. Save in: Select the item "Building Blocks.dotx" 8. Options: If you have a large autotext with several paragraphs and maybe headings, then select item "Insert content in its own paragraph". 9. OK. 10. Close the document (not Word!) with or without saving. 11. Now close Word itself. You get a message box about saving to "Building Blocks.dotx". Click on Save. The file "Building Blocks.dotx" is located in C:\Users\<your user name>\AppData\Roaming\Microsoft\Document Building Blocks. This folder has subfolder named 1031, 1033, 1041, for example. In my case I have to open subfolder 1033\16\. If you use the search feature of Windows, make sure the search includes hidden folders and subfolders. Now the import in LibreOffice. 12. Start with a text document. 13. Menu Tools > AutoText. 14. Select the Category into which you want to import the autotext from Word. Make sure it is writable. In default settings it will be "My AutoText". 15. Open the drop-down "AutoText" in the lower part and select "Import...". You get the usual File-Open dialog. 16. Now go to the file "Builing Blocks.dotx". Its location was described above. Select it and click on Open. 17. The autotext items, that you have created in Word, should now be available with their names you had given them in Word. That's all. It works without problems for me. I use Windows 11, Word 365 and an own debug build from current master. So there is no need to remove this feature. When you inspect the file "Building Blocks.dotx", you will find the autotext in \word\glossary @Roman: The autotexts from LibreOffice are stored in *.bau files and those are not imported via "Import" but by using the "Path" item in the AutoText dialog. In regard of extending an ott-file to be able to carry AutoText entries, this is a WontFix for me, because the current solution with *.bau files works fine. You can use several *bau files at the same time and they need not be located in the user profile. A company can provide AutoText entries located on a central server, for example.
(In reply to Miklos Vajna from comment #2) > Perhaps close this as won't fix (In reply to Regina Henschel from comment #3) > this is a WontFix for me Thanks for your comments.
Ok, then that item Import should be renamed to "Import from MSO files"
(In reply to Roman Kuznetsov from comment #5) > Ok, then that item Import should be renamed to "Import from MSO files" A somewhat lengthy text, don't you think? And not so helpful since you will find out in the filter one click later.
(In reply to Heiko Tietze from comment #6) > (In reply to Roman Kuznetsov from comment #5) > > Ok, then that item Import should be renamed to "Import from MSO files" > A somewhat lengthy text, don't you think? And not so helpful since you will > find out in the filter one click later. But then users will not have question about that import as I had when created this report
(In reply to Roman Kuznetsov from comment #7) > But then users will not have question about that import as I had when > created this report You could read the documentation.