#19509 closed defect (bug) (invalid)
String issue at (wp-load.php)
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 3.3 |
| Component: | General | Keywords: | |
| Focuses: | Cc: |
Description
I have translated this string to Arabic:
Then I removed wp-config.php to produce the error but then I found text still displayed in English instead of Arabic.
Should I translate the string manually at wp-load.php ?!
Change History (7)
#2
in reply to:
↑ description
;
follow-up:
↓ 3
@
13 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
#3
in reply to:
↑ 2
;
follow-up:
↓ 4
@
13 years ago
Replying to nacin:
Replying to rasheed:
Should I translate the string manually at wp-load.php ?!
No. This will automatically be done by the build process when you build a release through Rosetta.
Could I build a test release through Rosseta ? I tried to do that but I got invalid source error. which WordPress revision number should I enter ?
#4
in reply to:
↑ 3
@
13 years ago
Replying to rasheed:
Could I build a test release through Rosseta ? I tried to do that but I got invalid source error. which WordPress revision number should I enter ?
You should be able to find an answer to that on wppolyglots.
#6
@
13 years ago
OK I created a test release from the trunk:
http://ar.wordpress.org/builds/ar/trunk/wordpress-3.3-RC3-ar.zip
The string wasn't translated to Arabic.
Could anyone check it ?
#7
@
13 years ago
Your string wasn't translated because of this:
http://wppolyglots.wordpress.com/2011/05/16/hello-i-was-building-a-new-beta1-version/
I reported this bug six months ago, but it still hasn't been corrected. If you are building a package from the trunk folder, then delete the old ar.mo. Or you could create a 3.3 tag and upload all files there.
Replying to rasheed:
No. This will automatically be done by the build process when you build a release through Rosetta.