first of all I tried to get the strings mor drupalish
* no Camel Case
* double spaces in t()'s removed
* Email, email, etc => e-mail
* put _install() in its own file forward.install
* fix things like
...t('Thank you for your interest in spreading the word on').' '.variable_get('site_name', 'drupal').'.</p><p>'...
to
...t('Thank you for your interest in spreading the word on %site_name.', array('%site_name' => variable_get('site_name', 'drupal')))...
* t("e-mail this %type") and t("e-mail this page") are two different things now
-->i was not able to translate this in a proper way to german
-->"e-mail this %type" is still not perfect for the german language... but I have no better solution...
* removed ? > at the end of the file
I was not able to do a new pot-file, because I'm using the "new" SuSE Linux 10.1 which sucks in many ways
so please make one and look at it again if there are still some inconsistencies
ther is still one inconsistency at _settings():
on some textareas like "e-Postcard Message body:"
we have a variables like "%site"
on other textareas like the "Thank You Message:" or "Forward Instructions:" the user has no access to them - the site name gets inserted before the user sees the textarea
we have to decide if we want to have variables like %site on every textarea or if we remove them entirely...
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | forward_new.patch.txt | 45.36 KB | Tobias Maier |
| #15 | forward_0.patch | 49.6 KB | david lesieur |
| #11 | forward.patch_3.txt | 30.67 KB | Tobias Maier |
| #10 | forward.patch_2.txt | 30.67 KB | Tobias Maier |
| #8 | forward.patch_1.txt | 31.31 KB | Tobias Maier |
Comments
Comment #1
Tobias Maier commentedand here comes thie .install file
you can remove forward.mysql
Comment #2
Tobias Maier commentedComment #3
Tobias Maier commentedhere comes a new update of my changes
* update-path for the new .install file (UTF8 support as of http://drupal.org/node/22218#utf8_sql)
* removed some redundant drupal_get_path_alias() calls, because drupal_goto() calls url() which calls drupal_get_path_alias() again
Comment #4
seanrLooks good, but I prefer to keep two spaces between sentences for grammatical reasons.
Comment #5
Tobias Maier commentedI should mention that I did the second argument of variable_get() calls consistent
Comment #6
Tobias Maier commentedis it normal in the english language to have two spaces between two sentences?
you have to know this is not my primary language
Comment #7
seanrDepends. Most style guides I've seen recommend it, but it's not necessary. My preference is to use two simply because it better deliniates the sentence boundaries, but I suppose its more a matter of personal preference than anything.
Comment #8
Tobias Maier commentedI replaced
print theme("page", $output);with
return $output;I want to point you to
without this forward_instructions where never printed...
Comment #9
Tobias Maier commentedI let the double spacing issue as it is in the patch for now
I'm too tired to change this for today
If you may commit this and you think this is necessary to change back,
then you can do this for the few places where it is needed
imho we dont do it in the rest of the drupal world so we shouldnt do it in contrib modules, too...
good night,
tobi
Comment #10
Tobias Maier commentedwell, here comes a new version.
I hope this one fits all of our needs...
Comment #11
Tobias Maier commenteda very small change...
Comment #12
david lesieur commentedI like (and need) those changes. However, I have noticed something suspicious in forward.module, near line 343. With the patch, the following:
... becomes:
Any explanation? Thanks.
Comment #13
seanrIt's this part of the patch:
That should be changed to this:
Comment #14
david lesieur commentedAlso, I'm not too sure about some of the changes in function forward_link().
Before the patch, variable "forward_show_on_main" was actually used in forward_link() to determine if the links are to be shown on teasers, which I think is the kind of option we really need. The problem was, the variable was misnamed; it should have been "forward_show_on_teasers". I don't think we need a special case for the home page. So I'd remove the new checks for drupal_is_front_page() and rename the variable. What do you think? If agreed, I can re-roll the patch with that change.
Comment #15
david lesieur commentedHere is an improved patch that includes the fix in #13 and implements my comment in #14.
This also fixes some uses of t() that caused extractor.php to complain (and would have caused user-entered strings to find their way into the locales table). There were even some nested t()'s in the form of t(variable_get('var', t('str'))); ! These are fixed too.
Ah, and this patch also includes an updated forward.pot file.
I hope everybody will be pleased with this. ;-)
French and Spanish translations of the module are coming soon and will be based on this patch.
Comment #16
david lesieur commentedFYI: Here is the promised French translation.
Comment #17
Tobias Maier commentedhello Sean,
whats about the patch?
do you plan to commit it or does it need more changes?
Comment #18
seanrA lot of these changes and many others have been made since then so I'm quite cetain the patch will no longer apply. I'm not sure exactly which changes were implemented at this point since I got very busy with other work and lost track of it for a bit. If someone can re-roll the patch against the latest version I'll commit it.
Comment #19
Tobias Maier commentedi applied Davids patch which looks good to me,
tested it if it works
and made a new patch file
Comment #20
seanrOK, will test this today and hopefully get it committed today or Monday.
Comment #21
seanrThank you very much, BTW.
Comment #22
alexandreracine commentedAny update on this one? :)
Comment #23
alexandreracine commentedSeems ok...