[Kde-scm-interest] scripty questions

[Chani]

>
> > > > is merge.sh obsolete? can it be deleted?
> > > > repack-pot.pl isn't used right now; can it be deleted?
> > >
> > > repack-pot.pl is used in update_translations and this is part of
> > > scripty
> >
> > no it's not. update_translations passes it off to extract-messages, and
> > the code that used to use it there is commented out.
>
> Right, but why would you want to delete it? It's a script that does what it
> says and it can be useful.

well, it's in svn so it wouldn't be gone forever. if it's useful then by all 
means keep it, but it looked like some useless leftover that could be cleaned 
up. :)

>
> > > > ? why's there a copy of it in l10n-support
> > > > too?
> > >
> > > Because l10n-support is some kind of experiment for improving l10n and
> > > needs it
> > >
> > > > why does process_orphans.txt look like nothing has ever been deleted
> > > > from it?
> > >
> > > Because it was not
> >
> > why? just because nobody bothered? it wouldn't break anything to get rid
> > of all that old stuff? :)
>
> Because gives us a quick access to history of what was moved where, what
> was removed, etc and regularly teams screw up and commit old files and
> looking here it's easy way to move where it belongs.

mmkay :)

>
> > > > what's lbundle-check.py?
> > >
> > > scripty does not touch l10n-support at all, forget about it
> >
> > just because it's not part of scripty, doesn't necessarily mean it's
> > irrelevant for switching modules to git. becsides, I'm curious. :)
>
> l10n-support is Chusslove realm, ask him, no idea if he is on this list, i
> already told you on IRC that kde-i18n-doc list would have been a much
> better list for these questions since it's where the people with i18n
> knowledge is.

yeah, I need to get around to subscribing...

> > > > now, the problem: documentation/ is full of svn externals. absolutely
> > > > full of them.
> > > > if this folder is only used by scripts (and people running the
> > > > scripts who know what they're doing), then I should be able to write
> > > > a script to fetch the code from git. but if translators expect this
> > > > folder to be full of docbook files when checked out, that could be
> > > > bad, when half those files are in git. (btw, only a couple of the
> > > > externals successfully checked out when I tried anyways. svn: No such
> > > > revision 971664 )
> > >
> > > update_xml needs those files to be there.
> > >
> > > > the best thing I can think of in that case is asking the translators
> > > > to run a script to update documentation/ after they svn up (or
> > > > checkout). which isn't ideal.
> > > > so, do translators need it?
> > >
> > > Yes, as said update_xml needs it
> >
> > so... regular translators are running update_xml... why?
>
> To generate the docbook files that are real documentation, documentation po
> files are just there to ease translators life and are not used at all after
> update_xml is called
>
> > to see what the
> > translated docbook looks like all put together instead of as little
> > fragments in a po file?
>
> To see the docbook "compiles" the fact that docbook is a "relatively
> complex" language makes translators generate po files that when merged back
> to docbook don't "compile"
>

yeah, I heard more about this on irc... sounds unfun.

-- 
This message brought to you by eevil bananas and the number 3.
www.chani3.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090524/9a6e4503/attachment.sig