Databases
StackOverflow2013
Postsdbo
POParsing HTML to fix microtypography & glyph issues
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POParsing HTML to fix microtypography & glyph issues
    primarykey
    data
    text
    <p>I'm interested in <a href="http://en.wikipedia.org/wiki/Microtypography" rel="nofollow noreferrer">microtypography</a> issues on the web.</p> <p>I want a tool to fix:</p> <ul> <li>Quotes <ul> <li>“ (&amp;#8220;) opening quote (instead of ")</li> <li>” (&amp;#8221;) closing quote (instead of ")</li> </ul></li> <li>Apostrophe <ul> <li>’ (&amp;#8217;) apostrophe (instead of ')</li> </ul></li> <li>Dashes and Hyphens <ul> <li>– (&amp;#8211; or &amp;ndash;) en dash, used for ranges, e.g. “13–15 November” (instead of -)</li> <li>— (&amp;#8212; or &amp;mdash;) em dash, used for change of thought, e.g. “Star Wars is—as everyone knows—amazing.” (instead of -, or --)</li> </ul></li> <li>Ellipsis <ul> <li>… (&amp;#8230; or &amp;hellip;) horizontal ellipsis, used to indicate an omission or a pause (instead of ...)</li> </ul></li> <li>And more \o/</li> </ul> <p>All those fixes depend on the content language. In French, for example, we must add a insecable (non-breaking) space before every composed glyph (<code>:</code>, <code>;</code>, <code>…</code>, <code>?</code>, <code>!</code>, ...), and our quotes are « like this ».</p> <p>There are many constraints for such a tool:</p> <ul> <li>it must not edit any HTML inside protected tags (<code>pre</code>, <code>code</code>...)</li> <li>it must be fast (used on a CMS output)</li> <li>it must not break the HTML</li> <li>and so on.</li> </ul> <p>There already are some tools on the market:</p> <ul> <li><a href="http://michelf.ca/projects/php-smartypants/typographer/" rel="nofollow noreferrer">http://michelf.ca/projects/php-smartypants/typographer/</a></li> <li><a href="http://kingdesk.com/projects/php-typography/" rel="nofollow noreferrer">http://kingdesk.com/projects/php-typography/</a></li> <li><a href="http://code.google.com/p/typogrify/" rel="nofollow noreferrer">http://code.google.com/p/typogrify/</a></li> </ul> <p>They are all more or less based on SmartyPants, a 2005 lib, not tested, not documented, parsing HTML manually and not dealing with other rules than English. Hell no.</p> <p>So my questions are:</p> <ul> <li>Do you know of any decent tool like this?</li> <li>How can I do it? I already have a POC using <a href="http://symfony.com/doc/current/components/dom_crawler.html" rel="nofollow noreferrer">DomCrawler</a> but I'm not convinced. What's the best way to parse and edit HTML in PHP?</li> </ul> <hr> <p><strong>Edit July 2013</strong>: I have developed <a href="https://github.com/jolicode/JoliTypo" rel="nofollow noreferrer">JoliTypo</a> from the tests and expertise I gained with this issue. No existing lib was doing what I wanted to do.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDamien
    1. USDamien
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POParsing HTML to fix microtypography & glyph issues
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POParsing HTML to fix microtypography & glyph issues
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POParsing HTML to fix microtypography & glyph issues
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGreat question, although I'm wondering if this isn't the sort of thing it would be better to process at the point where the data is saved, rather than the point where it is output? Especially if you have a lot of text (which is the case where this would be the most useful), it's hard to imagine processing for details (like distinguishing between appropriate em and en dash usage) in a manner efficient enough so that it won't drastically increase page loading times.
      singulars
      1. POParsing HTML to fix microtypography & glyph issues
      1. USMichael Schuller
    2. CO@MichaelCSchuller This should be handled by a cache system IMO. I think editing user submitted content and persisting it is a bad idea as there is no way to get the type-writed version back. Storing both the user and the converted text can be a solution for performance related issues.
      singulars
      1. POParsing HTML to fix microtypography & glyph issues
      1. USDamien
    3. COThat of course runs the risk of making the output's relationship to the input somewhat opaque to the user who is entering the original text, but I suppose that's a philosophical, rather than a technical question. One reason why I think things like Markdown are such a good solution for formatting text input is that you know exactly what transformations will be applied (and you can get back the original as it was entered, as you say).
      singulars
      1. POParsing HTML to fix microtypography & glyph issues
      1. USMichael Schuller
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload