 | jpluimers on OpenSuSE fix “piix4_smbu… |
 | Nick on OpenSuSE fix “piix4_smbu… |
| jpluimers on Some ideas to show a Google Ca… |
 | Randy Tapson on Some ideas to show a Google Ca… |
 | Dominik Kwolczak on Convert/adapt an old ATX Power… |
Posted by jpluimers on 2018/12/03
One of the things that bugged me for a long time is that every now and then for some shapes, when editing their text, the draw.io web interface puts in trailing line feeds after the text, messing up layout.
The easiest way to work around it is by searching inside the diagram XML for
"".
(the above code got screwed by WordPress.com saving it, so the search is in this small gist below)
This behaviour is intermittent on the drawio MacOS desktop app.
–jeroen
Posted in Cloud Apps, Development, draw.io, Encoding, Internet, Power User, Software Development, Unicode | Leave a Comment »
Posted by jpluimers on 2018/09/25
For my link archive:
Via: [WyBack] Are there blank characters in unicode that have the same widths as period, comma and digits? – Lars Fosdal – Google+
Answer: no, though better fonts have period, comma, colon, semicolon and other punctuations the same width as the punctuation space.
The use-case:
I wanted right justified text without having to do custom positioning/drawing – where the decimal zero is white space.F.x. here 12 instead of 12.0
9.5
11.6
12 <– #$2008 and #$2007
13.4I.e. PunctuationSpace and FigureSpace
I don’t want to deal with positioning/rendering since it happens inside a third party component.
–jeroen
Posted in Development, Encoding, Font, Power User, Software Development, Unicode | Leave a Comment »
Posted by jpluimers on 2018/03/14
[WayBack] GitHub – keith-turner/ecoji: Encodes (and decodes) data as emojis:
Ecoji 🏣🔉🦐🔼
Ecoji encodes data as 1024 emojis, its base1024 with an emoji character set. As a bonus, includes code to decode emojis to original data.
Sick. Works splendid when all your systems are fully nice to Unicode.
None are. So there’s a German word for it:
Nein
Via:
–jeroen
Posted in Development, Encoding, Fun, Go (golang), Software Development, Unicode | Leave a Comment »
Posted by jpluimers on 2017/11/07
A well worth long rad:
We all recognize emoji. They’ve become the global pop stars of digital communication. But what are they, technically speaking? And what might we learn by taking a closer look at these images, characters, pictographs… whatever they are 🤔 (Thinking Face). We will dig deep to learn about how these thingamajigs work. Please note: Depending on your browser, you may not be able to see all emoji featured in this article (especially the Tifinagh characters). Also, different platforms vary in how they display emoji as well. That’s why the article always provides textual alternatives. Don’t let it discourage you from reading though! Now, let’s start with a seemingly simple question. What are emoji?
[WayBack] You, Me And The Emoji: Character Sets, Encoding And Emoji – Smashing Magazine
Via: [WayBack] Everything you ever wanted to know about characters, encodings, glyphs… and, oh yeah, emoji: bit.ly/2fNKeW3Long, rewarding read. – Ilya Grigorik – Google+
Here is just the ToC:
TABLE OF CONTENTS LINK
–jeroen
Posted in ASCII, Development, Encoding, ISO-8859, ISO8859, Shift JIS, Unicode, UTF-16, UTF-8, UTF16, UTF8, Windows-1252 | Leave a Comment »
Posted by jpluimers on 2017/09/25
At the end of April 2014, Roman Yankovsky started a nice discussion on Google+ trying to get upvotes for 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 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:
Posted in Ansi, ASCII, 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, ISO-8859, Missed Schedule, QC, SocialMedia, Software Development, Unicode, UTF-8, Windows-1252, WordPress | Leave a Comment »
