papafox

The fact that a personal name is stored in EBCDIC is missing the point. the mainframe has supported unicode for 20 years. The bank account holders name is stored in a character column in a database. Every character column can be defined with a different codepage, so it is possible to define the name column as stored in UTF-8, EBCDIC or any of a number of other codepages.

For the bank to claim that the reason that they can store names containing diacritics because the name is coded in EBCDIC is nonsense. The bank just needs to change the database column definition to UTF-8.

Re prepaid sims - in order to protect Australian voters from dreadful terrorists, activation of the Sim requires entering some form of id.

I don't read section 3.3(i) as preventing criticism of performance, rather it prohibits the release performance benchmarks without further permission from Atlassian.

Having been on the receiving end of competitors running 'benchmarks' on a service I worked on, and the trumpeting the very contrived and out of context figures, I can understand why Atlassian is trying to prevent it from happening to them.

Pity that it probably won't work.

Doesn't Zellers' Congruence do the same task? Zellers' has been around since 1883, and has been very widely implemented.