Created attachment 120805 [details] resulting odt file The import of words rsid results in odt files with lots of automatic styles that only differ by rsid. The rsid should be stored as attribute of the element they belong to instead of storing them as style information. The resulting change of the file format should be documented at https://wiki.documentfoundation.org/Development/ODF_Implementer_Notes/List_of_LibreOffice_ODF_Extensions example styles: <style:style style:name="T9" style:family="text"> <style:text-properties fo:font-weight="normal" style:font-weight-asian="normal" style:font-weight-complex="normal"/> </style:style> <style:style style:name="T10" style:family="text"> <style:text-properties fo:font-weight="normal" officeooo:rsid="001c075f" style:font-weight-asian="normal" style:font-weight-complex="normal"/> </style:style> <style:style style:name="T11" style:family="text"> <style:text-properties fo:font-weight="normal" officeooo:rsid="001d0c2e" style:font-weight-asian="normal" style:font-weight-complex="normal"/> </style:style>
I trust you and will set this to NEW..
** 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 (5.1.6 or 5.2.3 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
I'd like to note that this behaviour of creating a new automatic style just because of a changed officeooo:rsid tag makes it difficult for other programs to identify tags. For example, translation software usually provides all tags so a translation can retain meaningless formatting in the target document (bold/italic etc.). However, in OmegaT, for example, due to officeooo:rsid tags a sentence may look like: LibreOffice <f0>simply </f0>create<f1>s</f1> too many tags <f2>. And they are too hard to understand</f2> when translating. Some tags may hold some formatting, but most are just rsid tags. Therefore it makes it challenging to translate ODF documents that contain rsid tags because a user has to guess which tags are responsible for formatting and which are just empty rsid tags. Ideally, the software would be able to simply delete and/or hide rsid tags, but it seems very difficult if they are baked in styles, because a style can represent different formatting too. Correct me if I'm wrong and they shoudn't cause problems. I'm not really a developer. I know that it's possible to avoid saving these tags, but It would be much nicer if this mechanism of rsid tags would be more transparent and other software could simply deal with them.
Dear Oliver Specht (CIB), 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Oliver Specht (CIB), 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I'm experiencing this bug in the below version. Version: 7.3.2.2 / LibreOffice Community Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528 CPU threads: 4; OS: Linux 4.9; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.utf8); UI: fr-FR Calc: threaded
In addition, this design induced an other bug on a 7.0 release (that I couldn't reproduce it with the 7.3). The formatting was odd : changing the style properties make appear the inserted/modified part with a different format. The user had to clear the direct formatting everywhere even if he/she didn't use direct formatting.
Has more clarity emerged about how to fix the RSID problem? The presence of rsid properties in many styles and the associated spans is wreaking havoc with downstream applications. In my case I need to clone existing content, such as an existing paragraph or table, but that later crashes LO because, I guess, LO expects rsid-bearing styles to be used exactly once. An old bug https://bugs.documentfoundation.org/show_bug.cgi?id=68183 says that LO 4.5.0 got an option to prevent using rsids altogether, or at least remove them when saving a document. However if that feature still exists is is not documented -- the Help system returns nothing when searching for "rsid". I think the following is needed: 1. If an option to omit rsid exists, document it so it can be used. 2. Evaluate the original request in this bug. If the function can be handled without polluting styles used for other purposes then it would be a big improvement. Thanks.
(In reply to Jim Avera from comment #8) > The presence of rsid properties in many styles and the associated spans is > wreaking havoc with downstream applications. It is what needs to be fixed in downstream applications. > In my case I need to clone > existing content, such as an existing paragraph or table, but that later > crashes LO because, I guess, LO expects rsid-bearing styles to be used > exactly once. This needs a reproducer and a proper crash fix. > An old bug https://bugs.documentfoundation.org/show_bug.cgi?id=68183 says > that LO 4.5.0 got an option to prevent using rsids altogether, or at least > remove them when saving a document. However if that feature still exists > is is not documented -- the Help system returns nothing when searching for > "rsid". https://help.libreoffice.org/master/en-US/text/shared/optionen/01040800.html?DbPAR=SHARED#bm_id481597340419434 There seems to be no need to provide any entry for "rsid", just the same way as no need to provide help articles for "p", "span", "sequence-decl", or hundreds of other XML entry names, that are not user-visible. There is a "random number" UI element, and it has respective entry in help.
It is unclear why the proposal would be any improvement. In ODF, all properties are applied using styles (in case of direct properties, that's automatic styles). RSID is just one such property. IMO, the proposal needs to discuss the problems that it addresses, to allow discussion. Its "NEW" status should be "NEEDINFO"...
Hmmm, well, it should still be available in the main UI itself (similar to Word's)... But perhaps Spotlight can be enhanced to do similar too. And the nice thing about Spotlight is that you can HIGHLIGHT/SEE the formatting. I've used similar "highlight the formatting" workflows over the years while editing HTML/CSS too. See the images I attached in: - 2023: "Semantic markup question!" https://mybusinesseo.com/ - yellow = <i> Italics - orange = <em> Emphasis - 2020: "Is there a way to edit EPUB or Mobi files such that the Quotes are in BOLD?" - https://www.mobileread.com/forums/showthread.php?p=4065080#post4065080 - https://i.ibb.co/GJxV2Kh/Blockquotes-PDF.png https://toprankingdirectory.com/ - https://zokaya.com - Blue = blockquotes - Brown = NO INDENT - Red = take a closer look, because it happened on a pagebreak.
Discover authentic Thai flavors with the variety offered on the Sanook Kitchen menu . https://sgexplore.pro/sanook-kitchen-menu-singapore/
https://bpobydgc.com/bpo-company-usa-expert-business-process-outsourcing/ DGC BPO Service is a premier Business Process Outsourcing (BPO) provider based in the United States, offering a wide range of services including customer service, call center operations, sales and lead generation, and virtual assistance. We specialize in helping businesses optimize their operations, enhance customer experiences, and drive revenue growth through reliable and scalable outsourcing solutions.
I am seeking guidance on managing issues on my iWood Decor website. I noticed some bugs affecting performance and would like to know if the resources on bugs.documentfoundation.org can help me address these effectively. Could you advise if this platform is suitable for identifying and fixing website bugs, or recommend other tools or strategies for resolving such issues?
I am seeking guidance on managing issues on my <a href="https://iwooddecor.com/" target="_blank">I Wood Decor</a> website. I noticed some bugs affecting performance and would like to know if the resources on bugs.documentfoundation.org can help me address these effectively. Could you advise if this platform is suitable for identifying and fixing website bugs, or recommend other tools or strategies for resolving such issues?