Date: prev next · Thread: first prev next last

On 06/17/2011 09:39 AM, drew wrote:
On Fri, 2011-06-17 at 08:45 -0400, webmaster for Kracked Press
Productions wrote:
On 06/17/2011 06:20 AM, drew wrote:
But it doesn't matter at this point - with Jeff gone I assume this
'little sprint' is in my lap, but only for figuring out timing. Which is
to say, I looked and thought and figured if it was just me then I could
get it done by 7/7 - if anyone else jumps in...well that will change for
the better.

Anyway I was trying to be a little humorous in the email. So one page a
day, on average, is my goal and if so then by July 7th it should be done
and tested.

Do you want me to work the pages?
Heck yes. For right now it might be most efficient to have me do the
first pass cut in of a page and then you can edit as needed, for a few
days at least and you can spin up on the details of working with the CMS
as you do.

I've got an idea on how to layout the files for a system where there is
one .iso image with all three languages on it - I have another for doing
three .iso images with one language each.

If we have a better menu structure, with the second navigation line like
LibreOffice site has, then I would like to see a "Addition To" type of
name.  That name would make a second line with:

Extensions    Dictionaries   Templates and Sample Files     Artwork and
Alright, I don't really have a strong opinion on that and would see it
as an implementation detail we can work out as we go. (lol, which is
probably going to be day 2 or 3...)
What I am talking about it what is shown on this page , or any other link on the top of the navigation bar[s]. It would make life simpler if we could do that, but that may be a future option. Hopefully the system has that type of option.

Could you give me the needed info so I can look at that system and maybe get an account started? I do not know where it is located, URL wise.

I wonder about the shared resources, beyond the themes and install
files.  It would be nice to see the dictionaries, extensions, templates,
and artwork, in a shared resource.
Yes I agree, from the point of view of the disc production platform -
the CMS does have a way to handle this and moving files to the CMS is
one of the first tasks to accomplish, one that will start this evening.

I still would like to see them on a
LibreOffice site instead of an OOo one.
Different subject, IMO, and given my reading of ALL the emails lately on
multiple lists from multiple organizations I figure that is about to be
a given.

I'm planning on doing the first - one .iso image with all three (English
only to srart) languages supported. But I want to put that to the
mailing list first.

As for the Language Support, we should have the language and help packs
for all the common languages that are taught in schools or in use in the
larger communities.  Marc states, I think, that he taught French to a
school population that had 50% or more students that spoke Portuguese.
Here they have Spanish, German, Italian, etc..  Hebrew is a community
the is not supported be most office suites, as far as I have been told.
If I may, also off topic for todays 'vitual' meeting.

I agree that having a English/Spanish/French .iso would be great,
whenever it happens.

We should use the wiki method of having a
navigation selection EN, FR, ES somewhere so the user can switch
language at the page level.
Actually I would go with a different approach, for the .iso, which would
be a single home page where the user selects the language (fr or en or
es) and that takes them to the top level page for that lanuages UI,
which of course offers links the files for that language. Of course
there are gong to be some files (many perhaps) that are shared. But for
the on-disc files I would not be in favor of offering this at a page

For the CMS based user facing website where we distribute the .iso this
may make sense, but that is not something we need to work out today IMO.

Within those pages, we could have the EN/FR/ES navigation links. That would be "simple" for me to setup once we have the pages created. I created a Javascript file for a different site that used a page ID and then it used that ID to determine what was displayed on the menu list. One script called. One ID per page. Simple to keep up-to-date once setup.

<script type="text/javascript">var menupage=4</script> --- The page ID <script type="text/javascript" src="menu-top.js"></script> --- The scripted that used that page ID

Are we going to have a 3.3.x site and a 3.4.x site since both are part
of LibreOffice's site?  There was also an idea floating on the lists
about having a DVD with both lines so the user can choose which one they
want to use.  I would not mind seeing one.  There just have to be some
reduction in the Extra's page to make both install groups fit on one DVD.
Good question - I would be in favor of a single .iso for the moment at
least and would prefer to see us go with the most stable release


At the end of the month 3.4.1 is due out - if on schedule. Once that is out, it may be considered "stable" enough for most non-business users. 3.4.2 or 3.4.3 might be ready for business users.

The last release [and first] for the lines are as follows:

3.3.5 - October 2011 ---------------- 3.3.4 - August 31st
3.4.5 - November 2011 -------------- 3.4.1 - June 29th, 3.4.2 - July 27th, 3.4.3 - August 31st, 3.4.4 - October 5th
3.5.0 - February 2012 ---> 3.5.6 - October 2012

So we will need to be ready for the 3.4.x line as well as the "most stable" 3.3.x line.

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.