Opened 2 weeks ago

Closed 2 weeks ago

Last modified 2 weeks ago

#456 closed bug (invalid)

Formatting text issue in LayGroup

Reported by: Samir Hawamdeh Owned by:
Priority: normal Milestone: 5.0-2020R2
Component: LayGroup.mcc Version: 5.0-nightly build
Severity: minor Keywords:
Cc: OS Platform: All
Blocked By: Blocking:
Release Notes:



Found a text related issue in the newer LayGroup
I noted this after translated the example text into the Complex 2 tab
In case an extra space will be added into the translated text of the example area, the whole text will completely mess up

The only solution to make the text in a correct order will be to just eliminate the space, however why this is a quick solution, in reality user may have the necessiry to add a manual break line

In the grab attached you can see what happen to the text when we add a "manual" line break into the translation (using Transifex)

Attachments (1)

laygroup.png (134.0 KB) - added by Samir Hawamdeh 2 weeks ago.

Download all attachments as: .zip

Change History (3)

Changed 2 weeks ago by Samir Hawamdeh

Attachment: laygroup.png added

comment:1 Changed 2 weeks ago by Thore Böckelmann

Component: undefinedLayGroup.mcc
Milestone: future release5.0-2020R2
Priority: undecidednormal
Resolution: invalid
Status: newclosed

This is not bug of LayGroup class, but a bug of the translation.

First of all, the tabs of LayGroup prefs class are meant as examples, nothing else. They just demonstrate how your user settings affect the object layout.

The "Complex 2" tab even lets you enter your own string to be parsed and converted to one object per word. You cannot enter linefeeds here, just words separated by spaces. This is all the parser needs and can handle.

The parsing rules are the same for your own text and for the standard text from the locale catalog: one single long line, no linefeeds

In the beginning I did correct the italian translation myself and removed the LFs again, but since you insisted on adding them again I finally chose to let you do your work and let you make your own experiences with the broken layout ;)

There simply is no necessity to add line breaks. It is an example.

comment:2 Changed 2 weeks ago by Thore Böckelmann

In 6689:

  • locale/MUI.pot: added a note about how the LayGroup example text has to be formatted to show up correctly. This refs #456.
Note: See TracTickets for help on using tickets.