I just run a full string extraction of the latest Drupal user interface. Then I converted the empty translation templates to the attached text file. My aim is to get people run spell checkers on this text and identify language issues we made when writing this huge amount of text. The simplest text format used here (stripped from any HTML) is the most suitable and portable for the task, so you can use your word processor, your command line spell checker, or whatever. I am handing over this data to you in the hopes that someone will pick it up.
Whenever a spelling issue is found, a quick greping of Drupal source code can uncover the source, or I can happily attach the .pot files for reference (general.pot and installer.pot as extracted from Drupal 6, which include full (HTML included) text and exact location information).
Comment | File | Size | Author |
---|---|---|---|
#23 | d6strings_6.patch | 1.54 KB | deekayen |
#22 | d6strings_5.patch | 24.21 KB | deekayen |
#19 | d6strings_4.patch | 5.12 KB | deekayen |
#17 | d6strings_3.patch | 29.01 KB | deekayen |
#13 | d6strings_2.patch | 17.53 KB | deekayen |
Comments
Comment #1
deekayen CreditAttribution: deekayen commentedIf nothing else, here is at least a diff of the spelling corrections I made through NeoOffice 2.2.1p0 to the txt file.
Comment #2
deekayen CreditAttribution: deekayen commenteddumb mistake. diff attached for real this time.
Comment #3
catchOK here's everything I found. I included grammatical errors flagged by MS Word (or me) as well. Original text included, changes in bold, I know this isn't ideal but quickest way to do it. Some paragraphs in the .txt don't have spaces after periods, but I think that's because they're not actually paragraphs in the system, so ignoring that. Some of these appear all over the place, tried to minimse duplication.
Some of these are a bit subjective as well, lots of consistent mis-spellings and some are neologisms/technical - but leaving them in for review anyway since usage ought to be standardised.
One caveat, I'm from the UK and although I tried to leave American spellings alone, one or two might have got picked up anyway.
Here it is:
In order for Drupal to work and to proceed with the installation process you must resolve all permission issues reported above.
In order for Drupal to work, and to continue with the installation process, you must resolve all permission issues reported above.
--
Failure to connect to your MySQL database server. MySQL reports the following message:
Failed to connect to your MySQL database server. MySQL reports the following message:
Failure to connect to your PostgreSQL database server.
Failed to connect to your PostgreSQL database server.
Optional path prefix, for example "deutsch" for the German versio
Optional path prefix, for example "Deutsch" for the German versio
Optional custom domain with protocol (eg.
Optional custom domain with protocol (e.g.
untranslated strings
un-translated strings
An HTTP error @status occured.
@uri
An HTTP error @status occurred.
@uri
which to include/exlclude the block or PHP code
which to include/exclude the block or PHP code
as well as a link labeled up
as well as a link labelled up
Unpublish
Un-publish
Can not delete
Cannot delete
cachable
cacheable
those with with light
those with light
additionaly
additionally
eg 'de'
e.g. 'de'
choosen
chosen
The link text corresponding to this item to appear in the menu.
The link text corresponding to this item, to appear in the menu.
unsticky
un-sticky
boolean
Boolean
whirlygigs
whirligigs
(not sure about that one, blame Microsoft)
identifer
identifier
autocomplete
auto-complete
preprocessor
pre-processor
unban
un-ban
logfiles
log files
unpublishing
un-publishing
timezone
time-zone
throttlable
throttle-able
depedents
dependents
Autocomplete
Auto-complete
vocablulary
vocabulary
webserver
web-server
unassign
un-assign
presave
pre-save
kB
KB
succesful
successful
Tableless
Table-less
re-colorable
recolorable
Comment #4
deekayen CreditAttribution: deekayen commentedpatch against cvs attached for my previous diff and some of #3. The "some" I left out were a couple of the extra hyphen changes from #3 since I think web terminology is developing its own lingo of sorts. Either way, I think this patch should get the glaring corrections.
things worth taking a moment of thought:
renaming the $cachable var
behavior vs behaviour (I favor behavior)
Comment #5
catchYeah I agree about the hyphens, I think they count as new spellings rather than wrong.
Comment #6
keith.smith CreditAttribution: keith.smith commentedThese are some good changes, and while I didn't do an exhaustive review, I did read through most of them.
In #184461, we briefly discussed alternative spellings, and I think behavior is the version to go with.
I'll go through this later today when I have some time, and will also read through Gabor's list of strings in case I see others that might need to be included.
I did note an instance of exchanging "smileys" for "smilies" I think "smileys" is actually correct when one is talking about multiple, uh, smileys (or so says http://dictionary.reference.com/browse/smileys). Personally, I'd just avoid that by changing the word to "emoticons".
Comment #7
deekayen CreditAttribution: deekayen commentedRevised for emoticons - good call IMO.
I should also note I agree with the table-less and re-colorable revisions, but they didn't turn up in my grep, so they're not in the patch. Since they fall in a debatable category, I think they can be safely skipped for now.
Comment #8
deekayen CreditAttribution: deekayen commenteddidn't notice status change
Comment #9
keith.smith CreditAttribution: keith.smith commentedI disagree on the increased use of hyphens, for example, the change from "untranslatable" to "un-translatable."
That said, I realize there are no universally accepted principles for the use of hyphens. My Chicago Manual of Style tends to spell most everything solid, including un- and non- prefixes. AP generally spells the prefixes anti- and non- hyphenated, and un- solid.
If the meaning can be made more clear with a hyphen, like the differences between "re-creation" and "recreation" or "walking stick" and "walking-stick", then you need a hyphen. If there's a proper noun involved (like "anti-Semitic"), involves figures (pre-2007), or the word is already hyphenated (un-self-conscious), then you need a hyphen.
Otherwise, I say down with hyphens :)
Maybe we should first complete a "triage" patch that only includes the misspellings that (IMO) absolutely must be corrected.
Comment #10
Dries CreditAttribution: Dries commentedI'm not a fan of the additional hyphens either.
Comment #11
deekayen CreditAttribution: deekayen commentedremoves patches against untranslated (previous patch changed to un-translated)
Comment #12
keith.smith CreditAttribution: keith.smith commentedI'm attaching a patch that builds off the last one, but only includes misspellings -- if I thought the change was very debatable (read that: went beyond changing a spelling error or went beyond standardizing on a particular spelling variant), I did not include it in the attached patch.
All or most of the changes that aren't in this patch, though, will still likely need to be made, but they may involve additional discussion. Some of the strings in Gabor's list read as somewhat tortured, and should perhaps be revisited under the guise of improving usability. Some of the suggested changes, like cachable to cacheable, are debatable; both spellings are *technically* correct so it isn't as necessary to correct them in this iteration as some of the other glaring spelling errors. Of course, both behaviour and behavior are correct; this patch substitutes behavior for behaviour purely in the interest of consistency.
Changes for ease of reference:
Comment #13
deekayen CreditAttribution: deekayen commentedProper diff attached. I even left out behaviour changes to make it I think ultimately non-contriversial (unless there's a strict spelling error remaining).
Comment #14
catchfwiw, if behaviour is acceptable in the US, it's also the only one of those spellings used in the UK (and I presume Aus/NZ), so +1 for me on standardising on that.
Comment #15
Crell CreditAttribution: Crell commented"behaviour" is not a valid spelling in American English. My understanding is that core uses American English, and if necessary British English is a quite simple translation pack.
Comment #16
ChrisKennedy CreditAttribution: ChrisKennedy commentedThis looks okay to me, but I see that the 'Contents of the "Pages" block; contain' to contains change in block.install isn't in the actual patch. Is that intentional?
Comment #17
deekayen CreditAttribution: deekayen commentedquite a collection of fixes to choose from now...
contain vs contains was an oversight in the previous patch
adds back behavior
Comment #18
Gábor HojtsyOK committed #17, being the noncontroversial patch; thanks! Now the question is what fixes are still up for discussion? I noticed that some (non-typo) fixes from #3 were not included, like Failure to Failed.
Comment #19
deekayen CreditAttribution: deekayen commentedI like Failed instead of Failure myself, but this patch removes a consistency issue from context. All the other DB error messages begin, "We were unable to". Given the beta status, I think the consistency is a bigger issue than should be handled in this round. If we want to make this one particular error more wordy like the others, it could start "There was a failure". I don't like the wordiness of the other errors or the fact the software is "we", so I think Failed is a good precedent for the other errors to follow in D7. If D6 wasn't beta, I'd be rolling a patch to re-word the other errors, too. Opinions?
Comment #20
catchI reckon all the errors should be patched to use "Failed to" rather than "We were unable to". Lots of wordings (and entire help texts) still going in to D6 so shouldn't be an issue with that.
Comment #21
Gábor HojtsyIndeed, interface strings are not frozen, we are fixing and improving consistency now. Translators are still told to wait for the green light when we (mostly) fix interface text.
Comment #22
deekayen CreditAttribution: deekayen commentedImplement #20. Rewords half of one error has follows:
- drupal_set_message(st('We were able to connect to the MySQL database server (which means your username and password are valid) but not able to select your database. [snip]
+ drupal_set_message(st('Failed to select your database on your MySQL database server, which means the connection username and password are valid, but there is a problem accessing your data. [snip]
Comment #23
deekayen CreditAttribution: deekayen commentedImplement install change from #3.
Comment #24
Dries CreditAttribution: Dries commentedCommitted both patches. Thanks a bundle, deekayen.
Comment #25
(not verified) CreditAttribution: commentedAutomatically closed -- issue fixed for two weeks with no activity.