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

List:       kde-i18n-doc
Subject:    Re: Running Lokalize from Pology
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2010-07-22 18:56:49
Message-ID: 201007221956.49412.aacid () kde ! org
[Download RAW message or body]

A Dijous, 22 de juliol de 2010, Alexander Potashev va escriure:
> 2010/7/22 Alexander Potashev <aspotashev@gmail.com>:
> > 22 июля 2010 г. 13:34 пользователь Yuri Chornoivan <yurchor@ukr.net> 
написал:
> >> Hi!
> >> 
> >> I have conducted some tests with Lokalize 1.1 and Pology from trunk and
> >> cannot confirm this problem (every change is clearly appears in
> >> stable).
> >> 
> >> Maybe Alexander can give a testcase that can be studied separately?
> > 
> > I can't reproduce this problem anymore, but I still don't know what
> > could cause it.
> 
> I have found the source of this problem: Lokalize does not backport
> changes to stable when I use a symlink to refer to the directory I
> want to scan with Pology.
> 
> For example, Lokalize project is configured to use these paths on my
> computer: /home/$USER/kde-full/kde/trunk/l10n-kde4/ru -- translations'
> root, /home/$USER/kde-full/kde/branches/stable/l10n-kde4/ru -- stable
> branch. But I also have a symlink ~/messages which points to
> kde-full/kde/trunk/l10n-kde4/ru/messages, and sometimes I use it to
> run Pology:
> posieve.py find-messages -smsgstr:'экспортирование'
> ~/messages/kdebase/ -slokalize

Might be worth filling a bug report in bugs.kde.org to make sure this one 
doesn't get forgotten.

Albert

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