|
#1
08-19-2009, 02:33 AM
|
|||
|
|||
Suggestion: Changing the Translation Format
I use Gabfire's Advanced Newspaper, and I find it the most amazing WordPress theme for online publications. My only issue with the coding is the format of the translation. I wish it was translated according to WordPress codex.
With the current formatting I cannot add certain words within the PHP files or new templates to the translation file, neither I can use the theme in a bilingual website. Also, other things such as different styles of writing dates have problems. I will appreciate if you add this change to the list of changes for the next updates. More info about this subject can be found here: http://wpml.org/2009/05/wordpress-theme-localization/ All you need to do is the step one mentioned in this link. The step two (collection of the terms) can be easily done by a great plugin named "Codestyling Localization Plugin": http://tinyurl.com/bdwppz The rest is done by the users of the theme. Last edited by bijan; 08-19-2009 at 02:42 AM. 
|
|
#2
08-19-2009, 08:30 AM
|
|||
|
|||
|
bijan,
I have the knowledge of .po files and how to implement it to a theme, but it is extremely hard for most of our clients to translate a theme using a .po file. That is why the translation is implemented as a single .php file and globally called by other template files. "Codestyling Localization Plugin": We do not really want to rely on plugins with our themes, since if the development of any plugin is stopped by the plugin developer, we can start having problems with our clients for future releases of WordPress where plugin would possibly not work. I am curious to learn the limitation with translation template. would you please give me an example of what you were trying to achieve?
|
|
#3
11-11-2009, 01:50 AM
|
|||
|
|||
|
There are many problems with a "non-.po" format. Here is a list of the problems I have with the current format:
1. Time and date format: not all dates and time formats follow the latin language and Christian-based order. Using ".po" format one can keep the date format in the theme untouched and define the right format for the date in the language file. The new style becomes active if the respective language is defined in the configuration file as the language of the site. The site shows the correct date format without editing any of the theme files. It is not possible with the current language files. One needs to edit every theme file that has dates in them. 2. Comma: Comma looks different in certain languages, and that is easy to define in a ".po" file. For example you can easily define an Arabic/Persian comma in the ".po" file and it replaces all the Latin commas in the theme with the Arabic/Persian version. Such a thing it is not possible with the PHP language file. To fix the problem one needs to edit all the files in the theme to get rid of the wrong comma. 3. Upgrading the theme: Currently one needs to fix many things inside the theme's PHP files to change the language of Advanced Newspaper to a non-Latin based language. Editing all the files in the theme is problematic since it makes the upgrade almost impossible. The ".po" files make the upgrading the theme much easier. 4. Adding terms to the language file: One can easily define new terms and their translations to the ".po" file. It is not the same for the current PHP file. Maybe I do not know how to do it but that is one of the problems I still have. 5. Plural forms: Plural names are made differently in different languages. One can easily define the plural form in ".po" file. I could not do the same with the PHP language file. 6. Bilingual Sites: One can not make a bilingual site with the current format of the translations (if one of the languages is not a Latin-Alphabet-based language) since some of the core files of the theme need to be changed. For example in my case by changing the format of the dates and commas inside the PHP files I made it impossible to have a bilingual site that shows these elements correctly for both languages.
|
|
#4
11-11-2009, 01:53 AM
|
|||
|
|||
|
By the way "Codestyling Localization Plugin" is a tool to translate the ".po" files and save them to the site. One does not need it to run the theme. It just makes the translation/saving/up-laoding process very easy. Much easier than editing the current PHP file. After the translation the user can disable the plugin. It has nothing to do anything with the theme.
|
|
#5
11-11-2009, 06:43 AM
|
|||
|
|||
|
Quote:
To convert all translations into .po format is as well in our to do list at the moment.
|
|
#6
02-10-2010, 06:10 PM
|
|||
|
|||
|
Mehmet, is there a roadmap for each theme? I couldn't seem to find one.
|
|
#7
02-10-2010, 07:34 PM
|
|||
|
|||
|
Quote:
|
|
#8
02-13-2010, 01:00 PM
|
|||
|
|||
|
As in regards to the translation of themes, this is my point of view:
- for beginners, using a php file for localization is easier. POEdit on PC is complicated. I haven't tried the plugin that generates .mo. - unfortunately, the PHP file doesn't translate everything. Many title attributes aren't available in the php file. This is why ultimately PO files are the best. - My final proposition: each theme should have an integrated translation interface. A bit like Wordpress' possibility to modify php and CSS files within the admin. Ideally, this interface creates an .mo file (I'm not sure if this is even possible)
|
|
#9
02-13-2010, 04:51 PM
|
|||
|
|||
|
Quote:
You can actually control translations via admin dashboard of wordpress for .po files
|
|
#10
03-05-2010, 11:28 AM
|
|||
|
|||
|
Quote:
For translation, have you checked that thread
|
 |
| Tags |
| language, localization, translation |
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
