Posted by aufumy on November 17, 2009 at 2:08am
4 followers
| Project: | Organic groups |
| Version: | 6.x-2.3 |
| Component: | og.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
| Issue tags: | localization |
Issue Summary
Allow node type names to be translated by adding a wrapper function for tt() that degrades gracefully if i18n module is not enabled.
other similar issues in different modules:
http://drupal.org/node/606862
http://drupal.org/node/606804
http://drupal.org/node/471546
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| og_tt.patch | 4.41 KB | Idle | FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch og_tt.patch. Unable to apply patch. See the log in the details link for more information. | View details | Re-test |
Comments
#1
Rerolled patch against today's 6.x-2.x-dev CVS. Added one more
og_tt()call.#2
Tagging.
#3
The last submitted patch, og-634680-1.patch, failed testing.
#4
Rerolled patch against the 6.x-2.x branch as of now.
#5
The last submitted patch, og-634680-4.patch, failed testing.
#6
Doh.
#7
Need someone else familiar with Internationalization practices to review the approach. Or some linkbait to examples of best practices for similar stuff.
#8
Rerolled patch against 6.x-2.3. Some links:
- #128228: Make case states translatable
- #1071470: Make privatemsg_filter tags translatable
- #606862: node type information to be translatable
- Making your custom data translatable
- #606804: Node type information to be translatable
- #635646: add i18n support to allow node type information to be translatable
- #637010: add tt wrapper to allow node type information to be translatable
- etc.