Date: prev next · Thread: first prev next last


Hi Drew,

On Fri, Jun 17, 2011 at 8:22 AM, drew <drew@baseanswers.com> wrote:

<snip>

 Howdy,

well, no link to the projects ML yet, but maybe later today.

SO for this mornings stand up meeting:

One quick question:

Shall we layout the structure on the CMS development platform so as to
create a single .iso file with all the files needed to support all three
languages (html files/artwork/add-ons) or in such a way as to be able to
generate three .iso files, once each for each langauge?

I have, quietly, been working on my copy of SilverStripe and exploring
ways to approach this - my preference at this point would be to generate
one .iso file with everything included for the three languages.

How do others feel on this?

Thanks

Drew


If I understand what your asking correctly.... A single .iso would make sense
with the install-multi and install-all lang. packages. If there is
room for all the
different language files... docs, templates ... ( I think Tim@ said there was
room for all in a earlier email.)

1 iso. to distribute, 1 .iso to maintain.

Thanks for all your work.

-- 
Lyle Cochran
www.bytepowered.org
lpcoch@gmail.com
Ohio, U.S.

-- 
Unsubscribe instructions: E-mail to marketing+help@us.libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/us/marketing/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.