ähm, one moment please - the string i posted is the default drupal one. Aside, if this is the breadcrumb - it shouldn't be translatable as *one* string! If this is one string i'm unable to change this » char with a custom theme function.
So i found a bug... this string should be splitted in their elements. Aside this strings are core strings and should be reusable...
oh good grief. it's the body of the email notification. you make it seem like we've committed a mortal sin here. i'm loosing patience in going out of my way to make this a breeze to translate. hass, if you supplied patches more often then scorn, i might be more inclined to fix stuff like this.
however, if we change this, it's going to make it *HARDER* to translate for RTL people. they might want to translate the whole thing "backwards", which if i split it up for you will be impossible. in fact, i believe that's why i choose to wrap the whole thing in t() in the first place. so, i'm going to get a 2nd opinion from another translator, then probably mark this "by design".
Spoke to killes. He agreed this is painful for RTL folks. None of this is worth the hassle. The human-readable menu path was just there as a means to help usability, but if it's going to cause grief, forget it.
I'm realizing that this probably isn't in the breadcrumb, we're probably talking about some message that's sent out.
If that is the case, the >> is appropriate, which is part of the standard that drupal.org uses when describing a navigation path: (For example: http://drupal.org/handbook/modules/node )
Either that or, hass, you need to make your reports more than 1 sentence. You need to make sure we can understand the context. Otherwise I will just start closing them without comment.
@dww: no - this is not a mortal sin... it's the "won't fixer" and i don't like this unhelpful manner. i'm sorry i haven't looked into code about this string and where it is used and thought it's a breadcrumb, too. I translated the module and wonder what this is, nothing more. I was in "translation mode" and haven't spend time on a code review... thank you for helpfull handbook link, but i cannot know everything.
Comments
Comment #1
merlinofchaos commentedThe >> is in the breadcrumb and is completely part of your theme; update status has no control over that at all.
Comment #2
hass commentedähm, one moment please - the string i posted is the default drupal one. Aside, if this is the breadcrumb - it shouldn't be translatable as *one* string! If this is one string i'm unable to change this
»char with a custom theme function.So i found a bug... this string should be splitted in their elements. Aside this strings are core strings and should be reusable...
Comment #3
dwwoh good grief. it's the body of the email notification. you make it seem like we've committed a mortal sin here. i'm loosing patience in going out of my way to make this a breeze to translate. hass, if you supplied patches more often then scorn, i might be more inclined to fix stuff like this.
however, if we change this, it's going to make it *HARDER* to translate for RTL people. they might want to translate the whole thing "backwards", which if i split it up for you will be impossible. in fact, i believe that's why i choose to wrap the whole thing in t() in the first place. so, i'm going to get a 2nd opinion from another translator, then probably mark this "by design".
Comment #4
merlinofchaos commentedI'm confused. What does update status have to do with translating the breadcrumb...at all?
Comment #5
dwwSpoke to killes. He agreed this is painful for RTL folks. None of this is worth the hassle. The human-readable menu path was just there as a means to help usability, but if it's going to cause grief, forget it.
http://drupal.org/cvs?commit=71780
Comment #6
merlinofchaos commentedI'm realizing that this probably isn't in the breadcrumb, we're probably talking about some message that's sent out.
If that is the case, the >> is appropriate, which is part of the standard that drupal.org uses when describing a navigation path: (For example: http://drupal.org/handbook/modules/node )
Either that or, hass, you need to make your reports more than 1 sentence. You need to make sure we can understand the context. Otherwise I will just start closing them without comment.
Comment #7
dwwComment #8
hass commented@dww: no - this is not a mortal sin... it's the "won't fixer" and i don't like this unhelpful manner. i'm sorry i haven't looked into code about this string and where it is used and thought it's a breadcrumb, too. I translated the module and wonder what this is, nothing more. I was in "translation mode" and haven't spend time on a code review... thank you for helpfull handbook link, but i cannot know everything.
i appologize for the inconvience.
Comment #9
(not verified) commented