Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Plugin Author e2b

    (@e2b)

    Hyphenator doesn’t chance quotation, it only adds possible break points for hyphenation when rendered by the browser. Do you also use some typography plugins?

    Forum: Plugins
    In reply to: [Hyphenator] Not Working?
    Plugin Author e2b

    (@e2b)

    There is some syntax error at your source code, maybe that’s the problem and blocking JS from being executed:

    <link rel="shortcut icon" href="http://1"><link rel="apple-touch-icon-precomposed" href="http://1"><meta name="msapplication-TileColor" content="1"><meta name="msapplication-TileImage" content="1"><script><script> (line 810)

    Plugin Author e2b

    (@e2b)

    Alright, thank you. 🙂 Anything specific? So far the only thing is having a minimum length for hyphenated slices or only slice at more common points.

    Plugin Author e2b

    (@e2b)

    • I don’t see how adding additional classes that are only used for Hyphenator might be a problem for your website besides from having the overhead in code. Design etc. shouldn’t be affected.
    • Exceptions allow you to define custom positions for hyphens, too. So a word is hyphenated only at the positions you provided. E.g. “Assembly-women” will only split “Assemblywomen” at the given hyphen position if hyphenated at all.
    • As far as I know, Hyphenator.js (the JavaScript provided by this plugin) doesn’t support minimum length for hyphenated parts.
    Plugin Author e2b

    (@e2b)

    Hello. There are multiple ways to address your problem. You can specify a CSS class that shouldn’t be hyphenated (and is set within your website’s template accordingly), you can define exceptions right within the plugin options page and you might adjust the minimum length of words that should be hyphenated, so that hyphenation is only used for longer ones, leaving most of the words unhyphenated. There is nothing like an option to only use common hyphenations.

    Plugin Author e2b

    (@e2b)

    The plan is: fork the project on GitHub for edits, then send me pull requests and I’ll merge and push to the WordPress plugin directory (SVN). I’ll not give away write permissions to the SVN right now due to security concerns. This might change when obtaining my confidence.

    Plugin Author e2b

    (@e2b)

    Are you “odie2” on GitHub, too? I’ve created a mirror there.

    Plugin Author e2b

    (@e2b)

    I created a mirror on GitHub. Feeld free to contribute.
    https://github.com/e2b/wordpress-hyphenator

    Plugin Author e2b

    (@e2b)

    As you might have noticed, I’ve abandoned this project. I don’t use WordPress anymore and also the plugin is just a configuration UI for things you could also do when writing/edition your own theme. It’s always difficult to maintain something you don’t feel the need of for your own use case anymore within your free time.

    Since it is still quite popular, if anyone wants to continue maintaining this repository here, please let me know. I could also move it to GitHub for accepting pull requests.

    Plugin Author e2b

    (@e2b)

    TL;DR: If the problem occurs to you, please downgrade to version 4.0.0. I’ll update this plugin as soon as a fixed version is released by the Hyphenator.js developer. You might also think about your site’s domain configuration.

    Sorry for not responding to this thread. I’m not actively maintaining this plugin since I stopped using WordPress and also couldn’t really test it. As you likely noticed this plugin just uses the JavaScript “Hyphenator.js” which does the hyphenation work. It seems like a problem there that is not related to my code.

    This really seems related to some same origin policy which will be an issue if the url in the browser address bar differs from the url that is set in the WordPress configuration and used for embedding the JavaScript resource file. Can you confirm this only happens in this special case?

    Besides from the nasty error message, this setup isn’t recommended. WordPress sites should only be available using a specific domain. If you would like to use multiple domains for your site, please think about having a default domain and redirecting the others to that one. This is also bad in case of SEO, since Google might vote your site down because of the misuse of multiple domains and making the same content available on multiple sites using different domain names.

    Even I stopped maintaining this plugin, I would like to update it when a fixed version of Hyphenator.js is released. So this plugin should work at least as long as future WordPress versions won’t break any used APIs.

    @benjamin Pick: Nice hack. I plan to add an option for directly writing the configuration code in the next version.

    @sfbarth: The file with the debug suffix is the raw source code used for development, the normal file used by the plugin is a highly size optimized version using short variable names, less whitespaces etc. It does exactly the same and provides the same results even it has a different look.

    Plugin Author e2b

    (@e2b)

    Duplicate of “Vers. 4.1.0 insecure?“. Please discuss the problem there.

    Plugin Author e2b

    (@e2b)

    The Hyphenator plugin uses Hyphenator.js for doing the hyphenation. Actually the plugin just provides a simple configuration GUI for the great JavaScript tool. If you want to use it with an AJAX driven site, look at the documentation there: How to hyphenate text that has been loaded with AJAX?

    I’ve checked your code, but can’t find the problem. The last comma without a following word let the previous exception be ignored, but that’s only a problem for “kinderwijze”. I don’t know why the others aren’t used. Sorry.

    I’ve only written the WordPress plugin, the JavaScript code who does actually the hyphenation is from Mathias Nater (Hyphenator.js). I’ve wrote him an e-mail, maybe he is able to help.

    Plugin Author e2b

    (@e2b)

    Thank you very much for the hint! I’ve updated the current plugin version. Please note this is a silent update, so you have to uninstall and reinstall the plugin or manually unzip the new download to the WordPress plugin folder.

    Plugin Author e2b

    (@e2b)

    Very strange. I’m using the default WordPress function calls to write and read the plugin settings. Maybe something is wrong with your MySQL database or your WordPress installation. But it’s still confusing that other plugins work fine. Have you tried installing a random plugin you haven’t used before and see if the configuration works there?

    The plugin should work with every text as long as you have set up your preferred language and the class name correctly. Since version 4.0.0 you can force a language even if the lang-attribute is not used in your template. In case of your blog named like your username the class “entry-content” (without quotes) would be correct. Do you know how to write CSS?

    If Hyphenator is activated and configured you should see something like this in the source code of your website:

    <!-- Hyphenator for WordPress -->
    <script src="http://example.com/wp-content/plugins/hyphenator/Hyphenator.js" type="text/javascript"></script>
    <script src="http://example.com/wp-content/plugins/hyphenator/patterns/de.js" type="text/javascript"></script>
    <script type="text/javascript">
    	Hyphenator.config({
    		classname: 'entry-content',
    		remoteloading: false,
    		defaultlanguage: 'de'
    	});
    	Hyphenator.run();
    </script>

    The default configuration uses the class name “hyphenate” and needs a lang-attribute in the HTML structure. Otherwise it won’t work.

Viewing 15 replies - 1 through 15 (of 27 total)