Description: When I am using LO Writer 7.3.4 in Spanish, trying to make adjustments in the Language Settings Options, and more specifically in the Writing Help, I have found some strings without Spanish translation, as we can see in the screenshot that I have attached to this report to show how and where these errors are reproduced. Steps to Reproduce: 1. Open LO Writer 7.3.4 in Spanish. 2. Click on the Tools Menu ("Herramientas" in Spanish) 3. Click on Options ("Opciones" in Spanish) 4. On the left side expand the Language Settings ("Configuración de Idiomas" in Spanish) branch and then select the Writing Aids option ("Ayudas de escritura" in Spanish). 5. On the right side, in the "Modulos de idioma disponibles" section, look for the string "Lightproof grammar checker (English)" ["Revisor gramatical Lighproof" in Spanish]. 6. In the "User dictionaries" ("Diccionarios de usuario" in Spanish section, look for the strings: "• Standard" and "Technical". Actual Results: The strings "Lightproof grammar checker", "Standard" and "Technical" have no translation into Spanish. Expected Results: Translate the strings mentioned above into Spanish, except the term "Lightproof" as it is a proper name assigned to a particular tool. Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: es Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no
Created attachment 181024 [details] Spanish translation is missing in some strings in the Language Configuration Options The screenshot that accompanies this report shows how and where the error is reproduced.
I suppose this should be WONTFIX: the "problematic" entries are just dictionary names as they are defined in the dictionaries themselves; and just with book titles, that are used in alpgabetical index untranslated, with original spelling, it would not be reasonable to expect that a dictionary author for Hunspell would also provide translations of the dictionary name to all available languages (or localization team would be able to translate all names of all dictionaries).
For the English string "Lightproof grammar checker (English)" I suggest the following Spanish translation: "Revisor gramatical Lighproof (English)". "Lightproof" would not translate because it is a proper name assigned to a particular tool. Luego, "Standard" is "Estándar" in Spanish, y, "Technical" is "Técnico" in Spanish.
(In reply to Mike Kaganski from comment #2) > I suppose this should be WONTFIX: the "problematic" entries are just > dictionary names as they are defined in the dictionaries themselves... I concur
I can’t find the string “Lightproof grammar checker” on Weblate; a bug? (the last two words in that string should be translated.)
I agree that "Lightproof" should not be translated because it refers to the proper name of a dictionary. However, I also completely agree with Adolfo's opinion when he indicates that the last two words of the string "Lightproof grammar checker" must be translated, that is "Grammar Checker" whose translation in Spanish is "Revisor gramatical". This is important for common Spanish LO users, those who don't know any English.
Cloph, any chance to get Lightproof into weblate?
Same thing for other languages, not just Spanish. I agree that it's not realistic to ask extension developers to provide translations in all the languages LibreOffice supports, but I guess it's different for the extensions LO bundles for all languages, and that are relevant to more than one language? As I understand it, a fix would involve: - making the strings translatable in the corresponding repository (and reuse them across the codebase if repeated). For example, for LightProof strings, it's in the dictionary repo: https://opengrok.libreoffice.org/search?project=dictionaries&full=%22lightproof+grammar+checker%22&defs=&refs=&path=&hist=&type=&xrd=&nn=1&si=full&si=full - adding the repository as a project on Weblate. Is that correct?
Dear Albert Acer, 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
(In reply to QA Administrators from comment #9) > Dear Albert Acer, > > 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 Currently (Nov-28-2025) I am working with the latest version of LibreOffice 25.8.3.2 in Spanish, and I can see that this error, which I reported on June 30, 2022, has not been resolved and remains as I reported it at that time.
Created attachment 204333 [details] Screenshot 28-11-2025
The error is still present in LibreOffice 25.8.3.2.