The German strings in the list of embedded databases in the first page of the Datase Wizard differ: English version: * HSQLDB Embedded * Firebird Embedded German version: * Firebord (eingebettet) * Eingebettete HSQLDB Differences: - Different wording ('embedded' as prefix and suffix) - Different sorting than in English version Another question: As the string before the drop down list already is named 'Embedded database', why is 'embedded' duplicated in the list entries? Version: 6.3.0.4 (x64) Build-ID: 057fc023c990d676a43019934386b85b21a9ee99 CPU-Threads: 12; BS: Windows 10.0; UI-Render: Standard; VCL: win; Version: 6.4.0.0.alpha0+ (x64) Build ID: 41cd3e8e817c8c33a13608e62eeb06ce2c6977e4 CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-01_22:04:10
Heiko/Xisco: before talking about translation, there's first an UI question.
Would do the same as Thomas and rename the second entry to "HSQLDB (eingebettet)". Alternatively both with "x (integriert)".
Thomas: about rationalizing and removing "Embedded" part since there's already "Embedded database", I think the labels must be used elsewhere. That's why I think we may just keep "embedded". About prefix or suffix, I've got no strong opinion. Heiko: thank you for your quick feedback! Lionel: since it concerns Base, even if it's just UI part, thought you might be interested in this one. (I was first only focused on UX team).
(In reply to Heiko Tietze from comment #2) > Would do the same as Thomas and rename the second entry to "HSQLDB > (eingebettet)". Alternatively both with "x (integriert)". +1 I also prefer this variant as it's better readable in lists with the database name in front. That's also easier for sorting. (The other variant is better readable in continuous text.) (In reply to Julien Nabet from comment #3) > Thomas: about rationalizing and removing "Embedded" part since there's > already "Embedded database", I think the labels must be used elsewhere. > That's why I think we may just keep "embedded". Sounds reasonable and the doubling no tragedy in point of UX in this case. Regarding different sorting: In 6.4 master it's the same in English and German. Seems to be changed between 6.3 and 6.4. So there is no issue with sorting anymore.
Fixed on Pootle: for 6.2UI https://translations.documentfoundation.org/de/translate/#search=HSQLDB%20(eingebettet)&sfields=source,target&unit=160004969&offset=0 for 6.3UI https://translations.documentfoundation.org/de/translate/#search=HSQLDB%20(eingebettet)&sfields=source,target&unit=45398818&offset=0
(In reply to Julien Nabet from comment #5) > Fixed on Pootle: > for 6.2UI > https://translations.documentfoundation.org/de/translate/ > #search=HSQLDB%20(eingebettet)&sfields=source,target&unit=160004969&offset=0 > > for 6.3UI > https://translations.documentfoundation.org/de/translate/ > #search=HSQLDB%20(eingebettet)&sfields=source,target&unit=45398818&offset=0 Can we close it as RESOLVED FIXED ?
Let's put this one to FIXED then but as always, I don't know when it'll be included in translation repo.