I've seen that the french (my ^^) translation has been put online, but the script that should change the document.location doesn't work I'm using Firefox (0.8) but it works with Avant, so it should work in IE too.. I've already sent an email to Patchou about this problem

[edit] His answer : don't use firefox xD [/edit]

quote:

---

Originally posted by Apatik
don't use firefox xD

---

Well, it's not my fault if Firefox is not compatible with the browser which is being used by 95% of the people who go on msgplus.net . As I know that Firefox already has some kind of nasty plugin disabling Flash in the worse possible way, I couln't take this warning very seriously, sorry about that .

In any case, as Mnjul gave me the fix on a golden platter, I included it. It should now work with your browser .

Patchou, seriously: I think you're completely wrong about this.
Remember that 100% of windows users are sort of forced to use Internet Explorer unless they download another browser. Mostly n00bs and unconcerned people stick to IE => 90%. If you take a look at the 50 top posters you'll see that percentile dramatically decreases .

Any good website builder is concerned with the portability of the code:
- Following W3C standards
- Testing it on most browsers (ie, but not limied to: MSIE, Mozilla, Opera and Safari, at least)

You can't just marginalize a browser because it's less used than another, I thought you'd know that from Plus! compatibility with old and hardly used versions of Messenger, for example .

I'm happy anyway that this gets fixed soon .

PS: Firefox hasn't already anything about blocking flash. There is a third-party plugin that can do so, in order to block ads, not just block any flash that comes through the line .

when will the other languages be added?

[OFF TOPIC]

quote:

---

Originally posted by gooofi
when will the other languages be added?

---

quote:

---

Originally posted by CookieRevised

There are already many languages added...

---

i checked it before i posted and the "select your language here" @ msgplus.net shows only "francais"

it still doesn't work xD

If it still doesnt work I really doint know what else I could do. And as for following the glorious W3C standards, let me laugh: haha. If Microsoft (and Netscape at the time, for once, I have to give them credits for something) hadn't taken things in their own hands to allow more features in web page, almost nothing would have changed in the past 8 years. Standards are good, as long as they match needs. As far as I am concerned, IE has become the standard, I couldn't care less if another browser is not capable of rendering my pages as IE do. I know this sounds blunt that I'm really speaking my mind here (and this doesnt mean I don't like Firefox, this seems to be a very promising browser).

in the code of the main page of msgplus.net, search

code:

---

<select size="1" name="language" class="language" onchange="test();">
<option style="color:gray;">Select your language here</option>
<option value="fr">Francais</option>
</select>

---

code:

---

<form name="CholiWasHere">
<select size="1" name="language" class="language" onchange="test();">
<option style="color:gray;">Select your language here</option>
<option value="fr">Francais</option>
</select></form>

---

done

tbh, I don't agree Patchou. This isn't about new standards, this is about implementing the existing standards in the right way. Like Choli said, <select> is a form element, thus you need to include it into a form. You don't make a subroutine in a program without a startheader and a endheader...

Anyways, it works fine now...

EDIT: blah... I was too slow....

Anyways, the error in MSIE of whish I spoke in my last email (or the mail before that, dunno anymore) is indeed there. It concearns the small background banners shown in the boxes on the right side. I'll try to find out more and test some stuff and then I'll try to explain later...

Well, I'm sorry but no, this just doesnt do it. I added <form> and here is what it gave me:



I've removed it now. I have nothing against standards, they serve some purpose, but at the end, what matters is that they help you do stuff, not prevent you. If you find a good way to fix it, feel free to give me the code .

quote:

---

Originally posted by Patchou

---

quote:

---

be sure you don't put any extra space in the code

---

quote:

---

Originally posted by Patchou
Are you making fun of me?

---

quote:

---

Originally posted by Patchou
Anyway, there was no extra blank space, its just the <form> tag that did the problem. It seems to add the space of two blank lines which is absolutely not good. You can see on msgplus.net how the combo box is supposed to be displayed.

---

quote:

---

Originally posted by Patchou
Thanks for the help

---

Like I said before, to use form-elements in a proper way, you need to define a form. The problem with this, as you showed, is that MSIE has a bug when it comes to forms inside tablecells: it puts linebreaks before the selector...
It goes even further, MSIE even puts linebreaks before the table if you put the <form>-tag outside the table.

These bugs from MSIE (it's not a bug in other browsers) should be known by most website-developers because they are indeed very dodgy...

The workaround is to define the form outside the tablecell, but inside the table, so instead of:
<table><tbody><tr><td><form><select></select></form></td></tr></tbody></table>
use:
<table><tbody><form><tr><td><select></select></td></tr></form></tbody></table>


OR


Because you don't define a form, you must search for the form-elements with a script. Just like Guido does in msgplusjs.js. The problem with that is that the names from MSIE and Mozilla based browsers for the layerstructure of a document is different. And the script only checks for the MSIE based names, so that's why Mozilla based browsers return "undefined" and thus the script can't execute further.

The workaround for this is easy:
I've seen in msgplusjs.js that there is a very complicated and unneeded script being used to catch the select-object (with all the problems it brings).
This can be solved by:
Delete the function "GFDD_findObj" and "GFDD_jumpMenuGo", these are not needed because in the html-code the object can be returned directly by the use of the "this"-word like so: <SELECT class=language onchange="GFDD_jumpMenu(this);" size=1>



So, in short: choose one of the two methods:
1) use <table><tbody><form><tr><td><select></select></td></tr></form></tbody></table> and leave the javascript and everything as it is.
2) don't use the <form>-tag and change the select-tag to: <SELECT class=language onchange="GFDD_jumpMenu(this);" size=1> and then you can even remove those two functions (GFDD_findObj and GFDD_jumpMenuGo) in the script.


I hope this helps

quote:

---

Originally posted by CookieRevised
<table><tbody><form><tr><td><select></select></td></tr></form></tbody></table>

---

code:

---

<form name="CholiWasHere" style="margin-top: 0px; margin-bottom: 0px;">
<select size="1" name="language" class="language" onchange="test();">
<option style="color:gray;">Select your language here</option>
<option value="fr">Francais</option>
</select></form>

---

Bha.... I don't like HTML lol. Thank you for the fixes though, I'll try it out.

EDIT: Seems to work well. Let me knwo if the fox is happy with it now .

quote:

---

Originally posted by Patchou
Seems to work well. Let me knwo if the fox is happy with it now

---

* WDZ switches the language to Spanish...

quote:

---

Originally posted by Patchou
Seems to work well. Let me knwo if the fox is happy with it now

---

quote:

---

Originally posted by CookieRevised
I've seen in msgplusjs.js that there is a very complicated and unneeded script being used to catch the select-object (with all the problems it brings).

---

quote:

---

Originally posted by Ddunk

quote:

---

Originally posted by Patchou
Seems to work well. Let me knwo if the fox is happy with it now

---

Yep, works in Firefox

---

quote:

---

indeed, dodgy script

---

The script was dodgy, I agree . And I know it worked with FFox before (I tested the site in every modern browser), though I must have removed the <form> during development.

As for Patchou's opinions regarding browsers "uncompatible with IE"... well, I don't agree   These are undocumented behaviours which have no reason to work, if IE decides to make them work good for them, but it's not other browsers' fault.

quote:

---

As I know that Firefox already has some kind of nasty plugin disabling Flash in the worse possible way, I couln't take this warning very seriously, sorry about that

---

quote:

---

Standards are good, as long as they match needs.

---