From christoph-schaefer at gmx.de  Wed Oct  1 05:32:53 2014
From: christoph-schaefer at gmx.de (=?UTF-8?Q?=22Christoph_Sch=C3=A4fer=22?=)
Date: Wed, 1 Oct 2014 07:32:53 +0200
Subject: [scribus-dev] correction needed recent commit r19543
In-Reply-To: <542B1016.4040809@scribus.info>
References: <CAAt0FRhxDDUTFTeebqKrBmd2nATXLokVDEGhYZ+CCj-kjF0x5Q@mail.gmail.com>
 <trinity-f498aaf0-ed15-4290-8d30-0b25d6cbe9b3-1412059596473@3capp-gmx-bs58>
 <CAAt0FRjMFQaK+oOZn8ap+CoZ0Li1wRTFXM+owv-pJ9m2MyX4NQ@mail.gmail.com>,
 <542B1016.4040809@scribus.info>
Message-ID: <trinity-cf779fd1-4aac-47a0-b286-ea6a15eec78b-1412141573749@3capp-gmx-bs39>



> Gesendet: Dienstag, 30. September 2014 um 22:18 Uhr
> Von: "Craig Bradney" <cbradney at scribus.info>
> An: scribus-dev at lists.scribus.net
> Betreff: Re: [scribus-dev] correction needed recent commit r19543
>
> On 30/09/2014 8:57 pm, Kunda Loves Scribus wrote:
> > On Tue, Sep 30, 2014 at 1:46 AM, "Christoph Sch?fer" <christoph-schaefer at gmx.de
> > <mailto:christoph-schaefer at gmx.de>> wrote:
> > 
> >      
> >     And? Neither the bugtracker nor the commit list need to follow the rules of bureaucracy.
> >     Moreover, the developer mailing list and Mantis do record any changes reliably (let alone svn).
> >     Please don't try to turn Scribus into the equivalent of a public agency with obligatory,
> >     voluminous and unnecessary paper trails.
> >      
> >     You can be pedantic when it comes to Scribus itself, or licensing issues (I'm infamous for doing
> >     so), but we cannot waste our time by introducing bureaucratic rules that may suffocate development.
> >      
> >     Also: Please use Plain Text, not HTML, for your ML postings.
> >      
> >     Kind regards,
> >      
> >     Christoph
> >     *Gesendet:* Dienstag, 30. September 2014 um 00:18 Uhr
> >     *Von:* "Kunda Loves Scribus" <scribus.user at gmail.com <mailto:scribus.user at gmail.com>>
> >     *An:* "Scribus Dev Mailing List" <scribus-dev at lists.scribus.net
> >     <mailto:scribus-dev at lists.scribus.net>>
> >     *Betreff:* [scribus-dev] correction needed recent commit r19543
> >     Commit message for r19543 is actually #12733 and not #2733
> >      
> >     /Kunda
> >     _______________________________________________ scribus-dev mailing list
> >     scribus-dev at lists.scribus.net <mailto:scribus-dev at lists.scribus.net>
> >     http://lists.scribus.net/mailman/listinfo/scribus-dev
> > 
> > Hi Christoph,
> > 
> > re: Plain text
> > I'm usually thinking about such things. Honestly, I'm not fully used to using this type of ML
> > technology. Sometimes switching from between different types of lists that exist today can cause
> > some forgetfulness. These are things that I try to pay attention to as best as possible as well. As
> > for responding in pure text I need to examine gmail further to see if I can specify that. Will look
> > in to it. I'm pretty sure that reply to this email will _not_ send it in plain text. For just this
> > moment forgive me for doing so. 
> > 
> > re: bureaucracy
> > I see. Given your response I can feel that this is an important issue for you and therefore I'm
> > noting your position on it for future considerations. Though I am pretty certain that my intention
> > for pointing out what I was pointing out was purely out of 'future friendly' concern. In other
> > words, to be able to correctly and efficiently track down the correct revisions based on the commit
> > message. Also, I was following the intelligent behavior that has been modeled and that I've learned
> > to appreciate existing in the SVN commit process. 
> > 
> > Just to be clear, I have no intention of asserting my ego, quirks, or privileges on anybody let
> > alone 'suffocate development' or introduce unneeded protocols. I, just like all of us who
> > participate, want to see Scribus succeed. 
> > 
> > Now if you see behavior that you'd prefer me to reflect on and change I would be willing to listen
> > and examine your feedback. 
> > 
> > I am in agreement with you to keep Scribus as free as possible from bureaucracy. 
> > 
> > Thank you,
> > /Kunda 
> 
> Kunda - Please ignore Christoph in this case. :)
> 
> Christoph - lay off the war path :)


