Closed (won't fix)
Project:
Category
Version:
master
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Oct 2006 at 20:52 UTC
Updated:
10 Jul 2010 at 00:52 UTC
Jump to comment: Most recent file
Comments
Comment #1
marcoBauli commentedJoshua, i think you can use the local.module to translate almost any string into what you need if it properly uses t().
You might want to look at http://drupal.org/node/24593
Comment #2
JoshLangner commentedThere are several reasons that using a module, especially this one, will not work:
1. First and formost, changing "post" to "item" to make it more generic is logical. Generalization is the very essence of the Drupal CMS.
2. It's a small change.
3. I said "please."
4. local.module creates a serious performance hit.
5. I don't need local.module.
Comment #3
JonathanDStopchick commentedI know you should really have something extra to contribute, but I have to say this.
Best reason ever...
Comment #4
bdragon commented+1 on this change, even though it is so minor.
Patch attached against DRUPAL-4-7. Please review and change issue status to RTBC if found correct.
Comment #5
Jaza commentedThe wording of this message has been copied directly from the
taxonomy_render_nodes()function in the core taxonomy module:The category module tries to be consistent with the core taxonomy module (and the book module) wherever possible. I see no reason why this message should be worded differently in the category module to the way it's worded in core. I also, personally, don't see what's wrong with the word "posts": this is the standard word used throughout Drupal, to describe "nodes" in text that is displayed to end-users.
Please file an issue against Drupal core to have the wording changed. The category module will only have this change committed AFTER an equivalent change has been committed to core.
PS: Also removed unnecessary wording from the title of this issue.
Comment #6
bdragon commented