Description: LO 26.2.0 Beta 1 Spanish --> Insert menu --> Field --> Strings without translation. I am testing LO 26.2.0 Beta 1 in Spanish because that is my native language in Colombia. I found some strings in English, not translated into Spanish, under the Insert menu (“Insertar” in Spanish), specifically in the Field submenu (“Campo” in Spanish), as we can see in the screenshot I have attached to this report. These errors had been fixed very appropriately in LO 25.8.4 (Spanish Version) and for some reason, which I do not understand, in LO 26.2 Beta 1, Weblate ignored and removed those correct translations that were the most efficient for us LO users in Spanish. I really do not understand why they did that in LO 26.2. (Spanish Version). Steps to Reproduce: 1. Open LO Writer 26.2.0 Beta 1 in Spanish. 2. Click on the Insert menu (“Insertar” in Spanish). 3. Click on the Field option (“Campo” in Spanish). 4. On the right-hand side, look for the English strings indicated in the screenshots I have attached to this report. Actual Results: The following strings are in English without Spanish translation: Page Count In Range Date (Variable) Time (Variable) Weblate is ignoring the translations that were correct for LO 25.8.4 in Spanish, which appear to have been inexplicably removed Expected Results: Weblate should restore the translations (of the aforementioned strings) that had been fixed in the Spanish version of LO 25.8.4 in LO 26.2.X (Spanish version) 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: yes
Created attachment 204780 [details] LO Writer 26.2.0 Beta1 Spanish - Translations inexplicably removed – Path: “Insertar” --> “Campo”
Created attachment 204781 [details] Screenshot 02
Created attachment 204782 [details] Solución - Solution
Sometimes string translations get reset due to the conflict-solving process used to merge changes to the Git repository; I believe that was the case this time.
Thank You, Adolfo, for managing the solution for this issue.