Im not on a war path, but I must admit I love to fight government and corporate bureaucracies -- remember that I'm living in the land of red tape. If in doubt, look at this Australian's humourous description: http://www.livhambrett.com/everything-i-know-about-germany-germans/what-i-know-about-germans/ (#80 and 81, both very true) ;) When I smell demands for an action that doesn't make sense, but simply serves bureaucratic pedantry, all alarm bells start ringing. Thus, demanding that a typo in a commit message must be corrected automatically triggers a NO in super-sized capital letters, bold and italics ;)


No need to worry, though. I'm still relaxed and appreciate Kunda's work :)


Christoph


From scribus.user at gmail.com  Wed Oct  1 14:33:33 2014
From: scribus.user at gmail.com (Kunda Loves Scribus)
Date: Wed, 1 Oct 2014 09:33:33 -0500
Subject: [scribus-dev] correction needed recent commit r19543
In-Reply-To: <trinity-cf779fd1-4aac-47a0-b286-ea6a15eec78b-1412141573749@3capp-gmx-bs39>
References: <CAAt0FRhxDDUTFTeebqKrBmd2nATXLokVDEGhYZ+CCj-kjF0x5Q@mail.gmail.com>
 <trinity-f498aaf0-ed15-4290-8d30-0b25d6cbe9b3-1412059596473@3capp-gmx-bs58>
 <CAAt0FRjMFQaK+oOZn8ap+CoZ0Li1wRTFXM+owv-pJ9m2MyX4NQ@mail.gmail.com>
 <542B1016.4040809@scribus.info>
 <trinity-cf779fd1-4aac-47a0-b286-ea6a15eec78b-1412141573749@3capp-gmx-bs39>
Message-ID: <CAAt0FRgW_pWfCbVDZyKonyJekQd+o2arg9J2=0n4c4BxdNuexQ@mail.gmail.com>

On Wed, Oct 1, 2014 at 12:32 AM, "Christoph Sch?fer" <
christoph-schaefer at gmx.de> wrote:

