[Pkg-giraffe-discuss] zarafa-webapp-files seems not completely translated in the UI
Carsten Schoenert
c.schoenert at t-online.de
Tue Dec 1 18:17:41 UTC 2015
Hello,
Am 30.11.2015 um 08:58 schrieb Guido Günther:
> We're at least lacking a build-dep on gettext:
>
> https://github.com/tijuca/zarafa-webapp/pull/2
>
> This is _not_ build-tested since the upstream branch seems broken at the
> moment:
>
> ...
> dpkg-source: warning: file zarafa-webapp/client/tinymce-plugins/powerpaste/langs/uk.js has no final newline (either original or modified version)
> dpkg-source: warning: file zarafa-webapp/client/tinymce-plugins/powerpaste/langs/zh_CN.js has no final newline (either original or modified version)
> dpkg-source: warning: file zarafa-webapp/client/tinymce-plugins/powerpaste/langs/zh_TW.js has no final newline (either original or modified version)
> dpkg-source: warning: file zarafa-webapp/client/zarafa/advancesearch/data/DateRangeFields.js has no final newline (either original or modified version)
> dpkg-source: warning: file zarafa-webapp/client/zarafa/core/data/ZarafaCustomEventDispatcher.js has no final newline (either original or modified version)
> dpkg-source: warning: file zarafa-webapp/version has no final newline (either original or modified version)
> dpkg-source: warning: file zarafa-webapp/version has no final newline (either original or modified version)
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b zarafa-webapp gave error exit status 2
>
> and there's no pristine-tar to create a md5 identical tarball. Could you
> have a look?
I've changed the gbp.conf to enable a pristine-tar commit while
git-buildpackage is running the import-orig task. For getting a
pristine-tar branch for the current version 2.1.1 I've reset the current
debian and upstream branch to be equal with the current version on
Alioth and run a new import of the upstream sources with all the related
local made patches.
@Guido
I cherry-picked your fix for debian/control.
I also added the changes from yesterday again to get a rebuild of the
*.mo files for zarafa-webapp-files. Looks now like this:
> language:
>
> msgfmt:
> [echo] Converting /build/zarafa-webapp-2.1.1/plugins/files/languages/de_DE.UTF-8/LC_MESSAGES/plugin_files.po to ${outfile}
> [exec] 119 translated messages.
>
> msgfmt:
> [echo] Converting /build/zarafa-webapp-2.1.1/plugins/files/languages/en_US.UTF-8/LC_MESSAGES/plugin_files.po to ${outfile}
> [exec] 113 translated messages.
>
> msgfmt:
> [echo] Converting /build/zarafa-webapp-2.1.1/plugins/files/languages/fr_FR.UTF-8/LC_MESSAGES/plugin_files.po to ${outfile}
> [exec] 105 translated messages, 1 fuzzy translation, 7 untranslated messages.
>
> msgfmt:
> [echo] Converting /build/zarafa-webapp-2.1.1/plugins/files/languages/nl_NL.UTF-8/LC_MESSAGES/plugin_files.po to ${outfile}
> [exec] 105 translated messages, 1 fuzzy translation, 7 untranslated messages.
>
> msgfmt:
> [echo] Converting /build/zarafa-webapp-2.1.1/plugins/files/languages/zh_TW.UTF-8/LC_MESSAGES/plugin_files.po to ${outfile}
> [exec] 103 translated messages, 1 fuzzy translation, 9 untranslated messages.
> [copy] Copying 10 files to /build/zarafa-webapp-2.1.1/deploy/plugins/files
>
> deploy:
> [copy] Copying 310 files to /build/zarafa-webapp-2.1.1/deploy/plugins/files
>
> BUILD SUCCESSFUL
> Total time: 1 minute 26 seconds
But the UI doesn't use the locales yet. I believe there must be
something broken inside the PHP files because the *.mo files are
ignored. Jelle, can you please take a look at this if possible.
I forced pushed the whole thing once again on Github.
--
Regards
Carsten Schoenert
More information about the Pkg-giraffe-discuss
mailing list