Comments on: wp-Hyphenate 1.07 beta http://kingdesk.com/projects/wp-hyphenate/ web design Tue, 31 Aug 2010 16:02:16 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: 3 Extensiones Wordpress para tipografías | pixelco.us blog http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-564 3 Extensiones Wordpress para tipografías | pixelco.us blog Sun, 09 Aug 2009 00:49:31 +0000 http://kingdesk.com/?p=102#comment-564 [...] Web:  kingdesk.com/projects/wp-hyphenate [...] […] Web:  kingdesk.com/projects/wp-hyphenate […]

]]> By: wp-Typography | Jeff Siarto http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-410 wp-Typography | Jeff Siarto Wed, 08 Jul 2009 05:04:41 +0000 http://kingdesk.com/?p=102#comment-410 [...] This is the follow‐​up plu­gin to wp‐​Hyphenate (used on this site and one of my favorites) and rep­re­sents the best solu­tion for improved [...] […] This is the follow‐​up plu­gin to wp‐​Hyphenate (used on this site and one of my favorites) and rep­re­sents the best solu­tion for improved […]

]]> By: Jeffrey D. King http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-382 Jeffrey D. King Sat, 04 Jul 2009 08:04:51 +0000 http://kingdesk.com/?p=102#comment-382 This plugin is discontinued and replaced by the <a href="http://kingdesk.com/projects/php-typography/" rel="nofollow">wp-Typography</a> plugin. We learned a lot from this plugin, and wp-Typography is the realization this plugin's potential. Enjoy! This plugin is discontinued and replaced by the wp-Typography plugin. We learned a lot from this plugin, and wp-Typography is the realization this plugin’s potential. Enjoy!

]]> By: erz http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-381 erz Tue, 30 Jun 2009 15:53:04 +0000 http://kingdesk.com/?p=102#comment-381 @Jeffrey D. King Great to hear you are making progress. And that you made the functionalities of the plugin optional is just swell. Now I cannot wait to put my hands on your optimized version. Arrgh, the suspense... @Jeffrey D. King

Great to hear you are making progress. And that you made the functionalities of the plugin optional is just swell. Now I cannot wait to put my hands on your optimized version. Arrgh, the suspense…

]]> By: Jeffrey D. King http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-380 Jeffrey D. King Mon, 29 Jun 2009 15:44:25 +0000 http://kingdesk.com/?p=102#comment-380 @erz #42 <p>There is progress. I have a working draft, but I am refining the code to improve performance. I'm not entirely pleased with it's current processing requirements. </p> <p>As far as foreign language support, the combined plugin will support the same languages and the admin interface will once again be <a href="http://codex.wordpress.org/Writing_a_Plugin#Internationalizing_Your_Plugin" rel="nofollow">internationalized</a>.</p> <p>Lastly, the admin interface will allow you to disable any feature you do not want to use (including the typogrify features).</p> @erz #42

There is progress. I have a working draft, but I am refining the code to improve performance. I’m not entirely pleased with it’s current processing requirements.

As far as foreign language support, the combined plugin will support the same languages and the admin interface will once again be internationalized.

Lastly, the admin interface will allow you to disable any feature you do not want to use (including the typogrify features).

]]> By: erz http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-379 erz Mon, 29 Jun 2009 09:35:33 +0000 http://kingdesk.com/?p=102#comment-379 Thanks a lot for your work and efforts. Rest assured that I am promoting this plugin among the few developers I know (and hopefully in an upcoming article on Web-Typography as well). I was wondering how the work on the update is progressing - not so much in terms of a release date, but more in terms of functionality for foreign language users. The integration with the Typogrify-Plugin might be a boon to some, but a burden to others. Since I use a typographic plugin that is tailormade for German ("typographical improvements" with minor tweaks), I am wondering if the upgrade might prove detrimental to my setup, as I did not find wp-typogrify as fitting for my needs. All the best, erz Thanks a lot for your work and efforts. Rest assured that I am promoting this plugin among the few developers I know (and hopefully in an upcoming article on Web-Typography as well).

I was wondering how the work on the update is progressing – not so much in terms of a release date, but more in terms of functionality for foreign language users.

The integration with the Typogrify-Plugin might be a boon to some, but a burden to others. Since I use a typographic plugin that is tailormade for German (“typographical improvements” with minor tweaks), I am wondering if the upgrade might prove detrimental to my setup, as I did not find wp-typogrify as fitting for my needs.

