Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'translation'

Viewing 25 results - 1,126 through 1,150 (of 1,381 total)
  • Author
    Search Results
  • #55950
    Xevo
    Participant

    Found out how it works in poEdit, this’ll make my job easier. :)

    Instead of the full 100%, I only have to do about 30% translation.

    #55940
    Boone Gorges
    Keymaster

    Here’s a really helpful guide to translating using poedit: http://urbangiraffe.com/articles/translating-wordpress-themes-and-plugins/

    #55937
    Bowe
    Participant

    If you need any help translating let me know, I’ll be glad to help :) I also have no idea how the translation stuff works, but that shouldnt be so hard?!

    #55575
    Xevo
    Participant

    It has both his po and mo, so what do I do now? I’m new to translating. And since I’m also planning on translating both bbpress and wpmu. I’m eager to learn. :)

    And btw, I also use Poedit.

    #55573

    @xevo

    If the dutch language pack comes with both po’s and mo’s, then you can rescan the buddypress directory with poedit, update the database from the source, and then proceed with your changes.

    If not, then you’re sort-of out of luck I think. I haven’t found a tool to merge an existing mo into a new po, so it would be a manual process of copy and pasting each preexisting translation.

    #7375
    Xevo
    Participant

    Hi bp community,

    I’m planning on making a translation for the newest buddypress in Dutch, but I saw that there’s already an old translation for Dutch. It’s less time consuming to use an existing one after all..

    Can I see somewhere whats changed since then (1.0RC) and what I have to translate or change? I geuss the trac, but Im not farmiliar with working with that.

    Thanks,

    Mitchell

    #7353

    Topic: BP Translate

    in group forum Third Party Plugins

    Translation suite for BuddyPress (Beta super bleeding edge use-at-your-own-risk release)

    http://wordpress.org/extend/plugins/bp-translate/

    Includes a multilingual page/post capability for blogs (based on qTranslate), a po/mo editor (based on Codestyling Localization), and a slew of ajax functions for translating BuddyPress core component user interaction through Google Translate on the fly.

    Very little support will be offered for this plugin, so use at your own risk. It’s held together with duct tape and glue, so parts may be loose or totally broken for you.

    #55118
    danbpfr
    Participant

    flyout menu problem is solved.

    Was a f… folder permission…argh…

    #55108
    danbpfr
    Participant

    Thxs !

    no it’s not a big issue, just a important little detail as any other usability indication – not all site admin read and understand correctly english warnings or message. But you’re right, it’s not a big issue.

    I hope you find the time to take a look for the variable problem.

    If you know about css problems, i also have trouble with the flyout part of the ‘MyBlog’ menu (is not appearing)

    Cheers !

    #7217

    For plugin authors, it will be easier for your audience if you localize your plugins. This means more than just wrapping text in “__” and “_e” functions.

    1. You need a directory to put your po/mo files, preferably wp-content/plugins/your-plugin/languages/.

      You also need to make sure all of your plugin files exist within the same root folder and not have one go in /wp-content/plugins/ and the rest within /wp-content/plugins/your-plugin/.

      Why?

      For those of us that localize your files with a Po/mo editor, the file outside of the folder is missed in the scan, and those strings aren’t added to the translatable strings.

    2. You need to make sure you have your own textdomain and not rely on BuddyPress’s or WordPress’s.

      __( 'Title of page', 'your-own-text-domain' );

      Why?

      Because when theme authors want to use your plugin, they will need to know which translation files to edit to output the desired text without modifying your plugin to pieces.

    3. Be sure to include your language files gracefully. Use a method like…
      function bp_load_your_plugin_textdomain() {
      $locale = apply_filters( 'bp_load_your_plugin_textdomain', get_locale() );
      $mofile = WP_PLUGIN_DIR . "/bp-your-plugin/languages/bp-your-plugin-$locale.mo";
      if ( file_exists( $mofile ) )
      load_textdomain( 'bp-your-plugin', $mofile );
      }
      add_action ( 'plugins_loaded', 'bp_load_your_plugin_textdomain', 9 );

      Why?

      Because otherwise your translations will never load, or they will load out of order with the other plugins and cause things to get prematurely loaded that shouldn’t be.

    In all honestly very few, if any, plugins currently handle localization correctly. Even outside of the BuddyPress world there are thousands of plugins that are English only without a method to localize them properly.

    Taking the steps mentioned above will really help widen the audience of your plugin, and make sure that your users are able to translate and modify the verbiage it uses without hacking the core.

    #54940

    In reply to: Two Languages

    Bowe
    Participant
    #54880
    Paul Wong-Gibbs
    Keymaster

    The text “The default theme for BuddyPress” cannot be translated as it is in a .css file. As only the site administrator will see that text when they activate the theme, is it a big issue? The other text here is part of WordPress.

    The wrong path thing is more interesting and there are some other forum posts here with that problem. I don’t know when I will get time to look into it so maybe someone else can help.

    #54853
    Paul Wong-Gibbs
    Keymaster

    Hi

    I’ll check this out after work.

    danbpfr
    Participant

    Hi DJPaul,

    here i am with a discussion you proposed here:

    http://trac.buddypress.org/ticket/1202

    A missing translation has nothing to do with misconfigurtion i think. And the indicated words are not translated.

    The variable %2$s shows a wrong path, but shows something. And despite of what is written, my template is coming from the right place.

    Go to view yourself and explain me what could be wrong. I’m very interested ! ;-)

    http://buddypress-fr.net/bpdemo/

    #54728

    In reply to: BuddyPress i18n Topics

    I’m currently working on a user language setting for BuddyPress that will take on not just user settings but assist in translation for user to user interaction. There are lots of places where BuddyPress might not be completely internationalized, and the most likely cause is probably attributed to the developers and contributors so far being primarily native English speakers.

    It’s hard for us to test different languages since we don’t understand the languages we’re looking at or reading or what they’re supposed to look like. We’re relying on the qualified multilingual developers to help us track down and fix the areas that could use the attention.

    My current focus is on the English to Spanish side of this, with Portuguese next on the list. I’ve briefly tested the display of Chinese and French but admit that I understand those languages much much less.

    I read a few weeks back there’s a plugin out there that’s starting to help out with the translation and language barrier. I hope that as more and more people start using BuddyPress that more people also help contribute to internationalizing it.

    #54679

    In reply to: BuddyPress i18n Topics

    stripedsquirrel
    Participant

    Not sure if this needs a separate thread, but as it is connected to the original post:

    I have spanish speaking users and have uploaded the spanish Buddypress translations.

    However:

    – The buddybar follows the language settings of the blog it is on, not of the user that is logged in. Meaning that a Spanish speaker (with language settings -> Spanish on their settings) will see a nice Spanish buddybar when on their own blog, but when they go to an English blog (the main blog for example) then the buddybar turns to English, even though it is ‘their’ buddybar, with their blogs and links to their profile etc. Is this by design or a bug?

    As the community homepage is almost separate from the main blog, it should follow the user-set language as well when loaded.

    – As the translation is available, I think the language of the main blog/home theme should change according to the (logged in) user visiting it, else they are lost on the community homepage. However, currently it sticks strictly to the language settings of the main blog.

    update: just created ticket: https://trac.buddypress.org/ticket/1245 but would like to hear your thoughts on this as well.

    Cheers, Harry

    #54502
    r-a-y
    Keymaster

    Send Brent a message:

    https://buddypress.org/developers/westpointer/

    Although you should know that Brent is now helping Boone Gorges on another group forum notification plugin that already has translation support:

    http://dev.commons.gc.cuny.edu/2009/10/12/translate-group-forum-subscription-for-buddypress/

    #6991
    takuya
    Participant

    Time to time I post problems of BuddyPress not supporting i18n other than translation. There’re lots of limitations for non English users. For example, making group names in own language often returns 404, etc.

    Some moderators say they carefully watch this, but my other topics never get response from moderators or core developers. Maybe one is not enough to raise awareness and drive them to take actions.

    So anyone using BuddyPress other than English, please post your experiences, discuss, and find solutions together.

    #53964
    madloki
    Participant

    1): done with 1.1.1.

    5): Think its done

    ________

    7) Create new group works, but when the user add at step 4 an avatar bp brings this message on an blank page:

    (Link:http://test.de/members/admin/groups/create/step/group-avatar)

    Bist du sicher, dass du das tun möchtest?

    Bitte nochmal versuchen.

    Browser back > click on “next step” > same error.

    Browser back > click on “previous step” >bp site loads but without content at step 2

    The group is created with the avatar! Wrong link in the “step” buttons?

    Test on firefox > no problem! Think its only on ie!

    8) Create group headlines without translation

    9) Admin doesnt see invisible groups from other users. Not good, there is no control!

    lostdeviant
    Participant

    That was it! The conflict is with the qtranslate plugin. http://www.qianqin.de/qtranslate/

    I started a new thread in the qtranslate plugin forum to let the author know.

    It would be great if someone here could confirm it. This worries me since it was the only multilingual plugin that I could find that would work with MU.

    It puts language content in html language tags including titles. With that plugin off everything appears twice wherever I had added a translation.

    #52290

    In reply to: When comes the 1.1?

    Arturo
    Participant

    the week for the translations have been added? :)

    #52254
    Paul Wong-Gibbs
    Keymaster

    Please answer https://buddypress.org/forums/topic/when-asking-for-support

    Also, are you using a language translation on your site? If so, this particular bug has recently been fixed and will be in the next release of BP.

    #51742
    Mariusooms
    Participant

    No trac, but you can just send patches or code through my profile or irc. The svn at the moment is temporary until Erwin takes over again. I should note, that while testing is really appreciated and that you for sure can use the plugin as is, there is no guarantee that Erwin will actually use this code base and he could take a different direction all together. Just to disclaim on my part :) So, also new features will not be implemented as the base code first needs to be accepted.

    That being said. On what url or you missing icons? I might have completely overlooked it. I have gone through a LOT of code, so it easy to miss something. I’ll fix the translation as well. Thanks…

    I just set up a new event, and the issue with the location still exists

    This could be because you have upgraded? On a clean install I am pretty sure this is not the case, but I will verify later today.

    If you’re like me and really like customizing BuddyPress to fit your needs, then sometimes the built in BuddyPress verbiage might not fit for your particular website. Maybe you need to rename “Wire” to “Wall” or you don’t like that avatars are called “Avatars” and want to rename them “Profile Pictures,” well it’s actually way easier to do than you’d think and it doesn’t involve modifying ANY core files at all…

    If your sites native language is English, then in your bp-languages folder all you need is a buddypress-es_US.po file. Then, use your favorite po/mo editor to change the text that you want changed, save the file, and upload it to your site.

    Done.

    That’s right; WordPress, bbPress, and BuddyPress all allow you to do this. So if you don’t like some of the hard-coded verbiage that any of the platforms use, you can change it simply by modifying your own languages po/mo file.

    You could go nuts with this method, and create an English/Pig-latin translation. Klingon? Sure! Pirate English? Go right ahead! Start with English and change it up however you wish.

    #51017
    José M. Villar
    Participant

    @Korhan thanks for the warning. At the beginning I won´t have any member blogs, just the “main” one. My project will start with the latest news about the football team I support (like Feherbace !) and then evolve to a fan community with forum.

    That´s why it Facebook login will prove very useful

    Regarding ID, I don´t think I will implement it until they provide front-end translation, which is in their roadmap but with no ETA yet.

    @r-a-y thanx again

Viewing 25 results - 1,126 through 1,150 (of 1,381 total)
Skip to toolbar