I think that makes sense - having one rtl.css that overrides the default styles. It's a lot more maintainable than trying to keep multiple rtl stylesheets in sync with the main stylesheets.
 
You may need to use chained selectors or !important declarations in some places to successfully override the defaults. Let me know if I can make any changes to the core CSS to make things easier.
 
Cheers,
Wilson
 
On 6/7/06, mksoft <[EMAIL PROTECTED]> wrote:

I'm working on right-to-left enabled support for the admin interface.
The strategy right now was creating a matching RTLed stylesheet for
every one there is which overrides only the ltr specific settings, so
we have:

base.css->base_rtl.css
layout.css->layout_rtl.css

etc.

The problem ? Styles are scatterd among many sheets and it's getting
quite messy. Lots of those are loaded twice as well. e.g:

dashboard_rtl.css load dashboard.css which loads base.css. It also
needs to load base_rtl.css by itself (which loads base.css as well and
modifies the needed ones).

As we can see, it's quite a mess.

Since RTL changes are relatively small, maybe a better solution would
be to create an rtl.css which contains all the rtl needed overrides in
a single, and more maintainable file ? It would look better in the
templates as well. (loads the basic style, and in case of
LANGUAGE_BIDI, load rtl.css).

Comments ?
--
Meir Kriheli
http://mksoft.co.il



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django I18N" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/Django-I18N
-~----------~----~----~----~------~----~------~--~---

Reply via email to