<div>Ed's bug report has been confirmed on FF3, but it does not occur with FF2. Thanks to mchua for testing on FF2/Ubuntu and FF3/Ubuntu, I can also add that it does not occur on IE7/Vista. </div>
<div> </div>
<div>Furthermore, mchua confirms that commenting out arabic causes the problem to go away in FF3.</div>
<div> </div>
<div>In my opinion, this pretty much narrows this down to an issue with FF3 trying to do something clever on the span mouseover when it sees the R-to-L script of Arabic as I had speculated earlier. The easy work-around is to leave R-to-L scripts out at this point in time, until more clarity can be gained on whether this gets fixed in FF3. Perhaps creating a second template (or a second <span class> </span> statement on the same template) would be suitable near-term workarounds.</div>
<div> </div>
<div>Overall, my opinion is that the occurence of this issue only for FF3 beta-testers makes this something of a non-issue at this point in time. It might be nice for someone to communicate this back to mozilla community, but I'm going to decline to carry that ball. Ed, you're the FF3 beta-tester, maybe you might do so.</div>
<div> </div>
<div>I'd love to turn this wiki template idea over to someone who has good wiki template-fu. For instance, I don't know if this can be reduced to a single template (with variable start lang) or if practically it needs to be expanded into a suite of templates with fixed start langs. </div>
<div> </div>
<div>If there is anyone else out there that thinks the idea of end-users (testers at schools) being able to post to the wiki in their own language and get useful info back to developers (mostly lang-en) with minimal language barriers, please step up and chip in. I know machine translation is imperfect, but then again so are most messages to the "helpdesk" from end-users. I really think this would be a useful addition to overcoming l10n barriers to feedback from deployments, as well as minimizing the l10n barriers to local users harvesting information off of the mostly lang-en wiki pages. Human page translation efforts on wiki can be focused on truly "important" pages and most of the rest can be made reasonably comprehensible across language barriers by clicking a single link for a "good enough" Google translation. </div>
<div> </div>
<div>Thanks to morukai and mchua for testing.<br><br></div>
<div class="gmail_quote">On Sun, May 11, 2008 at 12:35 PM, Chris Leonard <<a href="mailto:cjlhomeaddress@gmail.com">cjlhomeaddress@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Interesting. it's tests absolutely fine for me on Safari on OSX and Firefox <a href="http://2.0.0.14/" target="_blank">2.0.0.14</a> and IE7 on WinXP/SP2. I don't have access to a config like your's right now and I haven't tested on my XO yet either. </div>
<div> </div>
<div>The template itself is surprisingly simple HTML See <a href="http://wiki.laptop.org/go/Template:Gttranslation_alt" target="_blank">http://wiki.laptop.org/go/Template:Gttranslation_alt</a></div>
<div> </div>
<div>You can also compare it to the original I found which assumes lang-en as starting language on page. <a href="http://wiki.laptop.org/go/Template:GTranslations" target="_blank">http://wiki.laptop.org/go/Template:GTranslations</a></div>
<div> </div>
<div>I modified it to assume lang-es as starting language.</div>
<div> </div>
<div>Just speculating, but perhaps it is the combination of the presence of Arabic (An R-to-L script) as the first entry on the list and the possibility that the beta-version of FF you're using is trying to do something clever (e.g. pre-interpret script direction on mouseover of span), but having unexpected consequences.</div>
<div> </div>
<div>One thing to test would be dropping Arabic out of the template as a first quick pass at narrowing it down. Of course, it's always possible you have identified one of the reasons that FF3 is still beta and not production.<br>
</div>
<div>Thanks for the testing.</div>
<div> </div>
<div>cjl<br></div>
<div>
<div></div>
<div class="Wj3C7c">
<div class="gmail_quote">On Sun, May 11, 2008 at 5:04 AM, Edward Cherlin <<a href="mailto:echerlin@gmail.com" target="_blank">echerlin@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>On Sun, May 11, 2008 at 12:58 AM, Chris Leonard<br><<a href="mailto:cjlhomeaddress@gmail.com" target="_blank">cjlhomeaddress@gmail.com</a>> wrote:<br>><br>> All,<br>><br>> I'm experimenting with a really cool template that I found sitting<br>
> more-or-less abandoned on the wiki. User:Katie had started it in Jan. It<br>> adds a Spanish to lang-xx translation quick-link to a lang-es wiki page. As<br>> a test-case, I've added it to <a href="http://wiki.laptop.org/go/Lambayeque" target="_blank">http://wiki.laptop.org/go/Lambayeque</a>.<br>
><br>> This could useful, feel free to try the links on Lambayeque, but it's highly<br>> experimental, so please don't replicate it around just yet.<br><br></div>The resulting set of links is rendered unstably in Firefox 3 on<br>
Ubuntu. When I point to any of the links, the order of the links<br>changes from RTL to LTR and back too rapidly to read. When I remove<br>the cursor from the line of links, it can remain rendered in either<br>order. The URL displayed in the status bar also flickers between two<br>
different values. When I click in a particular location, I can get<br>either of two different translations at random.<br>
<div><br>> The concept is<br>> generalizable, in fact, the original template is specific for lang-en, I<br>> modified it for use on lang-es pages. Essentially a whole suite of these can<br>> be created from lang-yy to langs -aa -bb -cc, etc, up to Google's coverage<br>
> limit. These templates will have to be created and named systematically,<br>> if/when it gets done.<br>><br>> I saw a message on the devel thread where Spanish language feedback (from<br></div>> Lambayeque) was not accessibe to the developer because of the language<br>
<div>> barrier. It just goes to show that l10n issues cut both ways.<br>><br>> <a href="http://wiki.laptop.org/go/User:Cjl" target="_blank">http://wiki.laptop.org/go/User:Cjl</a><br></div>> _______________________________________________<br>
> Localization mailing list<br>> <a href="mailto:Localization@lists.laptop.org" target="_blank">Localization@lists.laptop.org</a><br>> <a href="http://lists.laptop.org/listinfo/localization" target="_blank">http://lists.laptop.org/listinfo/localization</a><br>
><br>><br><font color="#888888"><br><br><br>--<br>Edward Cherlin<br>End Poverty at a Profit by teaching children business<br><a href="http://www.earthtreasury.org/" target="_blank">http://www.EarthTreasury.org/</a><br>
"The best way to predict the future is to invent it."--Alan Kay<br></font></blockquote></div><br></div></div></blockquote></div><br>