diff --git a/test/unit/page_renderer_test.rb b/test/unit/page_renderer_test.rb
index cbea5c43..c690087c 100644
--- a/test/unit/page_renderer_test.rb
+++ b/test/unit/page_renderer_test.rb
@@ -45,7 +45,7 @@ class PageRendererTest < ActiveSupport::TestCase
end
def test_wiki_links_after_empty
- assert_markup_parsed_as(%{\n
This is a wikilink\n This is a wikilink?. This <IMG SRC='http://hobix.com/sample.jpg' alt=''/> is an inline image link. This <IMG SRC='http://hobix.com/sample.jpg' alt=''></IMG> is an inline image link. That’s some text with a footnote 1 and another 2 and another 3. This is not a footnote. And that’s the footnote. This is second sentence (same paragraph). ↩ This is the very long one. One One This page does not utilize This page does not utilize Please mouseover to see the title: Please mouseover to see the title: Please mouseover to see the title: Please mouseover to see the title: I’ll say it one more time: this page does not use I’ll say it one more time: this page does not use This is double size: This is double size: This is an . This is an . This is an . This is an . Result on span: Result on span: Result alone: Without closing:
This is Paragraph (1 space after), list with no space: * ciao Paragraph (2 spaces after), list with no space: Paragraph (2 spaces after), list with no space: Paragraph (3 spaces after), list with no space: Paragraph (3 spaces after), list with no space: Paragraph with block quote: Paragraph with html after Paragraph with html after Paragraph with html after, indented: Emphasis Paragraph (1 space after), list with no space: * ciao Paragraph (2 spaces after), list with no space: Paragraph (2 spaces after), list with no space: Paragraph (3 spaces after), list with no space: Paragraph (3 spaces after), list with no space: Paragraph with block quote: Paragraph 2 Paragraph 3 Paragraph 4 Paragraph Br-> Paragraph 3 Paragraph 4 Paragraph Br-> I’m a big fan of typography in general. If you check out my homepage or my contact elliottcable page, and you’re using Safari/WebKit or Opera/Kestrel, you’ll notice the typefaces (fonts, as colloquialized) are very non-standard. (As of this writing, I’m using Museo and Diavlo1 heavily on both.) I’m a big fan of typography in general. If you check out my homepage or my contact elliottcable page, and you’re using Safari/WebKit or Opera/Kestrel, you’ll notice the typefaces (fonts, as colloquialized) are very non-standard. (As of this writing, I’m using Museo and Diavlo1 heavily on both.) The internet has not be a friendly place for typohiles like myself, up to this point, at least. One might even say it was a frightful, mentally scarring environment for those akin to yours truly. We’ve been restricted to reading page after page after page on day after day after day for year after year after year abominations of markup and design enslaved by the horrible overlords we know as Lucida, Verdana, Arial, Helvetica, Geneva, Georgia, Courier, and… dare I invoke ye, thou my terrible overlord? Times New Roman. Wherefore art thou, my glorious Archer? And thee as well, my beautiful Garamond? The technical restrictions of that horrible monster we know as the Web Browser hath forced us all too long to use those most banal, those most common, and those most abused, out of all of the typefaces of the world. All hyperbole aside, I’m extremely happy to see the advent of a standard All hyperbole aside, I’m extremely happy to see the advent of a standard Now, onwards to the topic of my post as declared in the header (yes, I know, a slow start - but it’s an interesting topic with an interesting history!). WebKit, the open source rendering engine behind the wonderfulness that is Safari, and how it handles the ‘new’ To put it simply, and to be very blunt, it’s broken. The CSS spec section for The CSS spec section for As you can see, my headings should use the typeface defined in The implication here is that, to make Isn’t it horrible? Seriously, my eyes, they bleed. There’s lots of problems with this far beyond the lack of semanticity when it comes to the typeface names… let me see how many ways this breaks the purpose of As soon as we begin to use Also, many default elements are destroyed, unusable, without ‘fixing’ - for instance, Also, many default elements are destroyed, unusable, without ‘fixing’ - for instance, If we want to use Javascript to modify the display of the content, we can’t simply adjust the mentioned textual control attributes - we have to know and change the entire You make us very wet. And by wet, I mean ‘not DRY’. What if we decide to change one of the bastardized font names? Or use a different font entirely? We have to go through all of our CSS, all of our Javascript, and make sure we update every occurrence of the typeface’s bastardized name. And by wet, I mean ‘not DRY’. What if we decide to change one of the bastardized font names? Or use a different font entirely? We have to go through all of our CSS, all of our Javascript, and make sure we update every occurrence of the typeface’s bastardized name. In summary… come on, WebKit team, this isn’t like you - you’re always the ones with the closest-to-standard implementation, and the cleanest code, and… hell, overall? Webkit is the most secure/fastest browser available. But this is making me lose my faith in you, guys, please get it right. You’re pioneering a leap into the future when it comes to the Web - this is as important, or more important, than Mosiac’s allowing of images was. To put it succinctly - don’t fuck this up, y’all. CSS: Cascading Style Sheets.EOT: Embedded OpenType 3: To give Microsoft a little credit, something I rarely do… Yes, I’m aware Microsoft submitted EOT to the W3C as a proposal - the problem isn’t with their attempts to make it non-proprietary, but with the basic concept of making typefaces on the web DRMed. Look what such attempts have done to the music and video industry - simply decimated it. Do we really want to see the same thing happen to our beloved medium as typography moves into the 21st century? W3C: World Wide Web Consortium These are fonts by Jos Buivenga, quite the amazing person. His (free) fonts are, uniquely, released for use on the web in To give Microsoft a little credit, something I rarely do… Yes, I’m aware Microsoft submitted EOT to the W3C as a proposal - the problem isn’t with their attempts to make it non-proprietary, but with the basic concept of making typefaces on the web DRMed. Look what such attempts have done to the music and video industry - simply decimated it. Do we really want to see the same thing happen to our beloved medium as typography moves into the 21st century? ↩ This is ruby code: Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Break: Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Break:\n\nThis is a [[wikilink]].")
end
@@ -55,7 +55,7 @@ class PageRendererTest < ActiveSupport::TestCase
"would be My Way " +
" in kinda " +
+ "
+
*** Output of to_latex ***
\vspace{.5em} \hrule \vspace{.5em}
diff --git a/vendor/plugins/maruku/spec/block_docs/html2.md b/vendor/plugins/maruku/spec/block_docs/html2.md
index 5bb70312..114f6710 100644
--- a/vendor/plugins/maruku/spec/block_docs/html2.md
+++ b/vendor/plugins/maruku/spec/block_docs/html2.md
@@ -12,8 +12,8 @@ md_el(:document,[
md_html("")
],{},[])
*** Output of to_html ***
-
-<p>here's an apostrophe & a quote "</p>
+<p>here's an apostrophe & a quote "</p>
-<p>here's an apostrophe & a quote "</p>
+<p>here's an apostrophe & a quote "</p>
-<p>here's an apostrophe & a quote "</p>
+<p>here's an apostrophe & a quote "</p>
*** Output of to_latex ***
{\colorbox[rgb]{1.00,0.93,1.00}{\tt \char60p\char62here\char39s~an~apostrophe~\char38~a~quote~\char34\char60\char47p\char62}}
diff --git a/vendor/plugins/maruku/spec/block_docs/images.md b/vendor/plugins/maruku/spec/block_docs/images.md
index 3fb25f8a..e3122974 100644
--- a/vendor/plugins/maruku/spec/block_docs/images.md
+++ b/vendor/plugins/maruku/spec/block_docs/images.md
@@ -52,15 +52,15 @@ md_el(:document,[
md_ref_def("css2", "http://jigsaw.w3.org/css-validator/images/vcss", {:title=>"Optional title attribute"})
],{},[])
*** Output of to_html ***
-<p>here's an apostrophe & a quote "</p>
-<img src="http://jigsaw.w3.org/css-validator/images/vcss"/>
* ciao
* ciao
* ciao
* ciaoheader
-
")],{},[])
*** Output of to_html ***
-
+
*** Output of to_latex ***
*** Output of to_md ***
diff --git a/vendor/plugins/maruku/spec/block_docs/notyet/triggering.md b/vendor/plugins/maruku/spec/block_docs/notyet/triggering.md
index 0c04644b..160f04ae 100644
--- a/vendor/plugins/maruku/spec/block_docs/notyet/triggering.md
+++ b/vendor/plugins/maruku/spec/block_docs/notyet/triggering.md
@@ -74,9 +74,9 @@ md_el(:document,[
* ciao
* ciao
* ciao
* ciao
Paragraph 5
Paragraph 51 2
-A X
+B X
*** Output of to_latex ***
\begin{tabular}{l|l|l}
diff --git a/vendor/plugins/maruku/spec/block_docs/red_tests/abbrev.md b/vendor/plugins/maruku/spec/block_docs/red_tests/abbrev.md
index 174900a4..14ecdb1c 100644
--- a/vendor/plugins/maruku/spec/block_docs/red_tests/abbrev.md
+++ b/vendor/plugins/maruku/spec/block_docs/red_tests/abbrev.md
@@ -381,40 +381,40 @@ md_el(:document,[
md_ref_def("spec", "http://?>", {:title=>") *[DRY]: Don"})
],{},[])
*** Output of to_html ***
-1 2
+A X B X WebKit (Safari 3.1) and the CSS @font-face declaration
+WebKit (Safari 3.1) and the CSS @font-face declaration
-@font-face
declaration in CSS. Internet Explorer first implemented a crutched, basic version of this way back in version 4, but nothing ever really came of it - their decision to create the proprietary .EOT2 format to appease overly restrictive type foundries’ worries about intellectual property (aka. the cold, hard dominatrix that we know only as Ms. Profit) truly and completely killed that initial attempt at bringing astute typography and it’s advocates to the web. This new run at @font-face
by an established, trusted, and open group (the W3C itself, responsible for helping to make much of what we use as designers on the web standard and cross-system compatible) has a much better chance, in my humble opinion - and I am quite looking forward to the consequences if it succeeds.@font-face
declaration in CSS. Internet Explorer first implemented a crutched, basic version of this way back in version 4, but nothing ever really came of it - their decision to create the proprietary .EOT2 format to appease overly restrictive type foundries’ worries about intellectual property (aka. the cold, hard dominatrix that we know only as Ms. Profit) truly and completely killed that initial attempt at bringing astute typography and it’s advocates to the web. This new run at @font-face
by an established, trusted, and open group (the W3C itself, responsible for helping to make much of what we use as designers on the web standard and cross-system compatible) has a much better chance, in my humble opinion - and I am quite looking forward to the consequences if it succeeds.@font-face
declaration. No, it’s not really ‘new’, but yes, it feels like it is.@font-face
is very specific - typefaces are to be selected based on a wide array of criteria placed in the @font-face
declaration block itself. Various textual CSS attributes may be defined within the @font-face
declaration, and then they will be checked when the typeface is referred to later in the CSS. For instance, if I have two @font-face
declarations for the Diavlo family - one for regular text, and one for a heavier weighted version of the typeface - then I later utilize Diavlo in a font-family:
attribute, it should refer to the basic Diavlo font defined in the first @font-face
. However, if I were to do the same, but also specify a heavy font-weight:
, then it should use the heavier version of Diavlo. To place this example in code:@font-face
is very specific - typefaces are to be selected based on a wide array of criteria placed in the @font-face
declaration block itself. Various textual CSS attributes may be defined within the @font-face
declaration, and then they will be checked when the typeface is referred to later in the CSS. For instance, if I have two @font-face
declarations for the Diavlo family - one for regular text, and one for a heavier weighted version of the typeface - then I later utilize Diavlo in a font-family:
attribute, it should refer to the basic Diavlo font defined in the first @font-face
. However, if I were to do the same, but also specify a heavy font-weight:
, then it should use the heavier version of Diavlo. To place this example in code:@font-face {
- font-family: 'Diavlo';
- src: url(./Diavlo/Diavlo_Book.otf) format("opentype");
+ font-family: 'Diavlo';
+ src: url(./Diavlo/Diavlo_Book.otf) format("opentype");
}
@font-face {
- font-family: 'Diavlo';
+ font-family: 'Diavlo';
font-weight: 900;
- src: url(./Diavlo/Diavlo_Black.otf) format("opentype");
+ src: url(./Diavlo/Diavlo_Black.otf) format("opentype");
}
h1, h2, h3, h4, h5, h6 {
- font-family: 'Diavlo';
+ font-family: 'Diavlo';
font-weight: 900;
}
div#content {
- font-family: 'Diavlo';
+ font-family: 'Diavlo';
}
Diavlo_Black.otf
, while my body content should use Diavlo_Book.otf
. However, in WebKit, this doesn’t work - it completely ignores any attribute except font-family:
and src:
in a @font-face
declaration! Completely ignores them! Not only that - not only that - it disregards all but the last @font-face
for a given font-family:
attribute string!@font-face
work as it is currently implemented in WebKit (and thus, Safari 3.1), I have to declare completely imaginary, non-existent type families to satisfy WebKit alone. Here’s the method I have used in the places I current implement @font-face
:@font-face {
- font-family: 'Diavlo Book';
- src: url(./Diavlo/Diavlo_Book.otf) format("opentype");
+ font-family: 'Diavlo Book';
+ src: url(./Diavlo/Diavlo_Book.otf) format("opentype");
}
@font-face {
- font-family: 'Diavlo Black';
- src: url(./Diavlo/Diavlo_Black.otf) format("opentype");
+ font-family: 'Diavlo Black';
+ src: url(./Diavlo/Diavlo_Black.otf) format("opentype");
}
h1, h2, h3, h4, h5, h6 {
- font-family: 'Diavlo Black';
+ font-family: 'Diavlo Black';
}
div#content {
- font-family: 'Diavlo Book';
+ font-family: 'Diavlo Book';
}
@font-face
:@font-face
in our page, we can no longer make any use of any other textual control attribute - font-weight:
, font-style:
, and font-variant:
are no longer available to us, because they no longer correctly map to technical typeface variant/features.<b>
would have no effect in a page styled for WebKit as above; We would have to specify something like b {font-family: 'Diavlo Black';}
- how broken is that? Unless we caught all such default elements and re-styled them to use the bastardized names instead of the correct attributes, lots of basic HTML formatting would be broken. I myself may never use in-document formatting (separation of design and content!), but what about comments forms? Forum posts? Direct HTML-literal quotes?<b>
would have no effect in a page styled for WebKit as above; We would have to specify something like b {font-family: 'Diavlo Black';}
- how broken is that? Unless we caught all such default elements and re-styled them to use the bastardized names instead of the correct attributes, lots of basic HTML formatting would be broken. I myself may never use in-document formatting (separation of design and content!), but what about comments forms? Forum posts? Direct HTML-literal quotes?font-family:
array of strings.@font-face
declarations - unlike the vast majority of other (even free to download) typefaces, which have ridiculously restricting licenses and terms of use statements. Props, Jos - you’re a pioneer, and deserve recognition as such. ↩
+require 'maruku'
require 'maruku'
*** Output of to_latex ***
diff --git a/vendor/plugins/maruku/spec/block_docs/wrapping.md b/vendor/plugins/maruku/spec/block_docs/wrapping.md
index 8b6c5333..b5d952d6 100644
--- a/vendor/plugins/maruku/spec/block_docs/wrapping.md
+++ b/vendor/plugins/maruku/spec/block_docs/wrapping.md
@@ -29,10 +29,10 @@ md_el(:document,[
],{},[])
],{},[])
*** Output of to_html ***
-puts Maruku.new($stdin).to_html
Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet.
Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet.
-
Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet
Lorem ipsum dolor amet. Lorem ipsum dolor amet. Lorem ipsum dolor amet