TODO

Carthik 20:15, 17 Dec 2004 (GMT)

Sorry, but that's totally nonsense! Users with limited English knowledge can get through this page (seeing the examples) but they DO NOT need anything related to the technology and/or how to translate WP. As I stated in the Talk page of the Translating... all these articles are aimed for different user category. Why to make a mess?

Moshu 20:45, 21 Dec 2004 (GMT)

Hey! Cool it :) We're all very reasonable people here.

I see what you mean now. Maybe then we should remove some of the stuff from Translating_WordPress into Localizing WordPress, and include a first paragraph referece to Localization Technology from the other two pages. Does that sound better?

Carthik 02:09, 22 Dec 2004 (GMT)

I can accept that the implementation aspects of localization can be separated from the list of localizations themselves, but Translating WordPress and Localizing WordPress really need to be merged. They're the exact same subject; separating them is just unnecessary.

Note: If you want to discuss merging Translating WordPress and Localizing WordPress further, we should do it on one of their Talk pages, so don't reply to this directly.

— morganiq 03:33, 22 Dec 2004 (GMT)

Alright, so we need two seperate pages:

1) A page with all the technical details about gettext in general and WordPress i18n and l10n in particular 2) A page with a "how to use a po or mo file to localize your copy of wordpress".

Can we agree on that and work towards that?

Carthik 07:11, 22 Dec 2004 (GMT)

Yup, see my comment on Talk:Translating WordPress.

— morganiq 10:11, 22 Dec 2004 (GMT)

How about making this page the central place for users to find (and possibly download) localized files (MO-only, full-version, themes...) ? I placed more than one link for my section (fr_FR), but it sure won't scale as is, if others want to centralize as much info as possible. I'm suggesting this in response to a user seemingly annoyed with having to click through many pages (wp.org -> support -> codex -> l18n page -> fr_FR site -> fr_FR.mo). Any idea on how to make it quicker for the end-user ?

XiBe 16:40, 17 May 2005 (UTC)

Attention Translators

I think it is a very bad practice to link from here directly to unzipped .po or .mo files. Some huge .po files just simply crash the browsers. Please, link to a site, where the user can find a link to download a zipped file. Another issue is offering only .po files for download. Most of the end-users lack the tools to generate a .mo file from the .po files, so practically it is useless for them. If you have the proper tools, please make a .mo file for your language, ready to download and install (xx_XX.mo). Thanks!

Moshu 18:10, 27 May 2005 (UTC)

Cleaning Up the Page

We now have a lot of information about several different topics spread across two pages: Translating WordPress and Localizing WordPress. Maybe we now need three:

1. WordPress in Your Language featuring links to get information about WordPress in different languages including downloading WordPress and foreign language support forums - information for the user.
2. Installing WordPress in Your Language (which would also fit under Installation)
3. Translating WordPress

There are now two names for the same page Translating WordPress and Localizing WordPress. I understand from the discussions above that there were merged, but they are used separately and link to the same page within this article. We need to clean things up.

Opinions? Lorelle 22:49, 5 Jun 2005 (UTC)