February 2, 2014 at 10:12 pm #218519
I’ve been trying to get the “built in” language files to show something for a while. I’ve opened them with poedit and have changed the language in the wp-config.php file but I can’t seem to see anything modifications in the theme?
the HTML shows <html lang=”‘de_DE’” class=”chrome chrome32 html_boxed “> but when looking at the blog which reads “this entry has 0 Comments in Uncategorized” it’s still English?
I suspect that this is something that should be taken care of by the language file, no? Same thing with a button called “Post Comment.” Should it not be translated through the language file and shown in the front-end?
What could I be missing?February 3, 2014 at 4:42 am #218587February 4, 2014 at 1:41 am #219072
Yes, I have the WPML plugin installed. I’m just looking to be able to deploy a “spanish” version of “dutch version” or the website independently. I just want the default language to be one language. No switching, no multiple versions of posts…. Just a different language.
But I can’t see anything changing?
February 4, 2014 at 6:22 am #219199
- This reply was modified 4 years, 1 month ago by kork.
That said, much of the site is now able to be in another language, but for things like:
this entry has 0 Comments
Is that something that needs to change in the source code, or can that be done with the language file?February 4, 2014 at 6:48 am #219204February 4, 2014 at 9:45 am #219235
I suggest to use Codestyling to translate these text strings. Install the plugin ( http://wordpress.org/plugins/codestyling-localization/ ), go to Tools > Localization and select “Themes”. Then search for “Propulsion” from the list and select your language and click the “create po-file” button. Click on “Rescan” to search for all text strings. Afterwards click on “Edit” and translate the required strings from the “avia_framework” textdomain. At least click the “create mo file” button next to the “Textdomain” selection dropdown (top left corner).
PeterFebruary 4, 2014 at 5:04 pm #219482
That was where I started as I’ve done this before with the enfold theme. Pretty simple stuff.
But for Propulsion, I took “Error 404 – page not found” the very first one in the list and set the translation to be “El Pago not Foundo” just to test it. The HTML reads “<html lang=”es-ES” class=”chrome chrome32 html_boxed “>
Nope, going to a 404 still shows the English version. I also tried the “Send” button for a form… Same thing. Doesn’t replace the text.February 5, 2014 at 2:54 pm #219926
Okay, where are the .mo and .po files actually supposed to be once generated? I’ve found them in the root of the theme, but with enfold they seem to exist in the language folder in the root of content. I’ve opened the .po file with poedit and the changes I’m making are in the file.
But the theme is quite simply… not loading the translations. Any of them. it_IT, es_ES, it doesn’t matter. Not loading.February 6, 2014 at 11:07 am #220414
By default the language files should be in a folder called “lang” (wp-content/themes/propulsion/lang/). I uploaded the German translation files here: http://www.xup.in/dl,12906936/propulsion.zip/ – I know that they’re working on my server and they should also work for you.
PeterFebruary 6, 2014 at 3:08 pm #220466
When I created the spanish .mo file using the localization plugin, it created it in the root/languages folder and called it “avia_framework-es_ES.mo”
But it’s not actually using the translations provided in the file… This is very frustrating.February 8, 2014 at 11:48 am #221199
Try to rename it to “es_ES.mo” and place it into the wp-content/themes/propulsion/lang/ folder.
PeterFebruary 11, 2014 at 3:36 am #222015
The topic ‘What does the language file actually change? Having problems even just testing!’ is closed to new replies.