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

List:       kde-i18n-doc
Subject:    Re: Impact of the gitlab migration to the i18n translation layout
From:       Guo Yunhe <i () guoyunhe ! me>
Date:       2020-05-22 6:49:53
Message-ID: M7v8Hxq--3-2 () guoyunhe ! me
[Download RAW message or body]

+1 for flat structure. Localization collaboration system like Weblate doesn't support \
sub-folder structure.

-- 
Guo Yunhe / @guoyunhe / guoyunhe.me



2020年5月16日 10:28 来自 xalba@clientes.euskaltel.es:

> 
> Hi everyone,
> 
> 
> 
> 
> 
> - When are you planing on making the change?
> 
> 
> 
> 
> 
> Current directory structure is helpful, it gives context to translators and helps \
> prioritise our efforts. 
> 
> 
> 
> 
> If the current physical structure is going to be removed. Is it possible to create \
> a list that displays files from the new  �flat � SVN structure as belonging to the \
> current categories, extragear-..., kdemultimedia, kdenetworks, ... 
> 
> 
> 
> 
> Something like a virtual view to show translatable files in the current categories \
> rather than in the real one. So we can see the real structure from SVN and the \
> virtual one with this  �list �. 
> 
> 
> 
> 
> Would it be possible to make statistics in  https://l10n.kde.org  show that virtual \
> view? 
> 
> 
> 
> I'm aware that this involves time and effort and I can't offer myself to make \
> something like this right now. But I really think it would be very helpful to keep \
> things clear to a wider audience. 
> 
> 
> 
> Cheers.
> 
> 
> 
> 
> 
> P.S.: I'm not sure to have made myself clear. I'm not a native English speaker.
> 
> 
> 
> ----- Jatorrizko mezua -----
> Nork: Luigi Toscano <luigi.toscano@tiscali.it>
> Data: 2020(e)ko Maiatzak 2(a), Larunbata, 22:56
> Gaia: Re: Impact of the gitlab migration to the i18n translation layout
> Nori: KDE i18n-doc <kde-i18n-doc@kde.org>
> 
> > Karl Ove Hufthammer ha scritto:
> > > Luigi Toscano skreiv 02.05.2020 16:38:
> > > > Please recheck the thread above, the tl;dr version is moving from:
> > > > 
> > > > <lang>
> > > > --> <messages/docmessages/docs/etc>
> > > > -----> <module>
> > > > --------> <po files of all repository in the module>
> > > > 
> > > > to:
> > > > 
> > > > <lang>
> > > > --> <messages/docmessages/docs/etc>
> > > > -----> <repository name>
> > > > --------> <po files of the repository>
> > > 
> > > Just to make sure I've understood it correctly. Is this an 
> > example of the new
> > > structure:
> > > 
> > > nn
> > > messages
> > > dolphin
> > > dolphin._desktop_.po
> > > dolphin.po
> > > dolphin_servicemenuinstaller.po
> > > org.kde.dolphin.appdata.po
> > > konsole
> > > konsole._desktop_.po
> > > konsole.po
> > > org.kde.konsole.appdata.po
> > > …
> > > 
> > > If so, that sounds fine. It's actually an improvement having 
> > all files for a
> > > single application together and separate from files from other 
> > applications.
> > Correct.
> > 
> > > 
> > > But it's bad that we can no longer see which files belong to, 
> > e.g., the
> > > ‘applications' bundle (they are highly visible, and one might 
> > want to
> > > prioritise the translation effort to make sure all of them are 
> > translated).
> > This is something which should be addressed somehow later, I 
> > concur, but not
> > now. We don't have a clear way how to track it at all, apart 
> > from a few
> > specific cases:
> > - Frameworks
> > - Plasma
> > 
> > But also for the application released as part of Release 
> > Service, even if we
> > group them together, it's not clear for example which of them 
> > are relevant to
> > which program.
> > 
> > And also for the extragear and playground bits, they may be 
> > actually split in
> > different repositories. Even KDevelop does not release all its 
> > modules together.
> > 
> > This is a different issue that should be solved in a more 
> > general way, not
> > just for translations.
> > 
> > > And it's a big problem if we can no longer see which files 
> > belong to the
> > > ‘playground-*' modules – so that we can ignore them! Having 
> > all playground
> > > files intermingled with files from normal, maintained 
> > applications will be a
> > > real pain. I would actually be happy with the playground 
> > translation files
> > > just being removed. We can always translate them when they go into
> > > ‘kdereview'. And perhaps this could force applications that 
> > (ab)use the
> > > playground module for something which really *is* maintained 
> > and regularly
> > > released, like ‘pkupdates' (the only example I know of), to 
> > finally move into
> > > (the equivalent of) ‘kdereview'.
> > 
> > Moving out the real unmaintained has been done over time and 
> > yes, there are
> > others which receive releases and they probably weren't reviewed 
> > officiallyyet (see also Yuri's answer).
> > 
> > It is worth nothing that there won't be any physical "move to 
> > kdereview"anymore, because the path on invent won't change, and 
> > we won't have modules
> > anymore on the i18n side, but this information will be tracked 
> > somewhere, I
> > guess (tbd).
> > 
> > I don't have a clear answer for this right now, sorry.
> > 
> > Ciao
> > -- 
> > Luigi
> 


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