headers
Daniel Leidert | 1 Feb 2009 15:33
Picon

Re: contributions to the language definition files

Am Mittwoch, den 28.01.2009, 13:06 +0200 schrieb alex bodnaru:

> i can report to have successfully scripted the svn co of bluefish-unstable,
> debian packaging and building of deb packages.
> 
> the script is attached.

I developed it a bit further. Would you mind distributing this script
under the GPL version 2 (or higher) like bluefish itself as part of our
SVN?

> please note it contains a small patch to Makefile.am,
> needed for make dist to work.

intltoolize should copy/link these files into the source tree. Maybe
intltool changed its behaviour recently? Which version do you use?

> daniel, i have opted for co instead of extract, in order to really maintain the
> local svn and not to download everything, every time.

No problem. I attached the result to this mail. Please test it from your
bluefish checkout. The `set -ex' is for testing atm. The -x can be
removed later.

I removed the co-stuff for the moment, because if we distribute the
script with the SVN, it is not necessary and the script can be run from
the checked out copy.

Regards, Daniel
(Continue reading)

Permalink | Reply | 5 comments |
headers
Daniel Leidert | 1 Feb 2009 15:45
Picon

Re: contributions to the language definition files

Am Sonntag, den 01.02.2009, 15:33 +0100 schrieb Daniel Leidert:
> Am Mittwoch, den 28.01.2009, 13:06 +0200 schrieb alex bodnaru:
> 
> > i can report to have successfully scripted the svn co of bluefish-unstable,
> > debian packaging and building of deb packages.
> > 
> > the script is attached.
> 
> I developed it a bit further. Would you mind distributing this script
> under the GPL version 2 (or higher) like bluefish itself as part of our
> SVN?

Ah, I forgot something. There is a small bug. The computed package
version is 1.3.3+svnXXXX atm, but it must be 1.3.2+svnXXXX or
1.3.3~svnXXXX as 1.3.3 is not yet released.

This needs to be fixed.

Regards, Daniel
Permalink | Reply | 1 comment |
headers
alex bodnaru | 1 Feb 2009 15:55
Picon
Gravatar

Re: contributions to the language definition files


hi daniel,

i'm just browsing your previous mail.

not checked it deep enough yet, but i aggree to your initiatives. i'll answer
that too, soon.

Daniel Leidert wrote:
> Am Sonntag, den 01.02.2009, 15:33 +0100 schrieb Daniel Leidert:
>> Am Mittwoch, den 28.01.2009, 13:06 +0200 schrieb alex bodnaru:
>>
>>> i can report to have successfully scripted the svn co of bluefish-unstable,
>>> debian packaging and building of deb packages.
>>>
>>> the script is attached.
>> I developed it a bit further. Would you mind distributing this script
>> under the GPL version 2 (or higher) like bluefish itself as part of our
>> SVN?
> 
i'd be glad to. but please put it on the webpage, so it could be used to build
the packages. otherwise, it's like a key to a box distributed inside the box.

> Ah, I forgot something. There is a small bug. The computed package
> version is 1.3.3+svnXXXX atm, but it must be 1.3.2+svnXXXX or
> 1.3.3~svnXXXX as 1.3.3 is not yet released.
> 
> This needs to be fixed.
> 
that's what the program would read, indeed. ;)
(Continue reading)

Permalink | Reply | 0 comments |
headers
alex bodnaru | 1 Feb 2009 16:47
Picon
Gravatar

Re: contributions to the language definition files


hi daniel,

you have improved the script indeed, and made it look professional, but i have a
few techincal drawbacks:

you didn't let me co, so i had to use -b with dch, to use my older version than
the top of debian/changelog.
i really had to use find to find that tmp directory, inside the svn directory.
your message should point better at that location. since everything happen
inside our svn copy, especially since our copy is not being co/export right now,
it would really be good to keep a version of this script inside the svn-root,
that should not need the SVN_DIR env.
in case the debian building process is not interesting at all, but only the
debs, the building dir and any unrelated files should be removed in the process.
experimental is the right place for experimental software, but all personally
managed repositories, and especially mentors, use the unstable suite by default.
besides, bluefish-unstable has been specifically designed to be working, and to
wokd by the side of bluefish. thus i'd opt of unstable as default, and unlimited
configurability. ;)
instead of a tmpdir, wouldn't it be nicer to have a directory named using the
version of our build?

best regards,
alex

Daniel Leidert wrote:
> Am Mittwoch, den 28.01.2009, 13:06 +0200 schrieb alex bodnaru:
> 
>> i can report to have successfully scripted the svn co of bluefish-unstable,
(Continue reading)

Permalink | Reply | 2 comments |
headers
alex bodnaru | 1 Feb 2009 17:14
Picon
Gravatar

a few glitches


hi olivier, friends,

working with bluefish-unstable is a very pleasurable experience.

however i'm a conservative user, i could pinpoint a few small problems.

1. queerly, there are a few dialogs right of help.

2. when i'm putting the string that ends a foldable region, the L appears on the
left bar, but without the +- box on top of it.

3. generally, bflang format is not well known, and i feel i'm not allways
guessing right especially at regexp syntax, which understand is not standard.

4. this is legacy from bf-1.0.7: keywords ending at end of line are not been
recognized unless i force that by f5 or by appending and removing a space.

5. i don't remember exactly where i found s feature to insert attributes, like
style, in the html tag at cursor. the tag has been successfully altered, but an
unneeded neline was appended to it.

would it be possible to record a sequence of keys i've pressed? that's not for a
macro recorder, but for bug reproduction.

best regards,
alex
Permalink | Reply | 0 comments |
headers
Daniel Leidert | 1 Feb 2009 17:44
Picon

Re: contributions to the language definition files

Am Sonntag, den 01.02.2009, 17:47 +0200 schrieb alex bodnaru:

[..]
> you didn't let me co, so i had to use -b with dch, to use my older version than
> the top of debian/changelog.

You can adjust the script for your needs. Just add something like this
after SVN_DIR and SVN_URL declaration:

svn co ${SVN_URL}/trunk/bluefish ${SVN_DIR}

then after building the packages, simply copy them to somewhere else:

cp *.deb /your/preferred/place

and at the end, remove the subversion directory:

rm -rf ${SVN_DIR}

That's pretty easy. Then run this script via:

sh make-deb.sh SVN_DIR=/your/place

But this is not, how I want it to work from within the checked out
source.

[..]
> in case the debian building process is not interesting at all, but only the
> debs, the building dir and any unrelated files should be removed in the process.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Esfinge | 1 Feb 2009 17:49
Picon

about pt-br translation

I'm willing to update the pt-br (pt_BR.po) translation but never did
software translation before, so looking for instructions on bluefish
manual got me to this page:

http://bluefish.openoffice.nl/manual/ch12s08.html

These information are still valid? If not, please give me the right way :)

The pt_BR.po file shows in the heading: "PO-Revision-Date: 2004-12-09
09:53-0300\n" as of svn revision: 4502, and it lacks most of the new
Bluefish strings.
If my contribution are appreciated i will be happy to do it.

Thanks in advance.
Permalink | Reply | 3 comments |
headers
Daniel Leidert | 1 Feb 2009 18:04
Picon

Re: about pt-br translation

Am Sonntag, den 01.02.2009, 13:49 -0300 schrieb Esfinge:

> I'm willing to update the pt-br (pt_BR.po) translation but never did
> software translation before, so looking for instructions on bluefish
> manual got me to this page:
> 
> http://bluefish.openoffice.nl/manual/ch12s08.html
> 
> These information are still valid? If not, please give me the right way :)

These information are still valid except that we are using subversion
atm and that there are several .po files per language - one for the main
application in po/ and one per plugin in src/plugin*/po/.

If you need some more technical details, you can read:
http://www.gnu.org/software/gettext/manual/gettext.html#PO-Files
http://www.gnu.org/software/gettext/manual/gettext.html#Translators

There are also some editors specialized to po-file editing - poedit,
gtranslator, kbabel - bluefish can of course be used too :)

> The pt_BR.po file shows in the heading: "PO-Revision-Date: 2004-12-09
> 09:53-0300\n" as of svn revision: 4502, and it lacks most of the new
> Bluefish strings.
> If my contribution are appreciated i will be happy to do it.

We appreciate any help/contribution. It is usually considered "good
behaviour" to contact the previous translator too. There are usually
also language teams, which may help you to find a good entry point to
translation.
(Continue reading)

Permalink | Reply | 2 comments |
headers
alex bodnaru | 1 Feb 2009 18:42
Picon
Gravatar

Re: contributions to the language definition files


Daniel Leidert wrote:
> Am Sonntag, den 01.02.2009, 17:47 +0200 schrieb alex bodnaru:
> 
> [..]
>> you didn't let me co, so i had to use -b with dch, to use my older version than
>> the top of debian/changelog.
> 
seriously, if you let the user use his own svn check-out, he may have' like me'
an older version to insert in debian/changelog. hence -b. not needed for co in
the process.
> You can adjust the script for your needs. Just add something like this
> after SVN_DIR and SVN_URL declaration:
> 
> svn co ${SVN_URL}/trunk/bluefish ${SVN_DIR}
> 
> then after building the packages, simply copy them to somewhere else:
> 
> cp *.deb /your/preferred/place
> 
> and at the end, remove the subversion directory:
> 
> rm -rf ${SVN_DIR}
> 
i just thought the co would be a proper part of a first time impact with
bf-unstable downloading.
in my script, i could add rm -rf $svndir $pkgdir and could suppress the creation
of source package, an hop: the debs are at `pwd`.
> That's pretty easy. Then run this script via:
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jim Hayward | 1 Feb 2009 20:11

Re: about pt-br translation

On Sun, 2009-02-01 at 18:04 +0100, Daniel Leidert wrote:
> 
> These information are still valid except that we are using subversion
> atm and that there are several .po files per language - one for the main
> application in po/ and one per plugin in src/plugin*/po/.

All of the application PO files were out of date. Fixed in SVN revision
4516. The plugin PO files were already up to date.

Regards,
	Jim H
Permalink | Reply | 1 comment |

Gmane