Created attachment 1390247 [details]
Description of problem:
I've noticed that one dialog in LO Base somehow showing content in different languages, so far I've seen Dutch, Czech and Welsh (according to google language recognizer).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Go through wizard (Click Next and Finish)
3.Save the database
4.Choose create table in design view
New window is opened but the last two words are in random language.
The window title should be in English since everything is in english.
Not sure what should be causing it I have installed all libreoffice packages including langpacks my lang is set to LANG=en_US.utf8 and I have the whole system in English.
I reinstalled mi libreoffice and I noticed that last lagpack installed was
libreoffice-langpack-nl-220.127.116.11-7.el7.x86_64, which is ditch if I am not mistaken.
After removing only the langpack the dialog window was again in different language.
caolanm->sbergman: affects upstream master too
framework/source/fwe/helper/titlehelper.cxx:541 gets the ooSetupFactoryUIName property for com.sun.star.sdb.TableDesign
my config from --with-lang=de has both
<prop oor:name="ooSetupFactoryUIName"><value xml:lang="en-US">Base: Table Design</value></prop>
<prop oor:name="ooSetupFactoryUIName"><value xml:lang="de">Base: Tabellenentwurf</value></prop>
but the one used is the German one, presumably because it appears after the en-US one. I imagine this specific config element is marked up wrong, does it need something like oor:localized="true" in Setup.xcs or ... ?
<https://cgit.freedesktop.org/libreoffice/core/commit/?id=8f44fb5ee0bd21d192820ffd359504f6d1c68a52> "Mark Base window titles for localisation" localized uses of ooSetupFactoryUIName in officecfg/registry/data/org/openoffice/Setup.xcu, but failed to mark the prop as oor:localized="true" in officecfg/registry/schema/org/openoffice/Setup.xcs
Fixed in libreoffice-18.104.22.168-8.el7.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.