Krusader sourcecode script
Frank Schoolmeesters
After getting te Krusader sourcecode the Krusader i10n and Krusader
documentation is missing...
http://websvn.kde.org/trunk/extragear/utils/krusader/
$ svn co svn://anonsvn.kde.org/home/kde/trunk/extragear/utils/krusader/
Since the move of Krusader to SVN Extragear the Krusader source code
resides in different places:
- Krusader source code
- Krusader translated GUI languages (different location for every language)
- Krusader English documentation
- Krusader translated documentation (different location for every language)
I suppose we need a script to unite all Krusader code again on our
computer as it was before, and than compile the complete Krusader
source code.
Or how do other Extragear projects do handle this?
I suppose to update createdist.sh script for doing the job, or do we
create a new script?
Does someone has the time to create this script?
Krusader English documentation
http://websvn.kde.org/trunk/extragear/utils/doc/krusader/
Krusader i10n GUI:
Just one example of the Dutch translation:
http://websvn.kde.org/trunk/l10n-kde4/nl/messages/extragear-utils/krusader.po
In some cases there is also a desktop_extragear-utils_krusader.po file.
http://websvn.kde.org/trunk/l10n-kde4/nl/messages/extragear-utils/desktop_extragear-utils_krusader.po
Krusader i10n Handbook:
An example of the French Krusader handbook
http://websvn.kde.org/trunk/l10n-kde4/fr/docmessages/extragear-utils/
In some cases the translated docbook files are in SVN (German
example), but a usually they are not available, so they need to be
compiled
(merge the handbook po files into the original English docbook files,
to get the translated docbook files with "po2xml")
http://websvn.kde.org/trunk/l10n-kde4/de/docs/extragear-utils/krusader/
Thanks and bye,
Frank
Dirk Eschler
> Hi guys,
>
> After getting te Krusader sourcecode the Krusader i10n and Krusader
> documentation is missing...
> http://websvn.kde.org/trunk/extragear/utils/krusader/
> $ svn co svn://anonsvn.kde.org/home/kde/trunk/extragear/utils/krusader/
>
> Since the move of Krusader to SVN Extragear the Krusader source code
> resides in different places:
> - Krusader source code
> - Krusader translated GUI languages (different location for every language)
> - Krusader English documentation
> - Krusader translated documentation (different location for every language)
> I suppose we need a script to unite all Krusader code again on our
> computer as it was before, and than compile the complete Krusader
> source code.
> Or how do other Extragear projects do handle this?
> I suppose to update createdist.sh script for doing the job, or do we
> create a new script?
> Does someone has the time to create this script?
Hi Frank,
there's already a script in the KDE repository. I've documented how to use it
on the new website (http://django.krusader.org/downloads/krusader/devel/). As
the site is still password protected, here's how you get started:
$ svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk/scripts/createtarball
$ cd createtarball
$ ./create_tarball.rb -n -a krusader -v svn`date +%Y%m%d`
bye,
Dirk
--
Dirk Eschler <esc...@gmail.com>
http://www.krusader.org
Frank Schoolmeesters
Thanks!
It works great.
I have add an announcement on the current website.
http://www.krusader.org/phpBB/viewtopic.php?t=2315
btw.
Currently it contains 100% translated Swedish and Ukrainian handbook !
and 29 GUI translations.
I'm not sure why some other translated handbooks (e.g. French, German,
Russian) don't show up, but maybe they only show up when they are 100%
translated.
Thanks a lot and bye,
Frank
Dirk Eschler
> I have add an announcement on the current website.
> http://www.krusader.org/phpBB/viewtopic.php?t=2315
Just a remark regarding the version number in the announcement. Please don't
use version numbers like this for trunk, it leads to several problems:
1.) It's confusing when users say they are using version x.y, but that version
is in fact an unreleased svn version.
2.) The plan was to make a quick 2.0.1 release with updated translations. Now
2.1.0-svn > 2.0.1 if you compare them programmatically.
When i refer to versions in the code, the svn version is simply "svn". If a
version is required, then the latest release plus a postfix svn can be used.
So for current trunk 2.0.0-svn would be appropriate (2.0.0-svn < 2.0.1).
Frank Schoolmeesters
Hi Dirk,
I changed it back to version 2.0.0 both the announcement as in SVN
(for the Krusader about box, see below).
For 2.0.1 , currently the KDE translators are translating the latest
krusader.pot from trunk, the po files are auto magically updated by a
script called "scripty" if the source files are changing. But I think
it's possible to create a "stable krusader.pot for 2.0.1" I guess, but
I don't know how.
Regarding the (translated) documentation in trunk: the handbook is
still version 2.0.0 with some updates for Extragear and some minor
fixes (but I have not added the new features of trunk yet). So the
trunk handbook can still be used for 2.0.1 (and for 2.0.0 stable)
I guess that current Krusader trunk probably requires beta releases
because of the new features, I suppose trunk will become version 2.1.0
at the moment we release a beta1.
I was able to create HTML tarballs of the Swedish and Ukrainian
handbook (Krusader-2.0.0) but I'm not sure yet in what category they
should be added at the Sourceforge mirrors. Any ideas?
Adding many translations in current "documentation" section will
create some chaos I think (to many files).
For the moment only HTML files are possible for translated handbooks,
PDF and the other formats are for the moment not possible because the
translated docbook files seems not be identical anymore compared to
the original English docbook files, so with many parsing errors as
result and no PDF.
Thanks a lot and bye,
Goodnight,
Frank
Thanks and bye,
Frank
---------- Forwarded message ----------
From: Frank Schoolmeesters <codek...@users.sourceforge.net>
Date: Sun, Aug 16, 2009 at 11:31 PM
Subject: extragear/utils/krusader
To: kde-c...@kde.org
SVN commit 1012127 by frankschoolmeesters:
Changed Krusader version number from 2.1.0 to 2.0.0 after discussion
at Krusader-devel
http://groups.google.com/group/krusader-devel/browse_thread/thread/a9c56139322dff
M +1 -1 CMakeLists.txt
--- trunk/extragear/utils/krusader/CMakeLists.txt #1012126:1012127
@@ -2,7 +2,7 @@
INCLUDE(CPack)
-set(VERSION "2.1.0-SVN" )
+set(VERSION "2.0.0-SVN" )
set(RELEASE_NAME "Rusty Clutch")
find_package(KDE4 REQUIRED)
Frank Schoolmeesters
FYI
I have just added a Swedish and Ukrainian HTML handbook for download,
after both translations did show up after running the createtarball script.
http://sourceforge.net/projects/krusader/files/
In a new "documentation-i10n-html" section.
krusader_handbook-2.0.0-html-SV-Swedish.tar.gz
krusader_handbook-2.0.0-html-UK-Ukrainian.tar.gz
Unfortunately I can currently only provide translated HTML handbooks,
other formats like PDF do fail to compile for the moment :(
Basically my script to generate all the various output formats gives a
lot of errors as output, I need to check this why.
It fails probably because the translated docbook-xml files do have
some "damaged tags" compared to the original English docbook-xml files
(after removing the English strings and replaced with the translated
strings, several docbook tags are "moved" as well. e.g. ">" to close
a tag is placed on a new line).
"meinproc4" that generates the HTML files seems to be more fault
tolerant than other parsers.
Kind regards,
Frank