The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,862 other subscribers

when apple.com != apple.com – Phishing with Unicode Domains – Xudong Zheng

Posted by jpluimers on 2017/04/21

Vulnerability in Chrome, Firefox, and Opera makes users susceptible to phishing with Unicode domains.

Source: [Archive.isPhishing with Unicode Domains – Xudong Zheng

Basically these are not the same sites:

Depending on the font used, you might notice it if you look very careful.

Keywords: Unicode codepoints, visual similarity, codepoint to character mapping in fonts, Punycode

Via: [WayBack] Same URL, two websites? (notice the difference)1. https://www.аррӏе.com/2. https://www.apple.com/ – Jean-Luc Aufranc – Google+

References:

–jeroen

Posted in Power User, Security | Leave a Comment »

Tested the CastBuddy extension from the Chrome Web Store: nice, but high CPU usage even when no videos

Posted by jpluimers on 2017/04/21

CastBuddy – Chrome Web Store:

This extension finds videos on the web sites you are browsing and allows you to play them on your Chromecast device.

Works nice if you need it, but uses a lot of CPU (on my Retina MacBook with latest chrome: about 75% of one CPU core) so it drains battery fast.

You can view this high CPU usage in the Chrome Task Manager (which used to be available through chrome://tasks, but this is one of the use full Find Hidden Features On Chrome’s Internal Chrome:// Pages features they removed). Fire up the Chrome Task Manager through the Window menu.

Verdict

Enable only when you need it. Disable after use in chrome://extensions

–jeroen

via: CastBuddy – Chrome Web Store:

When it finds Chromecast comptible videos ( .webm, .mp4, .mkv etc), count of videos is shown over extension’s menubar icon, which you can click to Select a video and extension will send it to your Chromecast device. Once a casting session is established, you can control video playback from Extension’s popup page.

Posted in Chrome, Google, Power User | 2 Comments »

Warning: C64 geek pr0n! A Mind Is Born

Posted by jpluimers on 2017/04/20

Geek pr0n on the C64:

Making a demo in just 256 bytes would be a formidable challenge regardless of platform. A Mind Is Born is my attempt to do it on the Commodore 64. In the absence of an actual 256-byte compo, it was submitted to the Oldskool 4K Intro compo at [WayBackRevision 2017, where it ended up on 1st place.

Source: [WayBackA Mind Is Born

Via:

–jeroen

Read the rest of this entry »

Posted in 6502, C64, Commodore, Development, History, Software Development | Leave a Comment »

use vmrun – via How do I find the IP address of a virtual machine using VMware Fusion? – Super User

Posted by jpluimers on 2017/04/20

Note this works only when the VMs have VMware Tools installed (more on that below):

VMWare provides, not surprisingly, a built in tool for this, vmrun. It’s under /Applications/VMware Fusion.app/Contents/Library/vmrun although it has moved around in other Fusion releases a bit.

🍺 vmrun list Total running VMs: 1 .docker/machine/machines/myvm.vmx
🍺 vmrun getGuestIPAddress ~/.docker/machine/machines/myvm.vmx 172.16.213.128

via: How do I find the IP address of a virtual machine using VMware Fusion? – Super User [WayBack]

vmrun [WayBack] is barely documented and most of is in PDF of which this is the most recent I could find: www.vmware.com/pdf/vix180_vmrun_command.pdf [WayBack]

Based on the above path, I added this to my ~/.bash_profile file:

alias vmrun='/Applications/VMware\ Fusion.app/Contents/Library/vmrun'
alias vmrun-list-running-VMs='vmrun list | grep vmx'
vmrun-list-ipv4-of-running-VMs()
{
  vmrun-list-running-VMs | while read line ; do echo $line && vmrun getGuestIPAddress $line; done
}

Now I can do this:

$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
/Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
172.16.172.134
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.135
$ vmrun-list-ipv4-of-running-VMs
/Users/jeroenp/VM/diaspore.opensuse-Tumbleweed-x64/diaspore.opensuse-Tumbleweed-x64.vmx
172.16.172.134
/Users/jeroenp/VM/W81Entx64DelphiRegression.vmwarevm/W81Entx64.vmx
172.16.172.142

These are the messages I observed:

Error: The VMware Tools are not running in the virtual machine: /Users/jeroenp/VM/diaspore-opensuse-Tumbleweed-x64.vmwarevm/diaspore-opensuse-Tumbleweed-x64.vmx
Error: Unable to get the IP address
172.16.172.135

The first one means a machine is running but has no VMware Tools installed. For an OpenSuSE machine you can install it with zypper install open-vm-tools, for other Linux systems read VMware Tools auf Ubuntu, Mint, CentOS oder openSUSE installieren | ITrig [WayBack]

Some more examples of vmrun for VMware Fusion are at Control VMware Fusion from the Command Line | James Reuben Knowles [WayBack]

–jeroen

Posted in *nix, bash, Development, Fusion, openSuSE, Power User, Scripting, Software Development, SuSE Linux, Tumbleweed, Virtualization, VMware | Leave a Comment »

(35) Introducing Macintosh System 7.5 Product Overview – July 15, 1994 – Apple VHS Archive – YouTube

Posted by jpluimers on 2017/04/20

Some 23 years ago…

Posted in Apple, Classic Macintosh, History, Macintosh SE/30, Power User | Leave a Comment »

Dark corners of Unicode / fuzzy notepad

Posted by jpluimers on 2017/04/20

You think you know Unicode? Think again, then read [Wayback] Dark corners of Unicode / fuzzy notepad.

On basics, sorting, comparison, decomposition, composition, width, whitespace, encoding, emoji, interesting code planes and dark corners. Lots of dark corners.

The examples are in Python, but hold for almost any programming language

–jeroen

via: Kristian Köhntopp

Posted in Conference Topics, Conferences, Development, Encoding, Event, Software Development, Unicode | Leave a Comment »

When BRCC32 throws `Fatal error Illegal macro definition in command line or defines page.` in a DUnitX project

Posted by jpluimers on 2017/04/19

I had a Fatal error Illegal macro definition in command line or defines page. thrown by BRCC32.exe in one of my Delphi projects.

As cgrc.exe could build the .rc file [source in Russian; WayBack], I reproduced it from the console with an Empty.rc file that has no content. That way I could rule out file content: now it had to be command-line arguments which is a different cause than any of the search results I found before.

My project was based on one of the DUnitX test projects. It ran in Delphi XE8, but the Delphi version doesn’t matter as BRCC32 hasn’t been updated since 1999.

Further below are the failure/success examples; this went wrong:

  1. DUnitX uses the DUNITX-DEBUG define to enable debugging of DUnitX itself in DUnitX.inc which also supports the DUNITXDEBUG define in the same area.
  2. Delphi will translate a .RC file in a project into a BRCC32.exe call adding the project conditional defines and search paths
  3. BRCC32.exe doesn’t like hyphens in conditional defines throwing a non-descriptive error Fatal error Illegal macro definition in command line or defines page.

So either removing DUNITX-DEBUG or changing it into DUNITXDEBUG solves the problem. Hence my pull-request.

Read the rest of this entry »

Posted in Delphi, Development, Resource Files and Scripts (.res/.rc), Software Development, Windows Development | Leave a Comment »

“Galiad Computers Ltd.” that provided software in the 1990s to Polyvroom for vector based font design (plus some dry transfer lettering history)

Posted by jpluimers on 2017/04/19

Every now and then I complete more pieces of my early 1990s vector fonts era. This time I’ve found back the name of the company that provided some parts of the software that we used at Polyvroom to produce vector fonts (both PostScript and TrueType): “Galiad Computers Ltd.” from Israel. I don’t remember Eitan Mizrotsky though.

At the time of writing, http://galiad.co.il/ seems down, but the Web Archive has old copies of it. I totally forgot they did some more public Border Software as well.

Another party involved back then was Visualogik. They still exist, so I will get in touch with them one day.

Mecanorma, LetterPress and Letraset dry tansfer lettering (click to enlarge).

Mecanorma, LetterPress and Letraset dry tansfer lettering (click to enlarge).

I also learned that Trip Productions has reorganised a few years ago and now the letter rubbing part of Polyvroom (that they made for/with Mecanorma, LetterPress and Letraset lettering you could rub off: dry transfer lettering – image via @GraphicsVectors) is now licensed to ProCraft BV. The text is not completely accurate (Trip took over late 1994 when Polyvroom went belly up), bug gives a good impression:

Mecanorma was a French company and leading manufacture of instant lettering. The rub down lettering was manufactured by a Dutch company called Polyvroom BV. Around 1985 the company called Trip Productions took over Mecanorma and Polyvroom. In the following years Trip Productions BV developed digital fonts and produced the rub down lettering from Lisse in The Netherlands.

The main product of Mecanorma was always the production of the rub down lettering. It was not easy to to scale down the company when the market of the rub down lettering did almost disappear because of the new technology in the world. Many of the production lines for the rub down lettering were closed down. The rub down lettering is a decal technology and to survive Trip Productions did try to focus on that technology for a long time with success.

In 2012 the decision was made that they had to turn the company around. A new company was formed called Trip Licenses BV and they focus on the license of the Fonts and Patents the company has. The production and sales of the rub down lettering is still active and licensed to ProCraft BV in The Netherlands. The digital fonts are licensed to House of Type (ITF Inc.) in the USA.

I also found this about the Mecanorma Collection on MyFonts which has a more accurate timeline:

Mecanorma Collection

FollowAlong with Letraset, the French company Mecanorma was one of the major vendors of instant rub-down lettering. Along with licensing typefaces from other vendors, Mecanorma commissioned original typeface designs.

From 1989 until 1994, Mecanorma worked with another Dutch company Visualogik to create digital versions of their typefaces. These typefaces were released in Type 1 format, bearing a “MN” suffix. In addition, Monotype licensed and digitized some of Mecanorma’s typefaces. In 1995, Mecanorma stepped back from the professional graphics market and entered into other areas such as home decoration. During that time, their decorative materials, including their instant rub-down lettering, were manufactured by the now defunct Dutch company, Trip Productions BV.

In 2004, International TypeFounders (ITF) licensed the digital typefaces from Trip Productions BV and released them as the Mecanorma Collection. This helped to preserve one of the finest digital font libraries of display typefaces around, combining real arts and crafts into the tools of today.

In 2014, International TypeFounders entered into a permanent agreement with Trip Consultants BV, the legal successor of the French type foundry Mecanorma. As the exclusive worldwide digital rights owners of the collection, ITF have now republished the Mecanorma Collection in OpenType for the first time.

–jeroen

via:

Posted in Font, History | Leave a Comment »

When your markdown README files on GitHub are broken as of lately

Posted by jpluimers on 2017/04/18

Basically below gist tells it all.

Many repositories on GitHub do not have whitespace between the # and headings. This is against the specs, so GitHub fixed their rendering engine. Which means now many files do not render nicely any more.

So if you have headings like this:

##text

Fix them to be like:

## text

If your GitHub repository has less than 50 starts, you did not get an automatic pull request to fix it from https://github.com/bryant1410/readmesfix so you can either:

–jeroen

Recently, GitHub introduced the change in how atx
headers are parsed in Markdown files.

##Wrong

Correct

While this change follows the spec, it breaks many existing repositories. I took the
README dataset which we created
at source{d} and ran a simple
regexp PySpark job.
It appeared that more than 500,000 repositories have README files which are rendered
with invalid headers.

Among those 0.5mm, there are more than 10,000 which have more than 50 stars. They were
uploaded to data.world.

Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management | Leave a Comment »

Jan Barendregt is Looking for programmers to maintain existing Excel add-in software

Posted by jpluimers on 2017/04/18

Jan Barendregt is Looking for programmers to maintain existing Excel add-in software.

The reason is no fun (cancer without curative treatment and prognosis till death likely months).

Please follow-up on the forum if you can be of help: [WayBackEmbarcadero Discussion Forums: Looking for programmers to maintain existing Excel add-in software

–jeroen

Posted in Delphi, Development, Software Development | Leave a Comment »