[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Kwave, translated screenshots
From:       Chusslove Illich <caslav.ilic () gmx ! net>
Date:       2015-02-25 9:12:15
Message-ID: 201502251012.17912.caslav.ilic () gmx ! net
[Download RAW message or body]


>> [: Chusslove Illich :]
>> [...] the program maintainer commits localized screenshots not into the
>> program repository, but into the appropriate location in the Subversion
>> localization repository. Here that would be
>> trunk/l10n-kde4/<lang>/docs/kdereview/kwave/.
>
> [: Thomas Eschenbacher :]
> Yes, this is exactly the location that I thought about. So that means I
> have the permission to do that?

I would say yes, unless someone objects, in this thread.

>> In the manual workflow, translator looks into the second directory above
>> for original screenshots, makes localized ones, and puts them and commits
>> them into the first directory above.
>
> Ok, that means if someone sees that localized screenshots are already
> there (in trunk/l10n-kde4/<lang>/docs/kdereview/kwave/) and then does
> nothing, then everything would be fine.

It should be made explicit, by also having in there the file which lists the
automatically created screenshots. As I mentioned, to avoid confusion on
either side, this same list file should be present in both places: in the
original documentation directory and in the localized documentation
directories.

To make it general, I'd actually call this list file 'auto-generated'.

>> [...] But the translator does not see the normal screenshots from
>> program's .../doc/en, because populate_documentation.sh has somehow
>> mangled them upon download (replaced with dummy image, or overlayed with
>> note). [...]
>
> Well, that means changing some scripts of the KDE infrastructure.

Yes, and that is precisely what we should do. You can change it and test it:

  cd /some/random/place
  svn co svn+ssh://svn.kde.org/home/kde/trunk/l10n-kde4/scripts
  ./scripts/populate_documentation.sh kdereview

Afterwards I can test it too, and you can commit it.

> Just an idea: would "mangling the file name" also do the job (instead of
> mangling the content)? For example adding a prefix like "no-l18n-" to the
> filename?

Prefix no-i18n- has somewhat wrong semantics, "do not translate" rather than
"will be automatically generated".

I'm not sure which solution is best here. Options mentioned so far were: do
nothing (rely on presence of 'auto-generated' list file), prefix each
screenshot file name, replace each screenshot with dummy image, overlay
screenshot with note-image. I'd prefer the last solution, but it has the
downside that ImageMagick would have to be installed on translator's
machine.

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]