// this mail use UTF-8 format //
Hi all. Can you please remove the "5 same template per page" limit for small templates? Tim Starling spoke about other method to limit risk of DOS attack (based on template size), but waiting to those implementations can you deactivate the limit (or set it to 100) for tiny template (ex: less than 1kb, 256 bytes, or 100 bytes).
For example, on French WP, we use a lot of {{e}} to emulate <small><sup>e</sup></small> (it's same as the English "th" for centuries, etc.).
Other thing, I tried to make a template to be able to write Japanese furigana (small letters over kanjis to give the pronunciation) into articles. I tried this
{| style='display:inline;' |<font size='-4'>{{{2}}}<font> |- |{{{1}}} |}
I'd like to use it to write something like "これは{{furi|日本|にほん}}です" where "にほん" is display in small character upper "日本". This work fine in HTML, but with Mediawiki parser the first ("これは") and the last block ("です") are into <p> tag that prevent table to be inlined.
You can see an example here: http://fr.wikipedia.org/wiki/Utilisateur:Aoineko/Test_3 And the template is here: http://fr.wikipedia.org/wiki/Mod%C3%A8le:Furi
Aoineko
On Wed, Jun 09, 2004 at 03:41:29PM +0900, Makoto & Guillaume wrote:
// this mail use UTF-8 format //
Hi all. Can you please remove the "5 same template per page" limit for small templates? Tim Starling spoke about other method to limit risk of DOS attack (based on template size), but waiting to those implementations can you deactivate the limit (or set it to 100) for tiny template (ex: less than 1kb, 256 bytes, or 100 bytes).
For example, on French WP, we use a lot of {{e}} to emulate <small><sup>e</sup></small> (it's same as the English "th" for centuries, etc.).
Other thing, I tried to make a template to be able to write Japanese furigana (small letters over kanjis to give the pronunciation) into articles. I tried this
Shouldn't UTF-8 provide the needed diacritic characters needed to compose these, without needing HTML tables?
JeLuF
Jens Frank wrote:
On Wed, Jun 09, 2004 at 03:41:29PM +0900, Makoto & Guillaume wrote:
Other thing, I tried to make a template to be able to write Japanese furigana (small letters over kanjis to give the pronunciation) into articles. I tried this
Shouldn't UTF-8 provide the needed diacritic characters needed to compose these, without needing HTML tables?
I don't think it does. The standard way of writing many Japanese words is to use kanji (or at least to partially use kanji), which are ideographs, similar to the Chinese alphabet (indeed, kanji is essentially an adapted Chinese alphabet). Since ideographic alphabets aren't phonetically-based, it's not generally possible for people who don't know a particular character to pronounce it, in the way one can "sound out" unknown words in phonetically-based alphabets. To overcome that, sometimes Japanese kanji characters are "spelled out" phonetically using the phonetic hiragana alphabet, using small characters placed either above the corresponding kanji (in horizontal text) or next to the kanji (in vertical text).
So it's really something more on the publication-layout level than on the character level, which is why it'll probably never be in Unicode, even as a combinator sort of thing.
-Mark
* Delirium delirium@hackish.org [2004-06-09 04:04]:
Jens Frank wrote:
Shouldn't UTF-8 provide the needed diacritic characters needed to compose these, without needing HTML tables?
[...]
So it's really something more on the publication-layout level than on the character level, which is why it'll probably never be in Unicode, even as a combinator sort of thing.
To be pedantic about it, there are three characters defined in Unicode for this:
U+FFF9 INTERLINEAR ANNOTATION ANCHOR U+FFFA INTERLINEAR ANNOTATION SEPARATOR U+FFFB INTERLINEAR ANNOTATION TERMINATOR
In systems that support them, <FFF9><kanji><FFFA><hiragana><FFFB> would mean the kanji with the hiragana as ruby annotation. In practice, I don't think this is implemented anywhere. It was defined more for internal use in systems that could use them, not as characters that could appear in plain text or entered by users.
On Wednesday 09 June 2004 21:05, Alexandros Diamantidis wrote:
- Delirium delirium@hackish.org [2004-06-09 04:04]:
Jens Frank wrote:
Shouldn't UTF-8 provide the needed diacritic characters needed to compose these, without needing HTML tables?
[...]
So it's really something more on the publication-layout level than on the character level, which is why it'll probably never be in Unicode, even as a combinator sort of thing.
To be pedantic about it, there are three characters defined in Unicode for this:
U+FFF9 INTERLINEAR ANNOTATION ANCHOR U+FFFA INTERLINEAR ANNOTATION SEPARATOR U+FFFB INTERLINEAR ANNOTATION TERMINATOR
In systems that support them, <FFF9><kanji><FFFA><hiragana><FFFB> would mean the kanji with the hiragana as ruby annotation. In practice, I don't think this is implemented anywhere. It was defined more for internal use in systems that could use them, not as characters that could appear in plain text or entered by users.
Though I do think that tables should be inlined, perhaps even better solution would be to add support for these characters to MediaWiki. Should it be done?
Nikola Smolenski wrote:
On Wednesday 09 June 2004 21:05, Alexandros Diamantidis wrote:
U+FFF9 INTERLINEAR ANNOTATION ANCHOR U+FFFA INTERLINEAR ANNOTATION SEPARATOR U+FFFB INTERLINEAR ANNOTATION TERMINATOR
Though I do think that tables should be inlined, perhaps even better solution would be to add support for these characters to MediaWiki. Should it be done?
This is not something MediaWiki can do. Support for Unicode control characters is up to the browsers.
Timwi
On Saturday 12 June 2004 19:36, Timwi wrote:
Nikola Smolenski wrote:
On Wednesday 09 June 2004 21:05, Alexandros Diamantidis wrote:
U+FFF9 INTERLINEAR ANNOTATION ANCHOR U+FFFA INTERLINEAR ANNOTATION SEPARATOR U+FFFB INTERLINEAR ANNOTATION TERMINATOR
Though I do think that tables should be inlined, perhaps even better solution would be to add support for these characters to MediaWiki. Should it be done?
This is not something MediaWiki can do. Support for Unicode control characters is up to the browsers.
We know that most (all?) browsers don't support it. Why not doing it when it's as simple as
preg_replace( array( "/(.*)(.*)/", "/(.*)(.*)/" ), "<table style='display:inline;'><tr><td><small>$2</small></td></tr><tr><td>$1</td></tr></table>", $text);
?
Nikola Smolenski wrote:
On Wednesday 09 June 2004 21:05, Alexandros Diamantidis wrote:
To be pedantic about it, there are three characters defined in Unicode for this:
U+FFF9 INTERLINEAR ANNOTATION ANCHOR U+FFFA INTERLINEAR ANNOTATION SEPARATOR U+FFFB INTERLINEAR ANNOTATION TERMINATOR
In systems that support them, <FFF9><kanji><FFFA><hiragana><FFFB> would mean the kanji with the hiragana as ruby annotation. In practice, I don't think this is implemented anywhere. It was defined more for internal use in systems that could use them, not as characters that could appear in plain text or entered by users.
Though I do think that tables should be inlined, perhaps even better solution would be to add support for these characters to MediaWiki. Should it be done?
Unicode support is done at the browser level, so support for these characters would have to be added to IE and Mozilla in order for them to display properly. It *could* be done at the MediaWiki level, translating these Unicode characters into an HTML table approximation, but that would be a little bit strange.
-Mark
Makoto & Guillaume wrote:
// this mail use UTF-8 format //
Hi all. Can you please remove the "5 same template per page" limit for small templates? Tim Starling spoke about other method to limit risk of DOS attack (based on template size), but waiting to those implementations can you deactivate the limit (or set it to 100) for tiny template (ex: less than 1kb, 256 bytes, or 100 bytes).
For example, on French WP, we use a lot of {{e}} to emulate <small><sup>e</sup></small> (it's same as the English "th" for centuries, etc.).
Hello,
Also have a look at this bug report: http://sourceforge.net/tracker/?func=detail&atid=411192&aid=967833&a...
Makoto & Guillaume wrote:
// this mail use UTF-8 format //
So? :-)
Can you please remove the "5 same template per page" limit for small templates?
Whoa. I didn't know such a thing existed. Why is it a problem to have many copies of the *same* template on one page? You only need to load it once.
Timwi
Makoto & Guillaume wrote:
// this mail use UTF-8 format //
Hi all. Can you please remove the "5 same template per page" limit for small templates? Tim Starling spoke about other method to limit risk of DOS attack (based on template size), but waiting to those implementations can you deactivate the limit (or set it to 100) for tiny template (ex: less than 1kb, 256 bytes, or 100 bytes).
For example, on French WP, we use a lot of {{e}} to emulate <small><sup>e</sup></small> (it's same as the English "th" for centuries, etc.).
Other thing, I tried to make a template to be able to write Japanese furigana (small letters over kanjis to give the pronunciation) into articles. I tried this
Why not use {{susbt:e}} ? OK it's a bit longer to write.
-- Looxix
From: "Luc Van Oostenryck"
Makoto & Guillaume wrote:
// this mail use UTF-8 format //
Hi all. Can you please remove the "5 same template per page" limit for small templates? Tim Starling spoke about other method to limit risk of DOS attack (based
on
template size), but waiting to those implementations can you deactivate
the
limit (or set it to 100) for tiny template (ex: less than 1kb, 256
bytes, or
100 bytes).
For example, on French WP, we use a lot of {{e}} to emulate <small><sup>e</sup></small> (it's same as the English "th" for
centuries,
etc.).
Why not use {{susbt:e}} ? OK it's a bit longer to write.
-- Looxix
It is longer than {{e}} **and** it put a lot of HTML code into the article that make it difficult to read for next people who want edit it. It's not just a feature to help writing, but also to make articles more clean.
Aoineko
wikitech-l@lists.wikimedia.org