I went to localize.drupal.org today to see if I could contribute to the Spanish translation of Drupal 7. It has the Drupal 7.x-alpha1 version loaded currently.
There were LOTS of strings to be translated that had the word "node" in them, although according to http://drupal.org/node/604342 we are not supposed to be using the word "node" any more in the user interface. It ran to 3 pages, at 30 per page, so somewhere between 60 and 90 strings containing the word "node".
Some of them are from tokens, so we probably won't fix those (see #678012: Tokens should not use the word "node" in human-readable descriptions for what we did for node.tokens.inc - may need to do something similar for comment.tokens.inc?).
The rest probably need to be fixed. For reference, I exported the POT files for Drupal 7 -- it comes as a TGZ archive with each module in a separate POT file, unfortunately. (Technically, they are PO files for Spanish, but without the Spanish translations in there.)
Comment | File | Size | Author |
---|---|---|---|
#14 | 690622-reroll.patch | 6.7 KB | jhodgdon |
#7 | 690622-update.patch | 6.71 KB | jhodgdon |
#1 | 690622.patch | 6.68 KB | jhodgdon |
drupal-7.0-alpha1-es-templates.tgz | 124.17 KB | jhodgdon |
Comments
Comment #1
jhodgdonI went through these... Aside from tokens, which I'm leaving as-is mostly (see above), I found about 6 places that needed fixing.
Here's a patch.
Comment #2
moshe weitzman CreditAttribution: moshe weitzman commentedi could be wrong, but 'content item' is not a standard phrase in drupal. you could use 'post' in some cases, and 'content type' in the field api case.
Comment #3
yoroy CreditAttribution: yoroy commentedThe same http://drupal.org/node/604342 suggest to use 'piece of content' for node and that's what we're doing elsewhere in the ui. (Don't use 'post' as a noun)
Comment #4
jhodgdonMoshe: I didn't write the guidelines. Nor do I agree with them, necessarily... but we aren't using either node or post as a noun to describe a node, except in coder-facing documentation. And in the case of tokens, because pretty much none of them make a bit of sense without the word node. We are using content item now.
I personally think it makes a lot of the writing in Drupal UI and help text VERY awkward, but as I said, this was not my decision.
Regarding the idea for the field API of using "content type", I was informed in no uncertain terms when redoing the help for the field API never ever to say that we attach fields to content types or vocabularies, because the fields are attached to the individual nodes/terms.
Comment #5
moshe weitzman CreditAttribution: moshe weitzman commentedyou got bad information i think. on these field ui pages, we are attaching fields to 'bundles' which are equivalent to content types when discussing nodes. we do not attach fields to individual nodes.
Comment #6
jhodgdonRight... Hmmm...
The Field module help currently says:
This is not good as it is.
If we use the word entities here, then technically the entities are taxonomy terms, user objects, nodes, and comments, right? I mean, the field definitions are attached to content types (for nodes and comments), vocabularies (for terms), and to the user account system (for user objects). The field instances are attached to the entities node, comment term, and user objects.
In the field UI help, which is definitely aimed at the non-technical user, and hence avoided the terms entities, attach, bundles, etc., we said (after much debate):
So I agree that the suggested change to field.module in the above patch is wrong. I'm just not sure how it should be rewritten so that it is correct.
Comment #7
jhodgdonOK, here's a proposal:
Here's a patch with the above change (and the other changes from the previous patch).
Comment #8
reglogge CreditAttribution: reglogge commentedShouldn't it say
in the part of the patch for path.module?
Sorry, but I can't reroll the patch right now due to technical issues with my pc.
Comment #9
jhodgdonActually, I thought it was better without "item". This is on the form alter for the node editing form, by the way, so I think the context is pretty clear.
Comment #10
cosmicdreams CreditAttribution: cosmicdreams commented+1 for excluding the word "item".
Comment #11
amc CreditAttribution: amc commented#7: 690622-update.patch queued for re-testing.
Comment #12
retester2010 CreditAttribution: retester2010 commented#7: 690622-update.patch queued for re-testing.
Comment #14
jhodgdonHere's a reroll that should hopefully apply.
Comment #15
jhodgdontagging
Comment #16
Bojhan CreditAttribution: Bojhan commentedSince we dont use "node" anymore, without this fix it will be confusing.
Comment #17
jhodgdonThanks Bojhan for reviewing.
Perhaps we should hit the test bot and make sure this doesn't break anything -- it's been a while since the last test of that issue?
Comment #18
jhodgdon#14: 690622-reroll.patch queued for re-testing.
Comment #19
webchickCommitted to HEAD. Thanks!
And thanks for working on string freeze patches. :)