Search Results for 'translation'
-
AuthorSearch Results
-
April 3, 2009 at 8:09 pm #41752
In reply to: How do you call Wire in your language?
ostropunkParticipantI always associated wire with the telegraph. The Swedish translation has it as “kanal”, that’s channel in English. I changed it to “trÃ¥d” which translates to thread. In this context it is however closer to wire as in wireless communication which translates to “trÃ¥dlöskommunikation”. The Swedish word “vajer” simply don’t hold the communication meaning the word has in English.
April 1, 2009 at 2:52 pm #41594In reply to: don´t load language on ajax request
Burt AdsitParticipantHello. Hmmm. Never thought of that. Let me go look at this.
(later)
I don’t see how that is possible. When bp does an ajax call it loads the wp environment and all plugins get fired up including bp. Doing all that loads the translation files if your site is setup that way. The call is in bp-core.php.
April 1, 2009 at 11:20 am #41578In reply to: What about README translation ?
Paul Wong-GibbsKeymasterSuggest waiting for v1.0 before translating as odds are the readme.txt will be rewritten seeral times before then.
April 1, 2009 at 11:04 am #41576In reply to: What about README translation ?
Aron JayParticipantask Trent.
March 28, 2009 at 2:32 am #41206In reply to: I want to speak Spotlish
Lance WillettParticipantNo side effects that I know of, though our setup is still \”young\” (only been live for just over a month) so I don\’t know the long-term implications yet.
One thing I will mention, though — if you site has been live for a while you\’ll have to do some SQL cleanup in the database to rename things that have been cached (like user activity). For example:
UPDATE wp_bp_activity_sitewide SET content = replace(content,\' wire:\',\' wall:\');
What do you have to do different now that you didn\’t before you had the faux translation?
Actually, the biggest difference is a positive one: instead of hand-changing all the instances of \”Wire\” in the plugin and theme files we keep that in the language file instead. Since the language file (and the bp-custom file) aren\’t in the BuddyPress SVN repo they will never get overwritten when we upgrade.
March 28, 2009 at 12:06 am #41196In reply to: I want to speak Spotlish
Burt AdsitParticipantHa! I knew it was a good idea. I do have one every once in awhile.
Any side effects of this we should know about Lance? What do you have to do different now that you didn’t before you had the faux translation?
March 27, 2009 at 9:34 pm #41183In reply to: Rename Wire Link
Lance WillettParticipantTo create a custom translation file just for the purpose of label changes, see my instructions in https://buddypress.org/forums/topic.php?id=1877#post-9927.
To be honest, that’s all I did with my translation was change “Wire” to “Wall” for the BuddyPress setup at Tucson Digital Arts Community.
March 27, 2009 at 9:24 pm #41181In reply to: I want to speak Spotlish
Lance WillettParticipantHere is how I did a custom translation to replace slugs and labels. I’m replacing my language name with spots so you can see how it would work for you.
1. First I opened the POT file, copied it to a .po version, and then made the changes I wanted in a text editor (most with search and replace, but also had to do some new lines by hand).
2. I uploaded the .po file to my web server, and ran this from a command line:
msgfmt -o buddypress-spots.mo buddypress-spots.po
3. In my bp-custom file (wp-content/mu-plugins/bp-custom.php) I added a language definition:
define( 'BPLANG', 'spots' );
if ( file_exists( ABSPATH . MUPLUGINDIR . '/bp-languages/buddypress-' . BPLANG . '.mo' ) ) {
load_textdomain( 'buddypress', ABSPATH . MUPLUGINDIR . '/bp-languages/buddypress-' . BPLANG . '.mo' );
}
4. Then I went into wp-content/mu-plugins/bp-languages and added the spots.mo file there.
This solution is better (in my opinion) than using the define (‘WPLANG’, ”); in your wp-config.php file, and won’t break when you upgrade BuddyPress.
March 27, 2009 at 4:35 pm #41170In reply to: I want to speak Spotlish
Burt AdsitParticipantThe reason I suggested the translation route is that modifying the theme causes people to hesitate when upgrading. They don’t want to lose any custom they have. If I’m operating off a working copy of the svn trunk I can take my chances on an svn merge going ok. That it will skip my custom. However if my upgrade process is to replace the old code with the new code, just upload to the server, then I’m less likely to upgrade bp.
If it’s possible to achieve a solution without touching *any* code, I’m all for it.
March 27, 2009 at 9:46 am #41133In reply to: Rename Wire Link
trcwestParticipantyes i want to doo this too andy…
You could create a custom translation file and rename everything how you like.
I am just wanting to know how to do it properly and as of yet i have not found a simple show how… that is how to edit the .pot and then impliment it..
March 27, 2009 at 12:38 am #41108In reply to: Swedish translation done
trcwestParticipantim interested in using translation to change the words groups and group to spots and spot respectively..
so basically use the translation technique to change and customise what things are called on the site..
March 22, 2009 at 7:56 am #40614In reply to: When will buddypress release stable version?
Burt AdsitParticipantipin, new translation files are generated frequently. Check the svn trunk for notifications such as this: POT, generated from r1247
I believe that one was generated this past Friday.
March 21, 2009 at 12:18 am #40572In reply to: BPDEV Plugins have now localization support
danbpfrParticipanti made a french translation; Where can i give it to you ?
Dan
.mo and .po files downloadable from here:
http://buddypress-fr.net/bpdemo/2009/03/21/traduction-pour-buddypressdev/
March 16, 2009 at 5:28 pm #40138In reply to: link problem with multilanguage installation
Burt AdsitParticipantThe member theme and some core functions all refer to the main blog. The will use whatever translation is active on that blog.
March 14, 2009 at 3:14 am #39973mspechtParticipantCould this be done initially via a custom translation?
March 14, 2009 at 2:53 am #39971In reply to: Several widgets disappear when .mo file installed
z-20MemberHello all.
I had this same problem when I tried to use the Portuguese translation and this is how I fixed it.
1) Remove all your bp widgets.
2) Open translation.po
3) Find bp-core/bp-core-widgets.php (it is mentioned many times and write down the line numbers)
4) Open mu-plugins/bp-core/bp-core-widgets.php
5) Translate manually the lines where the translation file was supposed to do it.
6) re-upload mu-plugins/bp-core/bp-core-widgets.php
7) activate widgets that now will be named on your translation language e.g. “welcome” will be “Bienvenido”
send me a beer!
Voila!
March 12, 2009 at 5:38 pm #39840In reply to: Swedish translation done
MartinNr5ParticipantI’ve updated the files as I found a small error (no space before “medlemmar”).
March 11, 2009 at 7:29 pm #39772In reply to: How to translate BuddyPress?
tamphetParticipanthow are “the settings…” set??
I use the Poedit to do the translation. I always get this error message.
11:23:10: wampwww8phetwp-contentmu-pluginsbp-languagesbuddypress-vi.po:844: a format specification for argument 1 doesn’t exist in ‘msgstr’
11:23:10: wampwww8phetwp-contentmu-pluginsbp-languagesbuddypress-vi.po:2566: a format specification for argument 1 doesn’t exist in ‘msgstr’
11:23:10: msgfmt: found 2 fatal errors.
I believe that related to Settings…. But I don’t know how to set it.
Can someone help please.
thanks
March 10, 2009 at 1:47 pm #39678In reply to: Mass update ‘friends’ terminology
smuellerParticipantAnybody have any suggestions on this? I’m just looking to change the term ‘Friends’ to ‘Contacts’ throughout the install. I’m not really in need of a ‘translation’ per se – just an update to the existing default terms. Any help would be greatly appreciated.
March 9, 2009 at 11:58 pm #39620In reply to: Problem with translations!?
AlexParticipant‘Trunk’ means the latest development build in the SVN repository, which you can access and ‘check out’ here:
https://svn.buddypress.org/trunk
More information about using SVN here: https://codex.wordpress.org/SVN
March 9, 2009 at 5:14 pm #39574In reply to: Problem with translations!?
rustedMemberI have no idea what that means?
March 9, 2009 at 3:05 pm #39561In reply to: Problem with translations!?
Andy PeatlingKeymasterMake sure you are using the trunk and not RC1.
March 9, 2009 at 12:58 pm #39551In reply to: Problem with translations!?
lucifixParticipantYou can send me those 2 files to me and I’ll check it on my server: lucifix[that@thing]slo-foto[thatDOTthing]net
March 9, 2009 at 12:54 pm #39550In reply to: Problem with translations!?
rustedMemberthanks, but did not work… Same problem continues
March 9, 2009 at 12:33 pm #39549In reply to: Problem with translations!?
lucifixParticipantI had similar problems with translating, then I figure it out what I did wrong. You should uploaded these files to server:
1. /wp-content/mu-plugins/bp-languages/
– file: buddypress-***.mo
2. /wp-includes/languages/
– file: ***.mo
*** is the name of your language (etc. for Slovenian language: sl_SI)
I hope this helps
-
AuthorSearch Results