Jump to content
Pierre-Luc

Super Smartypants

Recommended Posts

Super Smartypants is a ProcessWire textformatter module which adds support for languages. It also allows you to set the different Smartypants Typographer parser attributes to customize which rules apply and fixes some bugs.

Super Smartypants requires the language module.

Usage

 
After installation, add /site/modules/TextformatterSuperSmartypants/smartypants.php to your language translations.
 
To enable Super Smartypants for a language, set the Smartypants attributes field to 1 (or see below for details), otherwise to disable leave the field empty.
 
Change default strings according to your masterful typographic knowledge.

Documentation and downloadhttps://github.com/plauclair/SuperSmartypants

  • Like 11

Share this post


Link to post
Share on other sites

Very cool and right in time! - I was just about to hacking the original code to make it work in German.

Your solution, using language translation files, is VERY SMART. - Works well so far (tested with PW dev, German/English).

Thank you very much for this contribution!

  • Like 2

Share this post


Link to post
Share on other sites

@Pierre-Luc

thanks for this module!

i'll try to remove spacing before a colon, but i can't get it to work.

In my test textarea i have the following text:

Lorem ipsum : dolor sit amet.

I want to remove the space before the colon, but i don't know how. When i enter a minus sign (-) in the input "Space before a colon (default:  )" i get the following output:

Lorem ipsum-: dolor sit amet.

The space is gone, but instead i got the minus.

What do i have to insert there to only remove the space. I read the documentation a dozen times, but i can't get it right.

Thanks!

Share this post


Link to post
Share on other sites

You need to set the parser attributes explicitely for this. Entering a minus in the "Space before a colon" field just replaces the space character before the colon with a new character (you would usually use it to change the space type, for forcing a non-breaking or a thin space for example, but it can take any character), this is why you're getting a - in your text. The documentation on GitHub tells how to do this, let me know if part of it is unclear.

Share this post


Link to post
Share on other sites
You need to set the parser attributes explicitely for this.

I think, this is the part, that is unclear to me …

I entered "1" in the first field. 

What would be the setup to remove spaces before a colon? I think it would be clearer, if i had an example for this.

It's probably easy as pie, but i can't get it to work …   :huh:

thanks!

Share this post


Link to post
Share on other sites

I see, the 1 you insert is a preset, but it doesn't have the "remove spaces before colons" turned on by default. You need to replace the 1 preset with all the individual parser attributes you want, so it might look something like : 

qDe:-;-

  • Like 1

Share this post


Link to post
Share on other sites

Super Smartypants is a ProcessWire textformatter module which adds support for languages. It also allows you to set the different Smartypants Typographer parser attributes to customize which rules apply and fixes some bugs.

Hi Pierre-Luc,

it was a good idea to enhance Ryans module from 2011 with language translations. Thank you for this.

There is a more current smartypants.php file available from the smartypants developer, who fixed some minor bugs. The direct link is:

https://littoral.michelf.ca/code/php-smartypants/php-smartypants-typographer-1.0.1.zip

Maybe you would like to consider this?

Share this post


Link to post
Share on other sites

Hi Pierre-Luc,

it was a good idea to enhance Ryans module from 2011 with language translations. Thank you for this.

There is a more current smartypants.php file available from the smartypants developer, who fixed some minor bugs. The direct link is:

https://littoral.michelf.ca/code/php-smartypants/php-smartypants-typographer-1.0.1.zip

Maybe you would like to consider this?

I'll look at merging the changes from 1.0.1., but they seem very minor (unless the revision notes don't tell the whole thing).

  • Fixed handling of HTML comments to match latest HTML specs instead of doing it the old SGML way.

  • Lowered WordPress filtering priority to avoid clashing with the [caption] tag filter. Thanks to Mehdi Kabab for the fix.

Share this post


Link to post
Share on other sites

Is the support for very old php versions still needed?

With PHP7 in strict mode, I now receive 2 notices:

Methods with the same name as their class will not be constructors in a future version of PHP

Changing 3 lines of code to using __construct instead fixed the notices for me, I think.

 

Share this post


Link to post
Share on other sites

sorry if this is a dumb question, but what does this module do? i don't understand it from the docs here and on github...

Share this post


Link to post
Share on other sites
On 2016-07-20 at 5:16 PM, bernhard said:

sorry if this is a dumb question, but what does this module do? i don't understand it from the docs here and on github...

It replaces some typographic marks with better ones depending on context. 

  • Like 1

Share this post


Link to post
Share on other sites
On 2016-07-19 at 3:27 PM, ceberlin said:

Is the support for very old php versions still needed?

With PHP7 in strict mode, I now receive 2 notices:

Methods with the same name as their class will not be constructors in a future version of PHP

Changing 3 lines of code to using __construct instead fixed the notices for me, I think.

 

What do you mean by very old? Many of the later 5.x releases are now EOL or simply unsupported anymore. I haven't done much housekeeping on the plugin for a while, the original smartypants code needs a good code review..

Share this post


Link to post
Share on other sites
3 hours ago, Pierre-Luc said:

What do you mean by very old? Many of the later 5.x releases are now EOL or simply unsupported anymore. I haven't done much housekeeping on the plugin for a while, the original smartypants code needs a good code review..

Well, the module works flawlessly so far (and REALLY helps to produce nice looking content!!!!).

With the small code change to "__construct" it is also working here with PHP7 without throwing notices any more.

Share this post


Link to post
Share on other sites

Is this module still maintained and we get an official fix for PHP7?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.1.1 Debugging: fixed error during uninstall 0.1.0 Added new detection of async scripts for W3C Validation 0.0.6 CSS-Debugging for hiding unused buttons, added ProCache support for the JavaScript tag 0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • By bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
×
×
  • Create New...