Opened 18 years ago
Closed 18 years ago
#3233 closed defect (bug) (fixed)
'Editor' tab title needs clarifier for translation
Reported by: | foolswisdom | Owned by: | foolswisdom |
---|---|---|---|
Milestone: | 2.1 | Priority: | normal |
Severity: | normal | Version: | 2.1 |
Component: | Administration | Keywords: | |
Focuses: | Cc: |
Description
Stefano wrote to wp-testers Oct 12, 2006 3:12 AM
Subject: [wp-testers] i18n issue
The RTE tab is named Editor, but this string is used for a role too, so the translation for both is unique, in Italian but i suppose in other languages the role is translated in a different way than the RTE's name.
Attachments (2)
Change History (10)
#3
@
18 years ago
Ryan Boren says on wp-hackers:
Maybe use a custom tag that is stripped by () and _e(). Translators can leave the tag in the translated text or omit it.
_e('Editor<wp:i18n_context>Tab</wp:i18n_context>');
#4
@
18 years ago
- Keywords has-patch removed
Oops, did not mean to add has-patch until after I tested. I should not have attached it I guess, or put in a comment right away.
HTML comment solution does not work, shows up on label. Guess input value can't include comments. Maybe can be escaped, but Ryan's solution seems more elegant and generalizes.
#5
@
18 years ago
I know we had a reason for choosing "editor" but given its existing context within WordPress as a publishing system perhaps we should reconsider that choice?
Personally I would be fine with Visual / Code or Visual / HTML.
I'm not a fan of adding another layer of compexity to our translation system.
#6
@
18 years ago
In light of everything, "Visual" seems like a win/win/win. I am indifferent whether the other is "Code" or "HTML".
Include HTML comment as proposed by MarkJaquith