All the best,
erz

]]> By: basambora http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-372 basambora Thu, 30 Apr 2009 16:11:20 +0000 http://kingdesk.com/?p=102#comment-372 Jeffrey, I see your point regarding the non-destructive changes, this means that the only way to enable the use of large language patters are: 1. using caching, this saves a bit of processing power, but on-the-fly processing is still needed sometimes 2. saving the original content and the parsed seperately, saves the processing power and response times are increased, though it requires a rather big change of your plugin (if possible at all) and it requires over 2 times as much data to be saved. So I guess I'll settle with the first option :) I also had a look at the tex files and their php counterparts, seems to me the conversion can be automated quite well, but I don't fully understand your format (nor the tex format), i.e. the begin, end and all arrays and also the dots in the tex patters. Could you clarify this for me? Greetings, Basambora Jeffrey, I see your point regarding the non-destructive changes, this means that the only way to enable the use of large language patters are:
1. using caching, this saves a bit of processing power, but on-the-fly processing is still needed sometimes
2. saving the original content and the parsed seperately, saves the processing power and response times are increased, though it requires a rather big change of your plugin (if possible at all) and it requires over 2 times as much data to be saved.

So I guess I’ll settle with the first option :)

I also had a look at the tex files and their php counterparts, seems to me the conversion can be automated quite well, but I don’t fully understand your format (nor the tex format), i.e. the begin, end and all arrays and also the dots in the tex patters. Could you clarify this for me?

Greetings,
Basambora

]]> By: Reinis I. http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-370 Reinis I. Sun, 26 Apr 2009 15:00:46 +0000 http://kingdesk.com/?p=102#comment-370 I'd like to comment that the current JS part of wp-Hyphenate is much too bloated. It could easily be stripped down to a couple of lines and the external file dropped. I've modified mine to use IE's conditional comments. I’d like to comment that the current JS part of wp-Hyphenate is much too bloated. It could easily be stripped down to a couple of lines and the external file dropped. I’ve modified mine to use IE’s conditional comments.

]]> By: Jeffrey D. King http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-367 Jeffrey D. King Mon, 20 Apr 2009 19:31:57 +0000 http://kingdesk.com/?p=102#comment-367 @basambora #38 I have purposefully avoided destructive alteration of data. This is for many reasons. It would break spell check when editing articles. If someone wants to turn off the plugin, articles would remain hyphenated. If there is a bug in my code, thousands of people would be knocking on my door because I just corrupted their entire archive. It is best practice to avoid destructive change to data, and I plan on continuing that practice with this plugin. The Dutch language pattern consists of nearly 14,000 patterns. In my early experiments with other languages, such pattern sizes caused unacceptable delay for processing time. I never bothered formatting the Dutch patterns for wp-hyphenate integration. You can look at the original Dutch TeX pattern <a href="http://mirror.unl.edu/ctan/language/hyph-utf8/tex/generic/hyph-utf8/patterns/hyph-nl.tex" rel="nofollow">here</a>. If you want to go to the trouble of formatting this, I would happily include it in the next release. @basambora #38

I have purposefully avoided destructive alteration of data. This is for many reasons. It would break spell check when editing articles. If someone wants to turn off the plugin, articles would remain hyphenated. If there is a bug in my code, thousands of people would be knocking on my door because I just corrupted their entire archive.

It is best practice to avoid destructive change to data, and I plan on continuing that practice with this plugin.

The Dutch language pattern consists of nearly 14,000 patterns. In my early experiments with other languages, such pattern sizes caused unacceptable delay for processing time. I never bothered formatting the Dutch patterns for wp-hyphenate integration. You can look at the original Dutch TeX pattern here. If you want to go to the trouble of formatting this, I would happily include it in the next release.

]]> By: basambora http://kingdesk.com/projects/wp-hyphenate/comment-page-2/#comment-366 basambora Sun, 19 Apr 2009 13:57:58 +0000 http://kingdesk.com/?p=102#comment-366 Hi, nice plugin, I do have a question though: Would it be possible to parse the post before storing it in the database? This way you don't generate unnecessary overhead and the plugin won't affect the page loading times. Greetings, basambora By the way: will Dutch ever be implemented? Hi, nice plugin, I do have a question though:
Would it be possible to parse the post before storing it in the database? This way you don’t generate unnecessary overhead and the plugin won’t affect the page loading times.

Greetings,
basambora

By the way: will Dutch ever be implemented?

]]>