>
>
> > Gesendet: Dienstag, 30. September 2014 um 22:18 Uhr
> > Von: "Craig Bradney" <cbradney at scribus.info>
> > An: scribus-dev at lists.scribus.net
> > Betreff: Re: [scribus-dev] correction needed recent commit r19543
> >
> > On 30/09/2014 8:57 pm, Kunda Loves Scribus wrote:
> > > On Tue, Sep 30, 2014 at 1:46 AM, "Christoph Sch?fer" <
> christoph-schaefer at gmx.de
> > > <mailto:christoph-schaefer at gmx.de>> wrote:
> > >
> > >
> > >     And? Neither the bugtracker nor the commit list need to follow the
> rules of bureaucracy.
> > >     Moreover, the developer mailing list and Mantis do record any
> changes reliably (let alone svn).
> > >     Please don't try to turn Scribus into the equivalent of a public
> agency with obligatory,
> > >     voluminous and unnecessary paper trails.
> > >
> > >     You can be pedantic when it comes to Scribus itself, or licensing
> issues (I'm infamous for doing
> > >     so), but we cannot waste our time by introducing bureaucratic
> rules that may suffocate development.
> > >
> > >     Also: Please use Plain Text, not HTML, for your ML postings.
> > >
> > >     Kind regards,
> > >
> > >     Christoph
> > >     *Gesendet:* Dienstag, 30. September 2014 um 00:18 Uhr
> > >     *Von:* "Kunda Loves Scribus" <scribus.user at gmail.com <mailto:
> scribus.user at gmail.com>>
> > >     *An:* "Scribus Dev Mailing List" <scribus-dev at lists.scribus.net
> > >     <mailto:scribus-dev at lists.scribus.net>>
> > >     *Betreff:* [scribus-dev] correction needed recent commit r19543
> > >     Commit message for r19543 is actually #12733 and not #2733
> > >
> > >     /Kunda
> > >     _______________________________________________ scribus-dev
> mailing list
> > >     scribus-dev at lists.scribus.net <mailto:
> scribus-dev at lists.scribus.net>
> > >     http://lists.scribus.net/mailman/listinfo/scribus-dev
> > >
> > > Hi Christoph,
> > >
> > > re: Plain text
> > > I'm usually thinking about such things. Honestly, I'm not fully used
> to using this type of ML
> > > technology. Sometimes switching from between different types of lists
> that exist today can cause
> > > some forgetfulness. These are things that I try to pay attention to as
> best as possible as well. As
> > > for responding in pure text I need to examine gmail further to see if
> I can specify that. Will look
> > > in to it. I'm pretty sure that reply to this email will _not_ send it
> in plain text. For just this
> > > moment forgive me for doing so.
> > >
> > > re: bureaucracy
> > > I see. Given your response I can feel that this is an important issue
> for you and therefore I'm
> > > noting your position on it for future considerations. Though I am
> pretty certain that my intention
> > > for pointing out what I was pointing out was purely out of 'future
> friendly' concern. In other
> > > words, to be able to correctly and efficiently track down the correct
> revisions based on the commit
> > > message. Also, I was following the intelligent behavior that has been
> modeled and that I've learned
> > > to appreciate existing in the SVN commit process.
> > >
> > > Just to be clear, I have no intention of asserting my ego, quirks, or
> privileges on anybody let
> > > alone 'suffocate development' or introduce unneeded protocols. I, just
> like all of us who
> > > participate, want to see Scribus succeed.
> > >
> > > Now if you see behavior that you'd prefer me to reflect on and change
> I would be willing to listen
> > > and examine your feedback.
> > >
> > > I am in agreement with you to keep Scribus as free as possible from
> bureaucracy.
> > >
> > > Thank you,
> > > /Kunda
> >
> > Kunda - Please ignore Christoph in this case. :)
> >
> > Christoph - lay off the war path :)
>
>
> Im not on a war path, but I must admit I love to fight government and
> corporate bureaucracies -- remember that I'm living in the land of red
> tape. If in doubt, look at this Australian's humourous description:
> http://www.livhambrett.com/everything-i-know-about-germany-germans/what-i-know-about-germans/
> (#80 and 81, both very true) ;) When I smell demands for an action that
> doesn't make sense, but simply serves bureaucratic pedantry, all alarm
> bells start ringing. Thus, demanding that a typo in a commit message must
> be corrected automatically triggers a NO in super-sized capital letters,
> bold and italics ;)
>
>
> No need to worry, though. I'm still relaxed and appreciate Kunda's work :)
>
>
> Christoph


Thanks fellas :)

Christoph, pretty funny link. I had this visual of you actually rolling
around in freshly printed Scribus SVN commit messages enjoying the scent of
the fresh paper and ink. Now if I could just find a squeegee to clean my
minds eye of that visual, that would be great.

I appreciate everybody's work as well. Onward!

Tsch?ss!
/Kunda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20141001/f69d2482/attachment.html>

From robert.rcampbell at gmail.com  Tue Oct 21 02:11:10 2014
From: robert.rcampbell at gmail.com (Robert M Campbell)
Date: Mon, 20 Oct 2014 22:11:10 -0400
Subject: [scribus-dev] Lao, Thai, Khmer, Burmese, and Karen
Message-ID: <5445C0BE.5030304@gmail.com>

Just curious, which backend for text layout does Scribus currently use?

ICU? Qt? Pango?

I helped provide Lao support in LibreOffice (with a great degree of help 
from the developers). I would love to try to see what I can do, so any 
help is appreciated.

Thanks!


