Re: transifex committing wrong translations to elfutils
by Noriko Mizumoto
Roland McGrath さんは書きました:
>> msgid: '%' is only meaningful with the 'x' option
>>
>
> That was indeed a typo in our format string (meant to be %c).
> Thanks for catching that! I've fixed it in the latest git tree
> on our fedorahosted repo.
>
Thanks! I see now fixed PO.
> It would be nice if the canonical po/Makefile's "make check"
> would do something that would catch those msgfmt errors in the
> package build before it gets to the translators.
>
I am not sure, but l10n infra team (Dimitris, Asgeir, etc) may be able
to have some idea on this?
noriko
14 years, 7 months
new release of lohit-fonts 2.4.3
by pravin.d.s@gmail.com
Hi All,
Today i have build new tarball of lohit-fonts-2.4.3,There are major
changes from a releasing point of view.
Changes are as follows:
now lohit is release as 2 tarball for each language:
example for hindi:
1) lohit-hindi-2.4.3.tar.gz
This is source tarball, it contains .sfd as well generete.pe for generating
ttf file from source.
2) lohit-hindi-ttf-2.4.3.tar.gz
It is binary tarball, it contains .ttf file, so if anyone want to use binary
file directly he can use this.
Now in new release there are 32 tarballs 2 for each language(total 16
langauge)
also there is svnsnap release lohit-fonts-svnsnap-20090909.tar.gz, see
http://pravins.fedorapeople.org/lohit/ for other files
advantage of doing this is that in future if there is some changes in Tamil,
we can release only Tamil tar ball,
so there is no need to build other font unnecessary.
Thanks & Regards,
----------------------
Pravin Satpute
14 years, 7 months
transifex committing wrong translations to elfutils
by Petr Machata
Hi,
I don't know who's the culprit, but for some reason we are getting
translations of wrong project in elfutils. In particular, Spanish and
Italian were thus damages in commits [1] and [2], respectively. The
string committed don't belong to elfutils, but to two different projects.
I sent messages to respective localization teams, but perhaps the tool
that the translators use could do some sort of validity checking. E.g.
comparing the strings that should be committed to po/*.pot, and issue a
warning, or outright deny the commit if "suspicious amount" of strings
changes (that is original strings, not localized ones)? I would like to
state that I have only a very vague idea how the whole localization
process works, so this proposal may not in fact be possible.
Hmm, should I file a ticket about this? If yes, where?
Please be sure to CC me if replying, I'm not a member of the list.
Thanks,
PM
[1] http://tinyurl.com/mhtlew SHA1 5658eef4d3
[2] http://tinyurl.com/llfzk8 SHA1 589b3d302f
14 years, 7 months