Posted by jpluimers on 2017/11/29
Good news the Press-This bookmarklet on WordPress.com has been reinstated.
See https://github.com/WordPress/press-this/pull/29 and the discussions in these below threads and sources.
Solves issues:
- #12 – Add text domains
- #15 – Restore Bookmarklet Functionality
- #17 – Needs better documentation
- #32 – The Press This bookmarklet itself on the tools page does not have the code
Some relevant sources:
Read the rest of this entry »
Posted in Bookmarklet, Development, Power User, SocialMedia, Software Development, Web Browsers, Web Development, WordPress, WordPress | Leave a Comment »
Posted by jpluimers on 2017/09/25
At the end of April 2014, Roman Yankovsky started a nice [Wayback] discussion on Google+ trying to get upvotes for [Wayback] QualityCentral Report #: 124402: Compiler bug when comparing chars.
His report basically comes down to that when using Ansi character literals like #255, the compiler treats them as single-byte encoded characters in the current code page of your Windows context, translates them to Unicode, then processes them.
The QC report has been dismissed as “Test Case Error” (within 15 minutes of stating “need more info”) by one of the compiler engineers, directing to the [Wayback] UsingCharacterLiterals section of Delphi in a Unicode World Part III: Unicodifying Your Code where – heaven forbid – they suggest to replace #128 with the Euro-Sign literal.
I disagree, as the issue happens without any hint or warning whatsoever, and causes code that compiles fine in Delphi <= 2007 to fail in subtle ways on Delphi >= 2009.
The compiler should issue a hint or warning when you potentially can screw up. It doesn’t. Not here.
Quite a few knowledgeable Delphi people got involved in the discussion:
Read the rest of this entry »
Posted in Ansi, ASCII, Conference Topics, Conferences, CP437/OEM 437/PC-8, Delphi, Delphi 2006, Delphi 2007, Delphi 2009, Delphi 2010, Delphi 7, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Delphi XE6, Development, Encoding, Event, ISO-8859, Missed Schedule, QC, SocialMedia, Software Development, Unicode, UTF-8, Windows-1252, WordPress | Leave a Comment »
Posted by jpluimers on 2017/05/31
[WayBack] cov.fefe.de – The Isoblog.
(it was Scheduled for 09:00 UTC, but after all these years, WordPress.com at random still suffers from the “missed schedule” bug)
Brilliant move. Der Spiegel never had a chance, and even Der Postillion is in awe. (Context).
Yes, cov.fefe.de is the same content as blog.fefe.de.
Via: [WayBack] #covfefe punkt de http://blog.koehntopp.info/index.php/1833-cov-fefe-de/ – Kristian Köhntopp – Google+
Background:
–jeroen
Read the rest of this entry »
Posted in Fun, Missed Schedule, SocialMedia, WordPress | Leave a Comment »
Posted by jpluimers on 2016/11/01
The below is even more convoluted when you have ad-blockers installed: then the G+ integration won’t even appear and the behaviour differs between classic G+ and current G+.
So here are the steps:
- Remove the WordPress link from https://security.google.com/settings/security/permissions
- In your blog settings (for me that’s https://wordpress.com/sharing/wiert.me) remove the G+ integration; do this in a Chrome incognito Window if the G+ integration is not visible
- At the same page re-add your G+ integration and follow further steps at https://jetpack.com/support/publicize/google/#reconnecting
Modern G+ settings at https://plus.google.com/settings does not have the above permissions integration link but classic G+ at https://plus.google.com/settings?gmbpt=true&fd=1 does.
via:
Hi there,
I have good news!
A few weeks ago, Google+ made some changes to their API. In doing so introduced some issues with Publicize. The module still worked, but the updates posted by the WordPress app on your Google+ Profile or Google+ Page were only visible to you.
In the past few weeks, we’ve worked with Google+ to start using a new API. That API works just like the old one, with one exception: publicized posts are now public. You can’t change the visibility of publicized posts to “My Circles”, or anything else.
If you’re happy to have Publicize publishing public posts to your Google+ Profile or Page, you can follow the instructions below to delete your old connection, and then reconnect your Jetpack site to your Google+ account:
https://jetpack.com/support/publicize/google/#reconnecting
I hope this helps.
Source: Topic: [Resolved] Sharing on Google Plus Private..? Why? « WordPress.org Forums
Posted in G+: GooglePlus, Power User, SocialMedia, WordPress | Leave a Comment »
Posted by jpluimers on 2015/08/10
A great on-line way to cleanup html (from for instance style information) before publishing it on your blog: HTML Cleaner – Word to clean HTML.
One of the things is does is Remove inline styles.
Ideal for copy-pasting a quote from a web-site to your HTML editor.
–jeroen
via: www.html-cleaner.com
Posted in Development, HTML, HTML5, Power User, SocialMedia, Software Development, Web Development, WordPress | Leave a Comment »
Posted by jpluimers on 2015/01/17
Woot! Post 2400 (:
For my own reference.
My old stats: https://wordpress.com/my-stats?blog=7443331
My new stats: https://wordpress.com/stats/7443331
Hopefully the old stats stay for a while as they are far more useful.
–jeroen
Posted in Power User, SocialMedia, WordPress | 2 Comments »
Posted by jpluimers on 2014/12/22
For my link archive: the “old” stats page, as it shows more information in a better formatted way (especially on larger monitors) My Stats — WordPress.com.
The “new” stats page used only half the screen width (long live responsive layout): Stats ‹ 7443331 — WordPress.com.
–jeroen
Posted in Development, SocialMedia, Software Development, Web Development, WordPress, WordPress | 2 Comments »
Posted by jpluimers on 2014/12/08
Boy, I wish I had found out about this a long time ago.
Embedding source code in WordPress web sites has always been a pain, as the Jekyll & Hyde faces of the WordPress Visual & Text keep fighting about the content.
A few artefacts I stumbled upon on a regular base:
Not so any more: just put your code in a public gist, then put the Gist url in the code without making it an actual link. Read the rest of this entry »
Posted in Power User, SocialMedia, WordPress | Leave a Comment »
Posted by jpluimers on 2014/11/10
Too bad the Markdown support from WordPress is a farce.
Below the horizontal rule is the Leak Check test from CommonMark. The rendering is even worse than the spec.txt rendering I posted before.
via:
Read the rest of this entry »
Posted in MarkDown, Power User, SocialMedia, WordPress | 1 Comment »