From ale.comp_06 at xox.ch  Tue Oct 21 14:37:38 2014
From: ale.comp_06 at xox.ch (a.l.e)
Date: Tue, 21 Oct 2014 16:37:38 +0200
Subject: [scribus-dev] Lao, Thai, Khmer, Burmese, and Karen
In-Reply-To: <5445C0BE.5030304@gmail.com>
References: <5445C0BE.5030304@gmail.com>
Message-ID: <54466FB2.1070902@xox.ch>

congratulations robert!

you've just been added to the complex script working group!


> Just curious, which backend for text layout does Scribus currently use?
>
> ICU? Qt? Pango?
>
> I helped provide Lao support in LibreOffice (with a great degree of 
> help from the developers). I would love to try to see what I can do, 
> so any help is appreciated.

more seriously, the core developers team is currently not actively 
working (mostly lack of time) on improving the support of non latin 
languages, but they accept patches and can give some hints on how to 
work on the support of complex script languages.

on the other side, lately there have been a few requests of people 
willing to contribute code for support of non latin languages (or having 
working code that they want to see included in the scribus trunk).
in parallel, kunda (who will for sure read these lines) wanted to create 
community working groups.

so: let's do it!


now, we need to know who (else) wants to be part this working group! :-)

ciao
a.l.e


From robert.rcampbell at gmail.com  Tue Oct 21 16:29:32 2014
From: robert.rcampbell at gmail.com (Robert M Campbell)
Date: Tue, 21 Oct 2014 12:29:32 -0400
Subject: [scribus-dev] Lao, Thai, Khmer, Burmese, and Karen
In-Reply-To: <54466FB2.1070902@xox.ch>
References: <5445C0BE.5030304@gmail.com> <54466FB2.1070902@xox.ch>
Message-ID: <544689EC.4010709@gmail.com>

> congratulations robert!
>
> you've just been added to the complex script working group!
>
>
>> Just curious, which backend for text layout does Scribus currently use?
>>
>> ICU? Qt? Pango?
>>
>> I helped provide Lao support in LibreOffice (with a great degree of 
>> help from the developers). I would love to try to see what I can do, 
>> so any help is appreciated.
>
> more seriously, the core developers team is currently not actively 
> working (mostly lack of time) on improving the support of non latin 
> languages, but they accept patches and can give some hints on how to 
> work on the support of complex script languages.
>
> on the other side, lately there have been a few requests of people 
> willing to contribute code for support of non latin languages (or 
> having working code that they want to see included in the scribus trunk).
> in parallel, kunda (who will for sure read these lines) wanted to 
> create community working groups.
>
> so: let's do it!
>
>
> now, we need to know who (else) wants to be part this working group! :-)
>
> ciao
> a.l.e
>
> _______________________________________________
> scribus-dev mailing list
> scribus-dev at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus-dev

Sounds great!

I've worked with LibreOffice in the past, helping them with 
implementation of the latest ICU so that Lao would be supported. I was 
given a great degree of guidance, but I believe that I could help do 
something similar for Scribus, with some help.

I'm no expert at programming, but I think working together, we could 
develop a solution that meets Scribus users' needs, particularly among 
those using complex scripts.

-Robert M Campbell


From scribus.user at gmail.com  Sun Oct 26 15:06:08 2014
From: scribus.user at gmail.com (Kunda Loves Scribus)
Date: Sun, 26 Oct 2014 10:06:08 -0500
Subject: [scribus-dev] Any volunteers to clean up the Bugtracker 'Scripter'
	category?
Message-ID: <CAAt0FRhL8bV1P2MbBVL_OFrT2RuRVNAgQuXA0R+ySt19QVbgoQ@mail.gmail.com>

In the ongoing effort to clean up the Scribus bugtracker and especially
with all this movement happening in the Scripter/CLI a need has presented.
Scribus is in the middle of transition from a deprecated version to a the
more updated version of it's Scripter.

Currently there are 95 open
<http://bugs.scribus.net/view_all_set.php?type=1&temporary=y&show_category=Scripter&hide_status=80>
scripter issues. Would anyone like to go through updating the issue queue +
remove what is not relevant anymore ?

Thanks  in advance!
/Kunda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20141026/95aff981/attachment.html>

