Opened 14 years ago
Closed 12 years ago
#16515 closed defect (bug) (duplicate)
Field names of QuickEdit and QuickPress don't fit in some languages
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.4 |
Component: | I18N | Keywords: | has-patch |
Focuses: | Cc: |
Description
Default strings are used in QuickPress and QuickEdit, but there is enough space only for english words. In some languages we use much longer meanings which don't fit in their area (view picture).
We can use custom css to make that area larger, but it would be easier to use different translations so translator could choose other meanings ir just translate the word in a shorter form.
I've tried to create a diff for quickpress. The same could be done with quickedit.
Attachments (3)
Change History (11)
#2
@
13 years ago
- Milestone changed from Awaiting Review to 3.4
- Owner set to nacin
- Status changed from new to accepted
#4
@
13 years ago
- Owner changed from nacin to SergeyBiryukov
- Status changed from accepted to assigned
Good points, Sergey. Can you run with this?
#5
@
13 years ago
What do you think about moving these words inside the box, the same way we have "Enter title post" in class-wp-editor.php (if it is possible)?
#6
@
13 years ago
- Cc kaipgis@… added
- Summary changed from Translate QuickPress strings using _ex instead of _e to Field names of QuickEdit and QuickPress don't fit in some languages
- Type changed from enhancement to defect (bug)
- Version changed from 3.1 to trunk
What do you think about making QuickEdit and QuickPress fields wider? It would fix long lithuanian words problem. Also you could remove some russian CSS from the core (same problem).
Otherwise I need some lithuanian CSS in the core.
See http://core.trac.wordpress.org/ticket/19603#comment:35
We should also try to adjust CSS to allow longer words here, in case a shorter one is unavailable or would make less sense.
For ru_RU, this was a problem from 2.7 to 3.1. In 3.2, the font was switched to a more narrow one, and I could get rid of custom CSS adjustments. However, I had to restore them due to CSS merge in 3.3, because the elements were shifted a bit.