Posts Tagged ‘mac’

I’m currently working with a client to improve the accessibility of their website for visually impaired users. This has involved a lot of time working with screen readers. As part of that, I have found a rather weird bug with Mac’s VoiceOver. It keeps saying the word “simul”.

Which isn’t a word. Maybe it’s saying simmul or simmel, or something else. None of these are words.

It happens when we give it a range to read. Something like “4-6”. The screen reader says the first number, then goes suspiciously quiet and says simul, and then starts building back up to regular volume as it gets to the final number.

I even asked about it on Stack Overflow, and everyone else was confused, too.

I wondered whether it might be a language issue. So, I tried adding a custom pronunciation, and double-checked the HTML tag had a lang attribute set to en-gb. Alas, no luck.

This is only a problem on Mac: TalkBack on Android works fine, for example.

In the end, I was able to get it to read correctly by changing the voice. By default, macOS comes with Daniel Compact set as the voice. However, when I switched to Daniel, Kate, or Kate Compact, it read it out correctly.

In a way, this is frustrating, because there is no much we can do to fix it. It’s a bug with the voice in Mac. But it is at least somewhat comforting to know that I wasn’t making some obviously silly mistake.

One of the irritating things about Spotlight Search in Mac is that you open want to open the folder that contains a file, but there is no obvious way to do this.

Luckily, there is a non-obvious way. And it’s pretty simple. Just hold down the Option key and double click on the file you want to open.

I was recently clearing space on my laptop hard drive when I noticed Google Chrome was taking 20gb of space. You read that correctly: 20gb.

After some searching, people suggested it could be old versions of Chrome. You can see into the package by right-clicking on it and clicking “Show Package Contents”. Inside I did indeed find dozens of old versions of Chrome and deleted them all. However, this only brought the size down to 19gb.

I wondered if the cache might be stored inside the app. I wouldn’t expect it to be, as typically it is stored in the user directory. However, when I went to clear out the cache, it only had 400mb in it away, so that ruled out that as a problem.

Next, I went through all the files in Finder to see if I could spot any large files. I could not. This made me suspicious, so I opened up terminal and checked it from there.

