Closed (fixed)
Project:
Drupal core
Version:
5.x-dev
Component:
node system
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Oct 2006 at 13:29 UTC
Updated:
28 Nov 2006 at 19:08 UTC
Jump to comment: Most recent file
Comments
Comment #1
kkaefer commentedIt's actually a bug
Comment #2
kkaefer commentedChanged some strings as well to account recent changes (i.e. blocks are not longer restricted to sidebars).
Comment #3
kkaefer commentedUpdated.
Comment #4
webchickPatch that impacts the string freeze. Changing status to critical task. Will try and review tomorrow when I am more awake.
Comment #5
webchickComment #6
RobRoy commentedThe previous patch introduced some typos and funky wording. This improves those typos and improves the help text.
Comment #7
drummI think 'Further' can be left out.
<p>should go outside t() on the last part (the one that is only one sentence).Comment #8
Gurpartap Singh commented<p>doesn't need to go out of t(), it's multi-line text. Also, restored the "Futher ..." line. Rest is same as appears in above patches.Comment #9
drummCommitted to HEAD.
'node' should be replaced with 'post' and/or 'content.'
Comment #10
kkaefer commentedI don’t think that ‘node’ should be replaced with something else. Users might see that term somewhere and will look it up on the help page.
Comment #11
drummAny UI text that mentions 'node' is a bug. node should strictly be an API term.
Comment #12
webchickEr. But this is a glossary? Surely it makes sense to mention it here? There's help for "Node" module listed at the top; it's reasonable to assume that someone might see that and wonder, "What's a node?" What better place to find the answer to this question than in the glossary?
Comment #13
webchickFurther, "node" is in all content URLs, which is as "user-facing text" as you can get. Again, it makes sense to have a definition here.
Comment #14
drummOkay.