incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <dave2w...@comcast.net>
Subject Re: OOo site standard CSS
Date Tue, 01 Nov 2011 01:09:46 GMT

On Oct 31, 2011, at 6:01 PM, Alexandro Colorado wrote:

> On Mon, Oct 31, 2011 at 6:41 PM, Dave Fisher <dave2wave@comcast.net> wrote:
> 
>> One cool thing you can do is use http://ooo-site.staging.apache.org/es/to confirm
your changes in advance of publishing to production.
>> 
> 
> On that topic should the following script be changed to ooo-site instead of
> openofficeorg?

Exactly!

> 
> ssh -t <user>@people.apache.org publish.pl openofficeorg <your Apache ID>
> 
> Currently that publish.pl only affects the current ooo/ site as opposed to
> the kenai migrated site (and NL projects).

We now have two sites and two trees.

Regards,
Dave

> 
> 
>> 
>> 
>> On Oct 31, 2011, at 5:33 PM, Alexandro Colorado wrote:
>> 
>>> On Mon, Oct 31, 2011 at 6:17 PM, Dave Fisher <dave2wave@comcast.net>
>> wrote:
>>> 
>>>> 
>>>> On Oct 31, 2011, at 4:26 PM, Alexandro Colorado wrote:
>>>> 
>>>>> Another CSS issue this time with the standard behaviors of certain
>> tags.
>>>>> Since the core css affects all the other projects, making modifications
>>>> on
>>>>> the CSS could give unpredictable behaviors on the rest of the site.
>>>>> 
>>>>> I would suggest to use target specific tags like classes or IDs for the
>>>>> tags needed to target.
>>>>> 
>>>>> I think that  having a css that targets body { background-color:
>> black; }
>>>>> would result on many projects being broken.
>>>>> 
>>>>> right now I specifically have this issue with the dl and dd tags and
>>>> their
>>>>> 'block' behavior.
>>>> 
>>>> Can you be more specific. I would take the tack that it makes sense to
>>>> change css/ooo.css if it conflicts with a project.
>>>> 
>>> 
>>> I could have missread the origin of the style and assumed it came from
>>> ooo.css. I am fixing it right now.
>>> 
>>> 
>>> 
>>>> 
>>>> But first check if there were implications on the main page, the
>> download
>>>> page and then ask.
>>>> 
>>>>> 
>>>>> I could fix them by wrapping them within their div and canceling out
>>>> these
>>>>> rules, but I rather have a more generic and standard CSS at the core
of
>>>> the
>>>>> site.
>>>> 
>>>> Recently I changed ooo.css - s/poweredby/poweredbya/g and then the
>>>> skeleton's footer.
>>>> 
>>>> For ja just now I modified ja/stylesheets/style.css removing specific
>> tags
>>>> related to the kenai wrapping of content into a table column. Other than
>>>> some URL changes that seemed to be all that was required.
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>>> 
>>>>> Regards.
>>>>> 
>>>>> --
>>>>> *Alexandro Colorado*
>>>>> *OpenOffice.org* Español
>>>>> http://es.openoffice.org
>>>>> fingerprint: E62B CF77 1BEA 0749 C0B8 50B9 3DE6 A84A 68D0 72E6
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> *Alexandro Colorado*
>>> *OpenOffice.org* Español
>>> http://es.openoffice.org
>>> fingerprint: E62B CF77 1BEA 0749 C0B8 50B9 3DE6 A84A 68D0 72E6
>> 
>> 
> 
> 
> -- 
> *Alexandro Colorado*
> *OpenOffice.org* Español
> http://es.openoffice.org
> fingerprint: E62B CF77 1BEA 0749 C0B8 50B9 3DE6 A84A 68D0 72E6


Mime
View raw message