[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: new Firefox/splash page for FC6?

O/H Paul W. Frields έγραψε:
> Was possible, and I figured out the technical details for how to provide
> arbitrary @class attributes for some elements.  This would allow
> translation of the index page in several languages.  However...
> How would we get the right HTML page to come up in the user's browser?
> Is there some META magic that allows autorefreshing with a page in a
> different language?  And can that language be derived from the browser
> environment?

We could make this distinction/check at the time the RPM gets installed, but,
this shouldn't be a system-wide setting.

On the other hand, it seems that Javascript provides a way to do this:


So, we can get it by calling `navigator.language`, which yields "en_US".
Konqueror supports this property too. There are some other properties (put up by
IE, browserLanguage, userLanguage, systemLanguage). You can check if your
favourite browser supports the `.language` property at the bottom of:


So, I guess we could just write a few lines of Javacript in `splash.html` and
redirect to the correct page, like: `splash-en_US.html`, etc.

> In any case, to accomplish #2, the fedora-release-notes package would
> have to be rearranged from its current state.  This is a problem of
> relative links and not wanting to have some very ugly hack to turn those
> links into translatable content.  It's much preferable to have an
> automatic engine that simply puts everything from one language together,
> and then the links would point to the same target in every locale, that
> being "./MYDOC.html".  This kind of rearranging isn't going to happen
> this close to release.

I didn't understand exactly what the problem is with what links, but anyway. We
could leave the release notes intact and just add `splash.html` as the default
homepage, right?

> Let's look at improving the situation post-FC6.
> For now, Dimitris, go ahead and keep working on the page as static HTML
> content.  If/when you're done with your part and ready to have it edited
> and polished, send it to the list.

I guess my work is almost over, I just need to put in some changes Rahul et al
proposed and polish the HTML and CSS. I'll probably do these tonight.


> I'll import it into the
> release-notes module and do the necessary packaging to make it work in
> the Rawhide tree.  If we hurry with this, we might even make it into
> test3, I'm told.

Dimitris Glezos
Jabber ID: glezos jabber org, GPG: 0xA5A04C3B

"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]