Template talk:Announce

The Non-breaking Space

I don't have a copy of one of those ancient browser to verify Omniplex's rationale or test a solution that works in all browsers, but the non-breaking space in most modern browsers (Firefox and IE tested) forces the size of any announce box to be two lines. This causes the announcement list to look too "airy". I'm going to remove one of the extra (regualr) spaces to see if this fixes the problem. — Ambush Commander^(Talk) 18:37, 17 June 2006 (UTC)

Manually setting a width seems to fix the nbsp wrapping. — Ambush Commander^(Talk) 18:42, 17 June 2006 (UTC)

Not checking what you did, because the effect is fine on template:Information thread (edit•talk•links•history), also on Goings-on. If necessary we could tackle it from a completely different direction, I can create a GIF from the PNG. A GIF should be smaller, it allows dirty tricks like 16 colours (instead of 256), enough for the MediaWiki logo... ;-) -- Omniplex (w:t) 21:25, 17 June 2006 (UTC)

Typography — Space before colon

Hello people, On the home page in french, I have “15:” instead of “15 :” My recent edits were maybe not the best way to handle that, but they have the merit of working.

no it was not working as you think, it works on one placen in a specific environment with specific language settings per user. verdy_p (talk) 12:54, 2 June 2014 (UTC)

Now this is broken. Can someone fix that, please ? Verdy p ?

it is not severaly broken (the small typography is less serious than translations to incorrect language or lach of adaptation to completely different scripts having very different contextual rules); for now it is a compromize waiting to be fixed elsewehere before we can be more precise. It is nons sense to fine-tune a specific language when it will worsen all others. verdy_p (talk) 12:54, 2 June 2014 (UTC)

What did my handling worsen ? I had put conditions so that only some specific languages — french, corsican, and so on — had their typography changed. --Nnemo (talk) 13:11, 2 June 2014 (UTC)

Thank you. --Nnemo (talk) 12:30, 2 June 2014 (UTC)

This is work on progress, but the problem is to trace the language effectively used, as I said above this is more complex than the basic edits that were performed, notably on this home page that does not pass this info correctly to templates. Also because legacy code has assumed everywhere that the UI language and the contentn language were the same (and the content language is not easy to handle in templates, depending on where they are used).

But you cannot make an superficial edit, the problem is deeper and requires preparation elsewhere. The main page is the worst page of Meta wiki, as every thing is mixed up and was initially tested only for English or were translated using false assumptions.

verdy_p (talk) 12:54, 2 June 2014 (UTC)

Note: the space before colon is already handled in the Template:colon. Which works on all pages using the Translate extension, as well as on all untransalted paes in English (most of untranslated pages are in English). For the other translated pages not respecting the conventions, there's no easy solution without passing additional parameters, and also witout trying to duplicate the code (which makes things even more complicate to fix later whe nthe number of places to edit simltaneously accumulates). Things are more complicate on a multilingual wiki like Meta or Commons. the tempaltes initially developed only for EN.WP or FR.WP will not work. I've probably passed more time than anyone else on Meta-Wiki tryng to improve things (and making many more tests and subtle corrections not evident, or emporarary edits meant to avoid breaking everyinth becair another change is made elsewhere). Such transformation to be really multilingual is necessarily more progressive but you cannot assume that all colons will behave the same everywhere.

Why could I not make a superficial edit ? If we don’t do this, then what do you propose we do ? --Nnemo (talk) 13:11, 2 June 2014 (UTC)

If you look closely n the history of Template:colon, you'll see that I perfectly understand the problem (and not just for French and English, you'll notice things for Armenian, as an example and for Indic scripts, Chinese...). verdy_p (talk) 13:02, 2 June 2014 (UTC)

Yes, I have seen that. It is great to have this adaptation to so many exotic writings. But the problem is that it does not work. --Nnemo (talk) 13:11, 2 June 2014 (UTC)

It will work with that code; but the problem is elsewhere and requires more edits before we can pass the correct language code (there are other places to edits before to avoid breaking pages severely with red links to unresolved template names or incorrect language code inference that would cause English to appear everywhere).

These eits are in line with an evolution to the Translate extension, or to be compatible with it (notably with page naming).

Look at Main Page/fr which does not have this issue, you'll understand the problem is caused by incorrect choise of default language (confusions everywhere in code between content language and UI language: the Main page does not specify pass the language to use everywhere; if it's missing it is hard to use the correct default between one or the other; and it is complicated by language fallbacks in both cases; and the fact that many templates used are also used on other pages using various models to translate them, which are not compaible with each other without additional "exotic" parameters, until we migrate thse other pages too, vefore simplifying what is no longer needed). verdy_p (talk) 13:23, 2 June 2014 (UTC)

PNG --> SVG

I propose, if everyone agrees, to remplace by . Thomas Linard (talk) 10:50, 10 January 2019 (UTC)