Comment from Tuomas: There is very little space for this string in the UI; please make more space to accommodate translations longer than the original. location of the string: https://git.libreoffice.org/core/+/master/wizards/com/sun/star/wizards/common/strings.hrc#99
wizards/com/sun/star/wizards/letter/LetterWizardDialogResources.py shows: 77 self.reslblPostCodeCity_value = strings.RID_LETTERWIZARDDIALOG_START_45 wizards/com/sun/star/wizards/letter/LetterWizardDialog.py shows: 916 (8, self.resources.reslblPostCodeCity_value, 917 "lblPostCodeCity", 113, 97, 4, 79, 68)) Now it's not easy to find the right way for this since increase space somewhere means you diminish space somewhere else. The best thing would be a kind of dynamic interface so it adjusts itself automatically but since this wizard is in Python not in C++, I don't know if it's possible. Caolán: any idea of something equivalent to weld process but for Python interfaces?
no, there isn't, its limited to the exported uno api and there isn't any dynamic layout support so its old-school pre layout requiring endless tweaking
Caolán: thank you for your feedback. I expected this answer but just wanted to be sure. Heiko/Xisco: following Caolán's feedback, should we consider as a WONTFIX? I mean, we could try to tweak for ages, I suppose there would be lack of space at a moment in this kind of screens. IMHO all the Java and Python UI should be converted into C++ so welding process could be applied. Of course, it's quite a big task but some priorities could be put according to if the module is very used or not and the size of the module of course.
(In reply to Julien Nabet from comment #3) > IMHO all the Java and Python UI should be converted into C++... Would rather do the opposite and make it an user extension. For the layout it might be an improvement if the state goes into a separate line. Or all three underneath each other. Very US-focused layout anyway and probably meant to insert just the abbreviated state code.
At minimum, we should avoid Java since we're trying to get rid of it. Anyway, I'm afraid we got a similar pb as tdf#75218. It's very difficult (impossible?) to make a template which adapts to every locale. Indeed perhaps letter wizard should be removed from LO core and there would be several Letter user extensions, one per locale. Of course it would need people to maintain each one.
(In reply to Julien Nabet from comment #5) > Anyway, I'm afraid we got a similar pb as tdf#75218. Without looking into the details, you can omit attributes in templates. LBP does a lot around this, see bug 143956 and his patches on Gerrit.
Heiko: tdf#143956 is about only page size, but I don't know if all localisation issues can be dealt this way for example: - length name of ZIP may differ - addresses in general may be formatted differently (in US there are States, in Germany Landers, etc.) - some countries may use lastname first - etc. I'll stop here since I'm digressing from the original bugreport :-) Laurent: any thoughts here?
Actually, bug 143956 is about embedded templates, whereas this bug is about wizard. I never used letter wizard previously, but I noticed that template produced by this wizard is US localized (page size, date format, language at least). So there is place for improvement... However, I agree with Julien in comment 7: letter layout (place for addresses, date, salutations...) is local dependent. A wizard satisfying everybody is hard to complete. IMHO the best choice would be extensions maintained by l10n teams.
Thank you Laurent for your feedback. It seems to me it should be a WONTFIX unless we recycle this one as enhancement indicating: "Move Letter Wizard into localized extensions".
Here is the complete article about the working of the auto-darkening welding helmet. https://weldinghelmetreviews.com/how-does-an-auto-darkening-welding-helmet-work/