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

List:       kde-i18n-doc
Subject:    Re: Non text resources l10n
From:       mvillarino <mvillarino () kde-espana ! es>
Date:       2013-01-29 22:23:55
Message-ID: CAGOKLE9=Q_Me6hO+qEQUDFzsmzLUgEuCXu-GWXreKcU72ay1rg () mail ! gmail ! com
[Download RAW message or body]

> I have now committed the script l10n-kde4/scripts/populate_source.sh, which
> uses parts of Scripty to check out and update all source repositories and
> arrange some convenient links (explained in script's header). I have also
> made some additions to l10n-support/scripts/lbundle-check.py to make proper
> use of the former. I will soon update the Techbase article, and in the
> meantime you could check if populate_source.sh works for you too (it should
> pull down ~10 GiB in trunk, and ~6 GiB in stable).

it seems that populate_source assumes that my
~/Translation/KDE/branches/stable/l10n-kde4 is under version control
.... and it is not. It is just a plain directory whose contents
(scripts/ templates/ and <lang>/) are versioned.

>
>> c) And a list of resources wich have an original counterpart but no
>> localized one ? (to the relevant language)
>
> There are two distinct cases here.
>
> The first case is where almost no resources need localization, so there is
> no way to have such a list automatically assembled. In principle, you spot
> a
> resource you want to localize, you add it, and then it gets tracked. This
> is
> the case that holds for almost everything that you would put in
> <lang>/data/.
>
> The second case is where almost all resources need localization. This is
> the
> case with documentation, where non-text resources are primarily
> screenshots.
> The Techbase article describes how to engage tracking of screenshots in
> documentation, so that when a new screenshot appears it gets automatically
> spotted and added to tracking. (But this section in the article needs
> updating too, to make use of populate_documentation.sh script's results.)
>
>> b) Once they are checked out. How can I get a thorough list of resources
>> whose original counterpart is newer than the localized one?
>
> By checking all l10n-track files for 'fuzzy' and 'obsolete' markers after
> lbundle-check.py has been run (obsolete means the original no longer
> exist -- maybe it was deleted, maybe it was moved). For example:
>
>   $ cd <branch>/l10n-kde4
>   $ lbundle-check.py <lang>
>   $ find <lang> -iname l10n-track | xargs grep '^fuzzy\|^obsolete'
>>list.out
[prev in list] [next in list] [prev in thread] [next in thread]