Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This was driving me crazy ;) ;)
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | secondary_links_description_6.x.patch | 939 bytes | David_Rothstein |
| secondary_links_description.patch | 2.55 KB | David_Rothstein | |
Comments
Comment #1
keith.smith CreditAttribution: keith.smith commentedGood catch.
Comment #2
Dries CreditAttribution: Dries commentedAh! Things like this drive me nuts too. I've committed this to CVS HEAD. I'm moving this down to DRUPAL-6 for Gabor to review. Not sure he'll want to break translations to fix this. I leave that up to Gabor to decide.
Comment #3
Gábor HojtsyI think a missing dot is better not to warrant breaking translations here, I think it is subtle enough to not be an issue if we leave it as-is in Drupal 6. Not committed to Drupal 6.
Comment #4
David_Rothstein CreditAttribution: David_Rothstein commentedJust to be really nitpicky.... the part of the patch that fixes the update function could still go into 6.x, I think. (Text that gets inserted during the Drupal 5->6 upgrade is never translated, right?) So people upgrading from Drupal 5 would get the fix, but fresh installations of Drupal 6 would have to do without the precious period ;)
Patch is attached.
Comment #5
Gábor HojtsySome people are judging Drupal 6's quality by the patches we "need" to apply between point releases. I am trying to mark these kind of fixes as "(very minor)", so to avoid us looking like having a buggy version (which we don't have). So all this said, I'd love if we could concentrate on fixing any important bugs, and not missing dots. Committed this one to Drupal 6.
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.