Search Results for 'translation'
-
AuthorSearch Results
-
October 22, 2010 at 9:56 pm #96139
In reply to: Multi-language edition
Carlos Perez
ParticipantI think the best solution is to have two separate .mo files with the interface translation and set the translation on wp-content/plugins/bp-custom.php (If you havent the file, create one) with the following code
$lang = substr($_SERVER, 0, 2);
switch ($lang){
case ‘en’:
define( ‘BPLANG’, ‘en’ );
if ( file_exists( BP_PLUGIN_DIR . ‘/bp-languages/buddypress-en.mo’ ) ) {
load_textdomain( ‘buddypress’, BP_PLUGIN_DIR . ‘/bp-languages/buddypress-en.mo’ );
}
break;
case ‘es’:
define( ‘BPLANG’, ‘es’ );
if ( file_exists( BP_PLUGIN_DIR . ‘/bp-languages/buddypress-es.mo’ ) ) {
load_textdomain( ‘buddypress’, BP_PLUGIN_DIR . ‘/bp-languages/buddypress-es.mo’ );
}
break;
}
Check that the filenames are the sameThis code detects automatically the browser language and defines the language.
Follow this article to find more about this
https://codex.buddypress.org/buddypress-site-administration/customizing-labels-messages-and-urls/October 22, 2010 at 10:31 am #96033In reply to: RSS activity feed is blank (solved)
danbpfr
ParticipantCDATA means caracter datas and doesn’t need to be passed encoded. So my conclusion is that there is somewhere a double encoding or something like this. Anyway.
I changed the code in bp-activity-template-tags.ph:1031
From
`//$title = trim( strip_tags( html_entity_decode( utf8_encode( $content[0] ) ) ) );
To
$title = strip_tags(html_entity_decode( html_entity_decode( $content[0] ) )) ;`and retrieved the accent in the translation. Now i have the title in the feed with a correct output on the title given by the user
When the accent is passed trought the translation ( i tried a normal, accent, & eacute and # &233 ) the feed fails.view here:
http://bp-fr.net/activity/feed/October 22, 2010 at 9:14 am #96032In reply to: RSS activity feed is blank (solved)
ParticipantThis morning i changed somme phrase in the translation and i can see this in the activity RSS feed:
<
October 20, 2010 at 4:45 pm #95727ParticipantBTW, I found all this helpful info:
https://codex.wordpress.org/Multilingual_WordPress
Manage multilingual posts in one post per language (for example Gengo and WPML). Translations are then linked together, indicating that one page is the translation of another.
Store all languages alternatives for each post in the same post (for example qTranslate).
Manage translations on the generated page instead of using a post context (for example Transposh and Global Translator)
Plugins that direct you to external translation services (for example Google AJAX Translation)
Plugins that link together separate WordPress installations for each language by pinging back and forth.I’ll try a few more options but sure would appreciate some suggestions.
ThanksOctober 20, 2010 at 9:48 am #95687In reply to: Changing WORDS in the TRANSLATION FILE.
Roger Coathup
ParticipantUnfortunately, a poorly written plugin and / or theme – that doesn’t use the slugs would not work.
However, you can’t legislate for that.
The instructions in the Codex page are the best and also most future proof way to code your solution – and will ensure that well written plugins / themes work.
October 20, 2010 at 9:40 am #95686In reply to: Changing WORDS in the TRANSLATION FILE.
PH (porsche)
ParticipantI was also concerned about compatibility with themes and plugins i install in the future.
October 20, 2010 at 9:38 am #95685In reply to: Changing WORDS in the TRANSLATION FILE.
Participant@rogercoathup (hat tip)!
Documentation seems indicate that this is a recommend practice. Though, Im always fearful in making changes like these..
I was wondering if there was a different method.
October 20, 2010 at 7:40 am #95677In reply to: Changing WORDS in the TRANSLATION FILE.
ParticipantDid you search the documentation?
https://codex.buddypress.org/buddypress-site-administration/customizing-labels-messages-and-urls/
October 20, 2010 at 4:23 am #95671In reply to: Changing WORDS in the TRANSLATION FILE.
Participantanyone? help?
October 19, 2010 at 4:14 pm #95607In reply to: Inconsistent translation
ParticipantSorry that was meant to say wplang obviously!
October 19, 2010 at 11:51 am #95575In reply to: Inconsistent translation
ParticipantYes, Ive defined wpland as PL_pl
October 19, 2010 at 11:46 am #95574In reply to: Inconsistent translation
Participant@boonebgorges, @hnla , @djpaul – can anyone fix the broken html in this stream?
-
AuthorSearch Results
