Meta Box

Contribution (pt_BR Translation) + Report on Non-Internationalized Strings

Support › General › Contribution (pt_BR Translation) + Report on Non-Internationalized Strings

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • November 7, 2025 at 7:48 PM #49296
    Jayron CastroJayron Castro
    Participant

    Hello Meta Box Support Team,

    I hope you are doing well.

    I am a Brazilian developer and an active user of Meta Box AIO in my projects. It's a fantastic tool and essential to my workflow.

    I recently spent considerable time fully translating the .po files for several Meta Box modules (including the Builder and other main addons) into Brazilian Portuguese (pt_BR).

    Currently, I have to manage these files manually in my /wp-content/languages/plugins/ folder, which becomes cumbersome to manage with each update.

    I would like to offer all my translation files for you to include in the official (core) distribution of the plugin. This would immensely help the thousands of developers in Brazil to have a 100% localized experience.

    To make it easy, you can download all my updated .po and .mo files here:

    Files

    Technical Note and Additional Help:

    I noticed that in the core plugin (meta-box/languages/), you seem to use a proprietary format (.l10n.php) instead of the standard .po/.mo files found in the addons (like the Builder). My files are in the standard .po format. If you need help converting them to the core's .l10n.php format, please let me know the process.

    More importantly: During the translation process, I also identified several strings (texts) in the UI that are not internationalized (they are "hardcoded" in English and do not appear in the .pot file).

    If the development team is interested, I would be happy to create a detailed, screen-by-screen report pointing out exactly where these strings are. This would allow you to make them translatable in future versions, further improving the plugin for a global audience.

    Please let me know if I can help with anything else.

    Thank you for your time and for the excellent product.

    November 9, 2025 at 10:14 PM #49303
    PeterPeter
    Moderator

    Hello Jayron,

    Thanks for your contribution.

    I will forward your translation files to the development team for inclusion in the plugin source code. Also, please share some texts that are not internationalized (translatable).

    November 11, 2025 at 11:08 AM #49312
    Anh TranAnh Tran
    Keymaster

    Hi Jayron,

    Thanks a lot for your contribution. We've updated the translations for the plugins that you sent.

    Regarding the translation format, since WordPress 6.5, it supports a new and more performant format for translation file .l10n.php instead of the old-fashioned .mo file. We use this format in our plugins to have a better performance. We also converted all of your translations to this new format, so you don't have to do that and send us again.

    Regarding translations for strings in JavaScript (which is used in UI), we have updated our .pot file. When you create a translation for it, please follow this step:

    - Create a .po file from .pot
    - Run the following command to create JSON file:

    cd /path/to/plugin/folder
wp i18n make-json languages --no-purge

    Unfortunately, I know the only way to do that is via wp-cli. I'm not sure if plugins like Loco Translate or WPML support creating JSON file for translating strings in JS.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.