cd /Applications
du -sch ./* | grep Chrome
195M	./Google Chrome.app

Google Chrome isn’t actually using the space: Finder is just reporting it incorrectly. However, it clearly showed up on Daisy Disk before, and disappeared after I cleared out all of the old versions. So whether they were contributing or not I’m not sure.

I recently had to upgrade my iPad because a lot of the apps have stopped working on it. It has had a good four years, but that is all you get out of a tablet, so I felt like I was forced to upgrade something I didn’t really want to upgrade.

This was also my first experience of iOS 8 (until then everything was running iOS 6).

I do not think it is Apple’s finest release. Getting started on it was a pain. I was prompted for my iCloud password at start-up but it refused to accept it (even though I could log on to icloud.com with the same password repeatedly). Therefore I had to turn iCloud off at first and then re-enable it once I was up-and-running. Except it then prompted me for the password over and over again.

It then prompted me for the passwords to all my email accounts and worse, wouldn’t let me switch out to 1password to copy and paste it in. I had to open 1password on my phone and manually copy the passwords in, which is a massive pain when you use log and complicated ones.

After that the App Store kept insisting it had 11 updates even though I had updated everything, and most of the apps, including Apple’s own settings app rapidly crashed.

Apple are having a bad year. One bad release you could overlook, but Yosemite, the new version of OS X is preforming very poorly too. It took me 8 hours to complete the upgrade and since then I have found my Mac has crashed numerous times and there is a bug which causes file dialogues to continually grow so big they disappear off the screen that Apple does not seem to have any plans to fix.

The hardware on the iPad Air 2 is quite nice. It is a lot lighter than my old iPad 2 and I do really like the touch ID.

There is a bug in Apple’s OS X Yosemite in which the file dialog boxes grow larger than the screen. However, it does not seem Apple are in a rush to fix this.

The workaround is different for each application but for Google Chrome you can temporary solve it by running the following commands.

defaults delete com.google.Chrome NSNavPanelExpandedSizeForSaveMode
defaults delete com.google.Chrome NSNavPanelExpandedSizeForOpenMode

The box will continue to grow each time you use it, so you will have to run these commands again every time the box gets too big again.

If you’re running MAMP and you’ve finally managed to get the Imagick extension to add ImageMagick support compiled, the battle may not be over yet. There are more things you need to do. You might get an error similar to the following.

Firstly, imagick.so was probably installed into the sytem’s PHP extension directory. So you might need to copy this into MAMP’s directory. Don’t just copy and paste the code below as you need to check the paths are correct for your system.

php -i | grep extension_dir
cp /usr/lib/php/extensions/no-debug-non-zts-20090626/imagick.so
/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/

Secondly, some of the libraries are out of date. You might get an error like the following.

[01-Jun-2012 08:46:22] PHP Warning:  PHP Startup: Unable to load dynamic library 
'/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/imagick.so'
 - dlopen(/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/imagick.so, 9): Library not loaded: /opt/local/lib/libjpeg.8.dylib
  Referenced from: /Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/imagick.so
  Reason: Incompatible library version: imagick.so requires version 13.0.0 or later,
but libjpeg.8.dylib provides version 12.0.0 in Unknown on line 0
[01-Jun-2012 08:51:54] PHP Warning:  PHP Startup: Unable to load dynamic library '/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/yaml.so' - dlopen(/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/yaml.so, 9):
image not found in Unknown on line 0

We can solve this by editing a configuration file.

sudo vim /Applications/MAMP/Library/bin/envvars

Comment out the first two lines below and add the last one.

#DYLD_LIBRARY_PATH="/Applications/MAMP/Library/lib:$DYLD_LIBRARY_PATH"
#export DYLD_LIBRARY_PATH
export PATH="$PATH:/opt/local/bin"

This should override out of date libraries such as libjpeg. If you’re still having problems, you can manually copy in the freetype library too.

cp /opt/local/lib/libfreetype.6.dylib /Applications/MAMP/Library/lib/

Though in theory this step should not be required. Restart Apache and you should see Imagick appear on the phpinfo() output.

If you are trying to install YAML via PECL on Lion, you may get an error such as the following.

configure: error: Please install libyaml
ERROR: `/private/tmp/pear/install/yaml/configure --with-yaml' failed

Some solutions on the internet suggest installing it via a package manager.

rvm pkg install libyaml

However, although this process will claim to work, when you come to run the command again, it will fail at the same point. Instead, you need to download libyaml, which you can do here, then extract it, cd into the directory and run the following commands.

./configure
make
make install

You don’t need to sudo. You should now be able to run the install command again.

sudo pecl install --ignore-errors yaml

This time it should be successful.

If you are trying to install PECL YAML on Mac OS X Lion, you may find you get a conflict with an error message similar to the following.

WARNING: pecl.php.net/yaml: conflicting files found:
yaml/LICENSE (pear.symfony-project.com/yaml)

This error is documented on GitHub and as it is not critical, can be overcome by turning off errors.

pecl install --ignore-errors yaml

On running that command, it should no longer stop at that point.

If you’re trying to run PHPUnit from the terminal in Mac OSX Lion, you may get an error similar to the following.

File/Iterator/Autoload.php failed to open stream

You can resolve this by running the following commands.

curl http://pear.php.net/go-pear.phar > go-pear.php
sudo php -q go-pear.php

PHPUnit should now run without errors (or at least, without errors in their code 😉 ).

If you’re running Mac OSX Lion and trying to update your locate db, you may get the following error message.

-bash: updatedb: command not found

You can call updatedb by using its full path instead.

/usr/libexec/locate.updatedb

You could also create a symlink in your bin directory which would then allow you to just call updatedb as normal.