On Sat, Jul 19, 2014 at 9:36 AM, Alexandro Colorado <j...@oooes.org> wrote:
> On 7/19/14, Kay Schenk <kay.sch...@gmail.com> wrote: > > On Sat, Jul 19, 2014 at 5:56 AM, Emanuele <emanuel...@gmail.com> wrote: > > > >> Alexandro Colorado wrote: > >> > ok if you can do that that{s great, just want to encourage to clean up > >> > the current state of the site where there are different css running > >> > aound on different paths that are just hard to manage and some of them > >> > might be deprectated. An example, would be having 4 css files on root. > >> > exceptions.css home.css sitemap.css styles.css > >> > >> Oh in that sense, yes, I agree. > >> > > > > There are MANY MANY MANY unused styles throughout the entire website. > For > > now, I don't think we should worry about them. At some point, maybe, > but a > > total evaluation will take time. > > > > I believe the css/ooo.css was put in place to accomodate the styles > needed > > by the CMS. Our legacy css files are all over the place. > > > > > >> The current structure is a bit funny to deal with, yes you have the file > >> "where you need it", but it may result in conflicts and it may not even > >> be so easy to find what you are looking for (it's just my feeling > >> though, maybe because I'm used to work with a single huge file). > >> See the attachment with the cleaned up code and the comments (idea > >> borrowed from another project I'm contributing to). > >> > >> I noticed there is the possibility to specify an id for the body tag, > >> that is cool and may already help to target specific pages with custom > >> styles if needed. > >> > >> I wonder also about the "local" websites (I mean the different > >> languages). I see... several variants in respect to both design and > >> content. Is there the intention to move them to a standard appearance or > >> just let them be with whatever style they have? > >> > > > > We have standardized some of the "native language" sites recently -- in > the > > last year or so as needed and desired by these communities-- but many > > continue to have their own look and feel. And this is OK. > > What about inactive NL sites? Is there a table which list the NL current > status? > Do you mean in terms of distribution or the web sites are newer/standardized? In any case. we have this page-- http://www.openoffice.org/projects/native-lang.html which could be edited to add a distribution status instead of the Level column which we no longer use. This would be a nice help if someone wants to work on that. Of course you can also easily navigate to a particular native language site from this one. > > > >> > >> Emanuele > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > > > > > > > > -- > > > ------------------------------------------------------------------------------------------------- > > MzK > > > > "To be trusted is a greater compliment than being loved." > > -- George MacDonald > > > > > -- > Alexandro Colorado > Apache OpenOffice Contributor > 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- ------------------------------------------------------------------------------------------------- MzK "To be trusted is a greater compliment than being loved." -- George MacDonald