100% translatable and localizable on wordpress.org

[bobbingwide]

oik-bwtrace needs to be internationalized and localized using the same i18n and l10n techniques as for oik. See https://github.com/bobbingwide/oik/issues/#9.

[bobbingwide]

Files which will need to be renamed so that strings can be found by WordPress.org and not found by makeoik are:

file	new name	comments
admin/oik-bwaction.inc	admin/oik-bwaction.inc_	Make it properly deprecated
admin/oik-bwtrace.inc	admin/oik-bwtrace.php
includes/bwtrace.inc	includes/bwtrace.php	Already deprecated in v1.24
includes/oik-bwtrace.inc	includes/oik-actions.php	Already deprecated in v1.24

[bobbingwide]

During recent testing with phpunit I discovered that several of the UK English translations done in wordpress.org are different from my automatic translations.
Some of the improvements are OK. Others are not.
OK improvements include:

• Spelling AJAX as Ajax
• Removal of spaces inside parentheses eg ( days ) becomes (days)
• Changing of hyphens to – ?

Invalid improvements are:

• the addition of after in "Reset trace file every transaction" and similar strings.

This is not what happens. The reset is performed at the start of the transaction.
Perhaps the US English could be changed to "Reset trace file for every transaction".
Or a translator's note to indicate when the resetting occurs.

[bobbingwide]

I'm reviewing this issue for v3.5.0.
If I change the US English strings then I'll have to change the test cases.
If I write translator notes then it may not be clear to the US English language users exactly what's going to happen for the "Rest trace file" related strings.
I think the best thing to do is to compare my UK English .pot file with the latest one on WordPress.org