We've found over the last few years that the stable releases have odd bugs in them that make our life difficult at print time. The answer from devs there has always to use trunk instead.
Ilan Rabinovitch Conference Chair Southern California Linux Expo 877-831-2569 x110 Voice 818-442-1865 Mobile ilan@linuxfests.org Email
--- Ask me about sponsorship and speaking opportunities at LinuxFests.org's upcoming events: * SeaGL - Nov 11-12, 2016 * SCALE 15x - March 2-5, 2017 - Pasadena, CA
On Mon, Feb 13, 2017 at 1:04 PM, Lei Zhang leiz@socallinuxexpo.org wrote:
I'll try that out, but please remember the danger of using trunk. The version of scribus-trunk I install today may be able to read your file, but what it saves may not be readable by the version of scribus-trunk you installed last week. When you run into this problem and upgrade tomorrow, that version of scribus-trunk may create files that my install from today cannot read, and so on.
On Sun, Feb 12, 2017 at 11:27 PM, Josh Andler scislac@gmail.com wrote:
Ubuntu 16.10 is what I'm using with this PPA: https://launchpad.net/~scribus/+archive/ubuntu/ppa
I use trunk... (since that is probably relevant)
On Sun, Feb 12, 2017 at 10:04 PM, Lei Zhang leiz@socallinuxexpo.org
wrote:
No version of Ubuntu/Debian provides 1.5.x as of this writing. [1] [2] What distro provides 1.5.x? I can make a VM.
searchon=names&suite=all§ion=all
searchon=names&suite=all§ion=all
On Sun, Feb 12, 2017 at 9:31 PM, Josh Andler scislac@gmail.com wrote:
Lei,
Yikes... not possible. They literally have one option in their Save As dialog (document). What platform/OS are you on? If we can't get you on a more recent build I can recreate the doc with an older version of Scribus.
On Sun, Feb 12, 2017 at 9:21 PM, Lei Zhang leiz@socallinuxexpo.org
wrote:
Josh,
Any chance your version of Scribus can save a file that is readable by Scribus 1.4.x?
On Sun, Feb 12, 2017 at 8:11 PM, Josh Andler scislac@gmail.com
wrote:
Sorry I didn't reply back here as well, here is an example file for the abstracts. https://drive.google.com/file/d/
0B66M6tvXugFoU0tVdFhabENObk0/view?usp=sharing
I will see if I can do one as well for the grid, but that is probably too much to ask on short notice (the existing python doesn't do anything close to it).
Cheers, Josh
On Tue, Feb 7, 2017 at 12:07 PM, Lei Zhang leiz@socallinuxexpo.org
wrote:
> If you can take a few talk entries from our schedule and manually > create a Scribus document out of it, I can try to write a script to
do
> the same. The existing scripts you referred to are not directly
useful
> since they have many values hard coded for their conference. > > On Mon, Feb 6, 2017 at 12:37 PM, Josh Andler scislac@gmail.com
wrote:
>> Lei, >> >> I'm hoping to have the ability to easily get data into Scribus >> documents. The best summary I can give is the biggest help would
be if
>> someone could dig in to the python and see that they understand it
to
>> help create our own custom scripts/tools. >> >> What's available appears to do something akin to our listing of
talks
>> & descriptions. This section of the program requires a whole bunch
of
>> manually applying styles (thankfully usually a once over, however
time
>> consuming process). If I can get text from a csv, either into >> pre-styled elements in a Scribus doc (or I don't know, perhaps the
API
>> allows setting that in the script) it would save a massive amount
of
>> time. Ideally, a modified version which would allow populating a
table
>> (for the visual grid schedule) would likely be the biggest help. >> >> As an offshoot thought, I'm also hoping to be able to use data >> importing to speed up generating the signs as well. >> >> Cheers, >> Josh >> >> On Mon, Feb 6, 2017 at 12:07 PM, Ilan Rabinovitch >> ilan@socallinuxexpo.org wrote: >>> Josh was hoping someone could take a stab at pushing the SCALE >>> presentation list into this code, and seeing what comes out the
other
>>> side. We're trying to see if this might reduce the level of
effort on
>>> his end for generating the schedule. >>> >>> >>> >>> >>> Ilan Rabinovitch >>> Conference Chair >>> Southern California Linux Expo >>> 877-831-2569 x110 Voice >>> 818-442-1865 Mobile >>> ilan@linuxfests.org Email >>> >>> --- >>> Ask me about sponsorship and speaking opportunities at >>> LinuxFests.org's upcoming events: >>> * SeaGL - Nov 11-12, 2016 >>> * SCALE 15x - March 2-5, 2017 - Pasadena, CA >>> >>> >>> On Mon, Feb 6, 2017 at 12:03 PM, Lei Zhang <
leiz@socallinuxexpo.org> wrote:
>>>> It's not obvious what you are asking for. Presumably one takes
their
>>>> software, feed it a CSV file, and get a SLA file out of it. Are
you
>>>> looking for help generating the CSV file, or modify their
software to
>>>> tweak the SLA output to fit your requirements? >>>> >>>> On Sun, Feb 5, 2017 at 9:22 PM, Josh Andler scislac@gmail.com
wrote:
>>>>> Hey All, >>>>> >>>>> So, working on the printed program for SCALE every year is one
of the
>>>>> most challenging tasks for the graphics/design team. If there is >>>>> someone who is proficient in python and willing to learn a
specific
>>>>> application's API, you could probably save us days of work
(especially
>>>>> if changes happen close to the expo). >>>>> >>>>> Basically, I need a way to pseudo-automate populating the daily >>>>> schedules for SCALE within Scribus. I spoke with a couple
developers
>>>>> for the application and was pointed to this repository: >>>>> https://gitorious.org/schedule-csv2scribus-rmll/
schedule-csv2scribus-rmll?p=schedule-csv2scribus-rmll: schedule-csv2scribus-rmll.git;a=tree
>>>>> ... which has the relevant files to generate pages within
Scribus from
>>>>> CSV files. >>>>> >>>>> Anyone interested, willing to do some digging, and want to talk
more
>>>>> about it? It would be greatly appreciated if I could get a hand
in
>>>>> this area. >>>>> >>>>> Cheers, >>>>> Josh >>>>> _______________________________________________ >>>>> Scale-planning mailing list >>>>> Scale-planning@lists.linuxfests.org >>>>> https://lists.linuxfests.org/cgi-bin/mailman/listinfo/
scale-planning
>>>> _______________________________________________ >>>> Scale-planning mailing list >>>> Scale-planning@lists.linuxfests.org >>>> https://lists.linuxfests.org/cgi-bin/mailman/listinfo/
scale-planning
>>> _______________________________________________ >>> Scale-planning mailing list >>> Scale-planning@lists.linuxfests.org >>> https://lists.linuxfests.org/cgi-bin/mailman/listinfo/
scale-planning
>> _______________________________________________ >> Scale-planning mailing list >> Scale-planning@lists.linuxfests.org >> https://lists.linuxfests.org/cgi-bin/mailman/listinfo/
scale-planning
> _______________________________________________ > Scale-planning mailing list > Scale-planning@lists.linuxfests.org > https://lists.linuxfests.org/cgi-bin/mailman/listinfo/
scale-planning
Scale-planning mailing list Scale-planning@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning
Scale-planning mailing list Scale-planning@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning
Scale-planning mailing list Scale-planning@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning
Scale-planning mailing list Scale-planning@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning
Scale-planning mailing list Scale-planning@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning
Scale-planning mailing list Scale-planning@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-planning