#5925: buddypress.pot issue
--------------------------+-----------------------------
Reporter: danbp | Owner:
Type: defect (bug) | Status: new
Priority: high | Milestone: Awaiting Review
Component: i18n | Version: 2.1
Severity: major | Keywords:
--------------------------+-----------------------------
several issues remains with the 2.1 pot file.
- some strings are untranslated despite the translation exist (from a
previous version for example)
- when you create a new pot file from scratch with poEdit, using all
possible keywords, you get an incredible number of new strings concerning
bbpress.
This sounds like the whole plugin is reintroduced to BP.
- if you download
[https://downloads.wordpress.org/plugin/buddypress.2.1.zip/the zip] from
the wp repo, buddypress.pot is at the root of BP and if you read the
header, you see
{{{
# Copyright (C) 2014 The BuddyPress Community
# This file is distributed under the GPLv2 or later (license.txt).
msgid ""
msgstr ""
"Project-Id-Version: BuddyPress 2.1\n"
"Report-Msgid-Bugs-To: https://buddypress.trac.wordpress.org\n"
"POT-Creation-Date: 2014-09-18 18:01:13+00:00\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2014-MO-DA HO:MI+ZONE\n"
"Last-Translator: JOHN JAMES JACOBY <jjj at buddypress.org>\n"
"Language-Team: ENGLISH <jjj at buddypress.org>\n"
"X-Generator: grunt-wp-i18n 0.4.5\n"
}}}
Maybe correct, but unusual. '''Particulary''' if you compare this file
with the pot file actually in the tagged version (r9015), the header
contains
{{{
# Copyright (C) 2014 BuddyPress
# This file is distributed under the same license as the BuddyPress
package.
msgid ""
msgstr ""
"Project-Id-Version: BuddyPress \n"
"Report-Msgid-Bugs-To: http://wppolyglots.wordpress.com\n"
"POT-Creation-Date: 2014-09-14 11:30:39+00:00\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2014-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
}}}
This header is also correct, and '''in the form used with previous'''
versions.
The [https://buddypress.org/support/topic/buddypress-2-1-bp-
language/page/3/#post-203625/latest tip] to get a translation to work was
to merge the previous version with the new one.
This means to take the po from 2.02 and to update it from the new pot
coming with 2.1
Doing this generates untranslated strings. For example, the SWA page title
or the buddybar View menu or the swa default filter - everything -, yet
these are old !
If you update from source (a la poEdit) this pot file (coming with BP),
you receive 1144 new strings !
And now, if you update the 2.02 po file with this pot file you get 1327
new strings and 135 obsolete. By details you have a 2.1 transaltion
achieved to 50%, with 705 untranslated strings and 625 marked as fuzzy,
for a total string number of 2668 !
As reminder, the 2.0.2 version translated to 100% contains only 1476
strings.
If this can help, here the header informations i use for the fr_FR
translation.
{{{
msgid ""
msgstr ""
"Project-Id-Version: BuddyPress 2.0.2\n"
"POT-Creation-Date: 2014-10-03 13:57+0100\n"
"PO-Revision-Date: 2014-10-03 14:13+0100\n"
"Last-Translator: dan <danco38 at gmail.com>\n"
"Language-Team: danbp\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n > 1;\n"
"X-Generator: Poedit 1.5.7\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-Basepath: .\n"
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop:1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;esc_attr__;"
"esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n"
"X-Poedit-SearchPath-0: ..\n"
}}}
The most important information is the keyword list:
{{{
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop:1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;esc_attr__;"
"esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n"
}}}
Aside these issues, another problem for custom translation is the
glotpress po file.
When you upload the po file, you get a header without any information. But
a po file without a keywords list used by the software is a little more
tendencious.
To resume the situation for 2.1, we have a wrong pot file shipped with BP
and a uncomplete translation on glotpress who can't fit with 2.1... where
2.1 is not avaible in the project !
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5925>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac