The strings 'All Styles', 'Hidden Styles', 'Applied Styles', 'Custom Styles' are used in all the style types in the styles sidebar deck, but they dont share the same string. The 'Hierarchial' string[1] is being shared. The strings are in this file https://opengrok.libreoffice.org/xref/core/sw/inc/app.hrc [1] https://opengrok.libreoffice.org/xref/core/include/sfx2/strings.hrc#217
Let's put 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 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 Yousuf Philips (jay) (retired), 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
Ilmari: Perhaps I missed something but I don't see any duplicates now. git grep -in style include/sfx2/strings.hrc include/sfx2/strings.hrc:58:#define STR_QRYTEMPL_MESSAGE NC_("STR_QRYTEMPL_MESSAGE", "The template '$(ARG1)' on which this document is based, has been modified. Do you want to update the styles of the current document, using the modified template?") include/sfx2/strings.hrc:59:#define STR_QRYTEMPL_UPDATE_BTN NC_("STR_QRYTEMPL_UPDATE_BTN", "~Update Styles") include/sfx2/strings.hrc:60:#define STR_QRYTEMPL_KEEP_BTN NC_("STR_QRYTEMPL_KEEP_BTN", "~Keep Old Styles") include/sfx2/strings.hrc:222:#define STR_QUERY_OVERWRITE NC_("STR_QUERY_OVERWRITE", "Style already exists. Overwrite?") include/sfx2/strings.hrc:226:#define STR_TABPAGE_INVALIDSTYLE NC_("STR_TABPAGE_INVALIDSTYLE", "This Style does not exist.") include/sfx2/strings.hrc:227:#define STR_TABPAGE_INVALIDPARENT NC_("STR_TABPAGE_INVALIDPARENT", "This Style cannot be used as a base Style,\nbecause it would result in a recursive reference.") include/sfx2/strings.hrc:228:#define STR_POOL_STYLE_NAME NC_("STR_POOL_STYLE_NAME", "Name already exists as a default Style.\nPlease choose another name.") include/sfx2/strings.hrc:229:#define STR_DELETE_STYLE_USED NC_("STR_DELETE_STYLE_USED", "One or more of the selected styles is in use in this document.\nIf you will delete it, text or objects using these styles will revert to the parent style.\nDo you still wish to delete these styles?\n") include/sfx2/strings.hrc:230:#define STR_DELETE_STYLE NC_("STR_DELETE_STYLE", "Styles in use: ") include/sfx2/strings.hrc:239:#define STR_STYLE_FILTER_HIERARCHICAL NC_("STR_STYLE_FILTER_HIERARCHICAL", "Hierarchical") include/sfx2/strings.hrc:338:#define STR_STYLEUSEDBY NC_("STR_STYLEUSEDBY", "(used by: %STYLELIST)") so no "Hidden Styles', 'Applied Styles', ... About Hierarchial, I did a git grep on sw: git grep -in HIERARCHICAL IwyuFilter_sw.yaml:636: - com/sun/star/container/XHierarchicalNameAccess.hpp README.md:154: hierarchical tree of numbered nodes. inc/SwNumberTree.hxx:502: Validates a child using hierarchical numbering. inc/SwNumberTree.hxx:508: void ValidateHierarchical(const SwNumberTreeNode* pNode) const; source/core/SwNumberTree/SwNumberTree.cxx:126:void SwNumberTreeNode::ValidateHierarchical(const SwNumberTreeNode * pNode) const source/core/SwNumberTree/SwNumberTree.cxx:293: ValidateHierarchical(pNode); source/filter/xml/XMLRedlineImportHelper.cxx:208: // next redline info (for hierarchical redlines) source/filter/xml/XMLRedlineImportHelper.cxx:420: // 3b) we already have a redline with this name: hierarchical redlines source/filter/xml/XMLRedlineImportHelper.cxx:723: // ( check presence and sanity of hierarchical redline info ) source/filter/xml/swxml.cxx:728: pMedDescrMedium->GetItemSet()->GetItem(SID_DOC_HIERARCHICALNAME); source/filter/xml/wrtxml.cxx:88: OUString aDocHierarchicalName; source/filter/xml/wrtxml.cxx:98: pMediumItemSet->GetItem(SID_DOC_HIERARCHICALNAME); source/filter/xml/wrtxml.cxx:100: aDocHierarchicalName = pDocHierarchItem->GetValue(); source/filter/xml/wrtxml.cxx:235: const OUString aName( !aDocHierarchicalName.isEmpty() source/filter/xml/wrtxml.cxx:236: ? aDocHierarchicalName source/uibase/docvw/srcedtw.cxx:27:#include <com/sun/star/container/XHierarchicalNameAccess.hpp> so no duplication too. Should we put this one to WFM?
I believe you and will close