There are pictures of me practicing aikidō on my dōjo’s website. On the shoulder of my dōgi, one can see the mark of my former dōjo, in Tatsunokuchi, Ishikawa.
Il y a des photos de moi en train de pratiquer l’aïkidō sur le site web de mon dōjo. Sur l’épaule de mon dōgi (la tenue pour pratique l’aikidō), on peut voir la marque de mon ancien dōjo, à Tatsunokuchi, Ishikawa.
Auf der web-seite meines Dōjo gibt es Photographien wo ich Aikidō treibe. Auf der Schulter meines Dōgi (das Aikidō Kleid), kann mann noch die Marke meines altes Dōjo, in Tatsunokuchi, Ishikawa, sehen.
I have recently started doing page layouts of old RPG scenarios. While this is much easier using a Pages and a modern laptop than say, using a Mac Classic with a 9 inch screen, I also work with much higher resolution images. Between Lion, Pages and Photoshop Elements, 4 GB of RAM started to feel a bit constrained. So I decided to buy some additional RAM for my 13-inch, Mid-2010 MacBook Pro. My favourite hardware supplier had some Mac Memory Memory Kits by Corsair with two 4 GB 204 pins SO-DIMM DDR3 1333 Mhz chips which was quite cheap. The kit did not list what machines it was compatible, but just claimed to be compatible with
Apple® iMac®, MacBook®, MacBook® Pro.
Installing the memory was pretty easy, unscrew the back of the laptop and the two slots are immediately accessible. After I installed the two chips, the laptop froze, I tried swapping them, the laptop still freezes at boot, so I replaced one of the 4 GB chips with an old 2 GB chip, and the laptop boots happily and recognises the memory. So I just assume that the other chip was somehow broken and returned it. Of course, as this was a kit, I got an e-mail telling that I needed to return both chips. Inconvenient. I got the replacement chips yesterday and mounted them this morning. Same problem. Basically the machine boots with one 4 GB stick, but not two.
Most of the forum where full of people with similar problems, but no useful answer, i.e. a lot of people saying the chips were bad and to replace them, until I found this post on Tyler Milner’s blog. The core problem is that the Mid 2010 MacBook Pro can only handle 1067 Mhz memory, if either chip is a 1067 Mhz the other 1333 Mhz chip is slowed down by the memory controller. But if both are fast ones, the memory runs at 1333 Mhz, which the CPU cannot handle. I find it pretty annoying that the MacBook’s memory controller cannot handle this situation and that Corsair’s compatible memory isn’t.
Currently my laptop runs happily with 6 GB, which is not too bad. I can now either flash one of the 4 GB chips to lower its frequency, like the linked post suggests, this involves booting into Windows. The other is to find someone willing to exchange my fast chips for slower chips. The problem seems to be that it is not easy finding 4GB 1067 Mhz chips. Compatibility, just like in the good old days…
This February, Sony did something unexpected: it did something smart. Included with the release notes for firmware update 4.11 is the following text
The Internet browser has been updated for improved content display.
Some websites that could not be displayed correctly, including interactive websites, are now supported, and page layouts are now displayed with better accuracy.
Given the fact that Sony won’t release a new living room console for a least one year, keeping the venerable PS3 relevant sounds like a good strategy to me.
What I find interesting is that many HTML5 additions designed for mobile phones are actually very relevant for a gaming console. Consider the following:
- The PS3 is typically connected to a TV or a big screen, and has hardware support for playing back H264 content.
- Input forms
- By default, the PS3 uses a soft-keyboard, so having specialised keyboards for numbers, e-mail addresses, and ranges would make it much more usable.
- Most PS3 come with Dualshock controllers which can produce vibrations.
- Media Capture
- The PS3 can be equipped with a webcam and a microphone.
- The PS3 has respectable Open GL ES rendering capacities
I suspect the main issue is going to be RAM, the PS3 is now six years old, and has only 256 MB or RAM, but smartphones those days don’t have much more. I will be interesting to see if Sony updates the browser and at which pace, but at least it is now in a situation where progress is possible.
I have done some spring cleaning on this blog, mostly simplifying stuff by using two nice html5 features:
ruby. The first fixes a long standing mess in html, the lack of of standard way of putting video clips into web pages. There was a large debate about the codec to use, with Microsoft and Apple pushing for h264, Google pushing for WebM, and Firefox pushing for the OGG format. The dust has not settled on this issue, most video on this site are in h264 format simply because this is the format my mobile phone produced, and the format most mobile phones can render. While the current solution is not perfect, before I had to use a combination of
object tags, which was much worse.
I took advantage of the cleanup to fix a few links that were still pointing to the old site’s address, in one case there were still links to the address
free.fr, from seven years ago. I also have been playing around with microdata those days, so I added the relevant meta-data to the video, I doubt this will have much of an impact, but I like the idea of embedding meta-data into the html, microdata is not a part of html5, by the way.
ruby tags are more specialised, and bear no relationship with the ruby programming language. The tag is surprisingly old: it was first suggested in 1996, and implemented as an extension by Internet Explorer 5, the fact that it took 15 years to standardise that tag is quite depressing. Ruby tags allows the writer to add phonetic annotations to some html text. The classical use-case is adding furigana to japanese kanji, but it can basically be used for any kind of annotation, like for instance IPA phonetics. There are basically three tags:
ruby which acts as a container,
rt which contains the annotation, and
rp which wraps the fallback code when ruby is not supported, that tag typically contains parenthesises. The source for the text in the box will look like this:
I have not back-converted all my existing content, the css tricks work, and it would be a lot of work, but I will use the standard tags from now-on.
Pixel art and 8 bit graphics are all the rage those days, so while the I clearly remember the block graphics, the colours in my memory were less saturated. The fact that I was using a crappy monitor is probably one explanation. After looking around on the web, I found a very informative page by Philip Timmermann “Pepto” that explains how the Vic II chip was producing colours and his resulting palette is quite dark, and seem somehow to match my memory better. As I wanted to play around with that palette, I wrote a quick python script that reads a
CSV file and outputs a Photoshop Palette. I found the explanations on the
ACO file format on this page.
Vic II colours
Interestingly, the resulting colour palette seems quite close to the hues of the theme I’m currently using on this blog (a modified version of japan-style), is there some influence at play? You can see a fragment of the banner image rendered using the Vic II’s palette in the top right part of the page. The size of the image corresponds to the full screen on a Commodore 64 in multi-colour mode: 200 × 160 pixels. The actual palette is in the table on the right (the font comes from style64.org).
One japanese tradition that I rather like is that in the restaurant, one does not pour oneself alcohol, instead, this is the responsibility of the person in front of you, or on your side. This seems to be a good system to prevent people from drinking alone. What I learnt yesterday is that there are two verbs for the act of serving one another: 酌み交わす and 次ぎ合う. The difference between those two is simple: the first is for sake, the second for beer. Important distinction.
Une tradition japonaise que je trouve plutôt sympathique c’est qu’au restaurant, on ne se sert jamais de vin ou de bière soi-même, c’est la responsabilité de la personne en face ou à côté. Cela me semble être un bon système pour empêcher qu’une personne boive seule. Ce que j’ai appris avec intérêt c’est qu’il y a deux verbes pour décrire l’acte de servir de l’alcool à l’autre : 酌み交わす et 次ぎ合う. La différence entre les deux est simple : le premier verbe est utilisé pour le saké, le second pour la bière. Distinction importante.
Le Kanji d’aujourd’hui :Today’s Kanji:
||Bar service, serving, hostComptoire, service, hôte
||The left part is the sake radical ⾣.
The right part is ladle 勺.La partie gauche set le radical de saké ⾣.
La partie droite est une louche 勺.
||Mix, mingle, associationMélange, association
||Next, order, sequenceSuivant, ordre, sequence.
||The left part is ice ⼎ (historically it was two 二).
The right part is lack 欠.La partie gauche set le radical de glace ⼎ (historiquement il s’agissait de deux 二).
La partie droite est le manque 欠.
||Fit, suit, joinAdaption, joindre
||Le lower part is mouth radical 口.La partie inférieure set le radical de bouche 口.
Those days I have been playing around with semantic tags an annotations on my blog. One interesting thing is the ability to associate my blog’s content with myself. What is the point? I write this blog in my own name, but there are multiple Matthias Wiesmann (or should I say Wiesmänner) on the web, and they do quite different things, like biological food, or get married to girls called Nadine or manage Hostels in Vietnam. Those tags associate my Google+ identity to the my blog, and things are show accordingly on the web:
I doubt my online reputation is sufficient to influence the behaviour of people searching the internet, beyond my circle of friends, but I find the idea interesting nonetheless.
I suspect that if you have a more important reputation in a given domain, making that association explicit can help people who trust you find your content.
Comme exercice, ma prof de japonais m’a donné quelques proverbes japonais basé sur des nombres à tirer au clair.As an exercice, ma teatcher asked me to look-up some number based japanese proverbs.
||Une chose dite, dix comprises.One thing said, ten understood
||Il comprend rapidement.He’s quick on the uptake
||Il piétine des deux pieds.Trampling on two feets
||Il n’arrive pas à se décider, il hésiteHe’s hesitating, procrastinating.
||Bleu, deux ansBlue, two years
||Un bleu, un nouveauGreenhorn
||Sur la pierre, trois année.On thé stone, three years.
||Il faut être patient.
Cent fois sur le metier, remettez votre ouvrage.One must be patient.
||Bonze de trois jours.Bonze of three days
||Quelqu’un qui commence beaucoup de choses, mais ne les termine pas.Somebody who starts things, but does not finish them.
||Quatre amers, Huit amersFour bitter, eight bitter
||Avoir beaucoup d’ennuisLots of trouble.
||Au milieu de cinq lieues (ri) de brouillardIn the middle of eight leagues of fog.
||Être complètement perdu.Completely lost.
||L’apprentissage de la main de soixanteThe learning of the hand of sixty.
||Il n’est jamais trop tard pour apprendre.You can always learn.
||Sept rotations, huit chutes.Seven rotations, eight falls.
||Souffrir à l’agonieBeing in agony.
||Une beauté, huit directionsOne beauty, eight directions
||l’ami de tout le mondeEverybody’s friend, nobody’s friend.
||touche en huitHit in eight
||Passer sa colère sur autruiTo spill out anger.
||neuf morts, une vie reçueNine deaths, one life granted.
||échapper de justesse à la mortA narrow escape from death
||dix personnes, dix couleursTen people, ten colours.
||À chacun see goûts.To each his tastes.
||Soixante pas, cent pasSixty feet, hundred feet.
||Deux options se valent.Both options are similar.