I currently maintain the PHP Typography project and the WordPress port of this project wp-Typography (http://wordpress.org/extend/plugins/wp-typography/)
The Drupal port will be named dru-Typography. A near final version of the module is available - upon request - for review.
The PHP Typography project does duplicate a subset of the functionality found in the Typogrify module (although it is off by defualt). Specifically, this module will add select CSS hooks for styling (but not the ligature or arrow replacement functionality). The adding of CSS hooks will be OFF by default. The reason its inclusion is three-fold:
First, the Typogrify module is a port of the PHP Typogrify project by Hamish McPherson (http://blog.hamstu.com/2009/01/30/wp-typogrify-merging-and-moving/). I have assumed responsibility for this parent project. After a ground-up rewrite, and merging significant new functionality, it has become PHP Typography. This new project's main feature is automatic hyphenation - not found in any other Drupal module. However, it does maintain the legacy Typogrify CSS hooks.
Second, Hyphenation requires extensive parsing of the text (as does the Typogrify module). As such, it is unnecessary to parse twice when both functions can occur during the same parsing operation. Inclusion of the typogrify functionality has significant performance advantages (for those who desire both functions).
Third, this is a port of a non-drupal-specific project. Separation of Typogrify functionality (to avoid competition) would be time consuming and unnecessarily complicate future updates (as the parent project evolves).
But to repeat... the main functionality of this module is automatic server-side hyphenation of text, which is not available in any other module. The Typogrify-like functionality will be off by default.
It should also be mentioned that maintenance of a separate Typogrify module is desirable, in that, for those who want the Typogrify functionality without hyphenation, they will not be bogged down with the extra processing required for hyphenation. Typogrify is a streamlined module that should not be burdened with the extra weight of the proposed dru-Typography module.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | dru_typography.zip | 563.62 KB | kingjeffrey |
Comments
Comment #1
kingjeffrey commentedComment #2
avpadernoI am not sure we should accept a module that has the same purpose of an already existing one.
Comment #3
timmillwoodI was just about the start writing this module.
@KiamLaLuno, can you give a link to the already existing one?
Comment #4
avpadernoTypogrify.
Comment #5
ajk commentedComment #6
kingjeffrey commentedWhile there is some shared scope, I do not believe it accurate to state it "has the same purpose of an already existing one". The core functionality of the plugin is automatic hyphenation. No other module offers that functionality or purpose.
The reason there is some shared functionality is that this is a port of a generalized PHP project to Drupal. The mother project includes the similar functionality to the Typogrify module.
Also, the overlapping functionality is not identical. For example:
1) dru-Typography allows application of CSS hooks in a context sensitive manner. Specifically, it allows you to define HTML elements, id's and classes which should not be processed. Typogrify does not offer this capability.
2) if an ampersand is already wrapped in a <span class="amp">, Typogrify will wrap it again. dru-Typography will not.
3) dru-Typography allows you to wrap all digits in a <span class="numbers">, Typogrify does not.
In addition to hyphenation, dru-Typography offers features Typogrify does not:
1) smart character replacement for: fractions, math symbols, numeric ordinals, primes, french and german quotes
2) Granual widow control where you can specify the length of widows to protect and words to pull from the previous line to keep them company
3) Forced wrapping of hard-hyphenated words, long URLs and emails
4) prohibits phone numbers from being broken up onto different lines
In three weeks, the WordPress port of this has been downloaded more than 11K times. In 1.5 years, the WordPress port of Typogrify has been downloaded just over 6K times.
The features of this plugin are vastly beyond that of the Typogrify module, the core functionality is unique from the Typogrify module, the demand far exceeds that of the Typogrify module.
I believe acceptance of this module is in the best interest of the Drupal community. Please give this due consideration. Thanks.
Comment #7
avpadernoSee what reported in Apply for contributions CVS access, which states:
The module you propose is an extension to Typography, and you should do what reported above; you should offer to the current maintainer of Typography to become co-maintainer of his module.
Comment #8
kingjeffrey commentedIt is a project that began with the transfer of the responsibilities of the PHP Typogrify project's ongoing maintenance to me. It resulted in a ground up rewrite and rethinking of the entire project, to the point that it bears very little resemblance to the original project.
I would point out that Apply for contributions CVS access uses the words "are often" and not "are always". If this was a clone of the Typogrify module, I would agree. This is a radical step beyond. It is revolution, not evolution. Please compare the code base of the two projects. They are not related. Please compare the functionality. The are related only on the periphery.
To apply the PHP Typography project to the Typogrify module, it would require a complete abandon of the Typogrify code. It would seem silly to require evolution of an existing project, that is not capable of that evolution without starting over. It would literally be the same project in name only. But then, that would cause additional confusion, because the Typogrify name relates to the Christian Metts' original (Django based) Typogrify project (see http://code.google.com/p/typogrify/). This project has little relation to the PHP Typography project (see http://kingdesk.com/projects/php-typography/) that the proposed dru-Typography project is based on.
The value of this plugin should be plain. Even above in this thread, timmillwood expressed interest in porting the PHP Typography project to Drupal. With timmillwood having come out of Mark Boulton Design, and Mark Boulton Design being integrally involved in the redesign of Drupal 7, that has to say something about the value of this proposed module.
As a related aside. Mark Boulton has used WordPress in the recent design of his personal blog (http://www.markboulton.co.uk/). Guess what typography plugin he is using for the hyphenation on that website? wp-Typography, the WordPress port of the PHP Typography project.
It would be a shame if this tool was not available to Drupal users because of some non-compete concept that protects an unrelated project.
Comment #9
avpadernoThe project page of Typogrify reports that:
Remember that files available from third-party web sites are not allowed in Drupal repository.
Your application has been approved.
Comment #10
kingjeffrey commentedThank you.
Comment #12
avpaderno