Steps to reproduce: Add a comment, set its text to be RTL. Save. Open it again and it's back to LTR. A a side note, if you open the said file in Microsoft Word, the whole text is set to LTR (not just the word order) and is unreadable until fixed. Which has to be done one by one. This doesn't happen if you save your file as ODT.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 168649 [details] Added a sample document I provided a sample document. You can see that the comment is still shown LTR despite me setting it to RTL before saving. (You can try to change it back to RTL, but the direction won't be saved)
[Automated Action] NeedInfo-To-Unconfirmed
repro in Version: 7.1.5.2 (x64) / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (ru_RU); UI: en-US Calc: threaded
repro in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (ru_RU); UI: en-US Calc: threaded
Repro in 7.0, but not anymore. Arch Linux 64-bit Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c8b607b7c0096c58dc5187262bf0133dee728d50 CPU threads: 8; OS: Linux 6.11; UI render: default; VCL: kf6 (cairo+wayland) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: CL threaded Built on 19 November 2024
Fixed in LO 7.5 with commit a73daa562c82a5c058a217ba80035da08d40451d Author: Justin Luth on Mon Jul 11 15:27:54 2022 -0400 tdf#114734 docx export: save comment paragraph properties *** This bug has been marked as a duplicate of bug 114734 ***