Changes between Initial Version and Version 1 of Ticket #26879, comment 21
- Timestamp:
- 03/08/2014 10:27:48 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26879, comment 21
initial v1 1 1 2 OK, my apologies for the delay. Here 's a patch.2 OK, my apologies for the delay. Here are a couple of patches. 3 3 4 4 … … 30 30 2. Now to the main text, proposing something along the lines of 31 31 32 "OK! We'll need some information about your database.33 34 This information is available through your web host. If you don't have it, you'll need to get in touch with them. Here's what you need:"32 "OK! We'll need some information about your database. 33 34 This information is available through your web host. If you don't have it, you'll need to get in touch with them. Here's what you need:" 35 35 36 36 So, most people just need to know which information they need, not the immediate explanation about what happens if it goes wrong - they'll naturally skip over the whole paraprah if it's too long, so splitting it up here. if something does go wrong, or they're confused, they'll re-read all information naturally, IMHO. In short, I'm trying to make sure the important bit is read. … … 47 47 Unfortunately, this led to creating a couple of extra translatable strings of text (I created two new paragraphs, each of one line, effectively, to avoid using a br tag.) This leads me to needing help and input from those who know what they are doing with such things: 48 48 49 a) It creates extra translation strings. Boo. However, it avoids including HTML in a translatable string, which seems to be something WP avoids.50 b) Aware that with the first version of wp-load.php, and indeed with the links to the documentation the reverse is happening - an a href is being included in a translatable string. To my uneducated eye, I suspect this is something of a different case, as, at least the docs link could go to a translated version of the codex page (shudder). So, in short, I did the best with the little knowledge I have, and some kind help from @DH-Shredder.49 a) It creates extra translation strings. Boo. However, it avoids including HTML in a translatable string, which seems to be something WP avoids. 50 b) Aware that with the first version of wp-load.php, and indeed with the links to the documentation the reverse is happening - an a href is being included in a translatable string. To my uneducated eye, I suspect this is something of a different case, as, at least the docs link could go to a translated version of the codex page (shudder). So, in short, I did the best with the little knowledge I have, and some kind help from @DH-Shredder. 51 51 52 52 At this point.. @vanillalounge - help?!