Japanese string "Custom Profile" is broken into two lines in "Tag Nodes into Profiles" dialog
Bug #1673510 reported by
Yuko Katabami
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Japanese translation for the string "Custom Profile" is broken into two line, with only the last character is in the second line, which does not look good.
Would it be possible to extend the width of this column, so that entire text fits in a single line?
Revision history for this message
| Yuko Katabami (ykatabam) wrote | #1 |
| tags: | added: i18n ui |
| Changed in tripleo: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → pike-1 |
| Changed in tripleo: | |
| assignee: | nobody → Jason E. Rist (jason-rist) |
| tags: | added: ocata-backport-potential |
| Changed in tripleo: | |
| milestone: | pike-1 → pike-2 |
| Changed in tripleo: | |
| milestone: | pike-2 → pike-3 |
Revision history for this message
| Emilien Macchi (emilienm) wrote | #2 |
| Changed in tripleo: | |
| assignee: | Jason E. Rist (jason-rist) → nobody |
| Changed in tripleo: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in tripleo: | |
| milestone: | pike-rc1 → queens-1 |
| Changed in tripleo: | |
| milestone: | queens-1 → queens-2 |
| Changed in tripleo: | |
| milestone: | queens-2 → queens-3 |
| Changed in tripleo: | |
| milestone: | queens-3 → queens-rc1 |
| Changed in tripleo: | |
| milestone: | queens-rc1 → rocky-1 |
| Changed in tripleo: | |
| milestone: | rocky-1 → rocky-2 |
| Changed in tripleo: | |
| milestone: | rocky-2 → rocky-3 |
| Changed in tripleo: | |
| milestone: | rocky-3 → rocky-rc1 |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| milestone: | stein-1 → stein-2 |
Revision history for this message
| Emilien Macchi (emilienm) wrote Cleanup EOL bug report | #4 |
| Changed in tripleo: | |
| importance: | Medium → Undecided |
| status: | Triaged → Expired |
To post a comment you must log in.
There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.