Comments for ForTheScience.org

Comment on Error 1044 in MySQL: Access denied when using LOCK TABLES by Hemant Gandhi

Hemant Gandhi — Sun, 07 Dec 2008 15:47:57 +0000

Nice and simple.
Most of the other posts I found wanted me to give the db user the right to look tables.

Comment on Proofreading! by Simone Piunno

Simone Piunno — Tue, 21 Oct 2008 22:12:23 +0000

Given enough eyeballs every error is shallow.

Comment on Cairo PostScript rendering by Stefano

Stefano — Mon, 22 Sep 2008 22:12:25 +0000

If i remember correctly, the datasource inclusion was present in the ps file as created by cairo, therefore Preview.app was not involved.

It was some time ago, so I could be wrong.

Comment on Cairo PostScript rendering by Noboby

Noboby — Mon, 22 Sep 2008 22:06:03 +0000

> Apparently, Cairo renders what looks like a JPEG image, and then includes it using DataSource

This might not be cairo’s fault, but Preview.app’s when converting ps to pdf

Comment on MacOSX Leopard extended ls by Stefano

Stefano — Tue, 13 May 2008 20:17:45 +0000

Nice to hear! I hope to produce even more useful information in the future. I am having a lot of fun with this blog.

Thank you for the comment!

Comment on MacOSX Leopard extended ls by Avinash Meetoo

Avinash Meetoo — Thu, 08 May 2008 18:36:48 +0000

Excellent post Stefano.

I had to recreate my Drop Box in my Public folder and the information you gave helped me tremendously.

Thanks.

Comment on Unraveling Unicode problems in WikkaWiki by Stefano

Stefano — Sun, 09 Mar 2008 09:05:45 +0000

Yes, you are right. I assumed that the terminal is not in UTF32. However, if you set both the terminal and the locale in UTF32, I would expect it to work, because all the utilities (aware of encodings) will produce UTF32 encoded data, and the terminal will interpret this data as UTF32. If you instead have an utility that just outputs Latin-1 encoded data, you will not be able to see it properly with such setup.

Comment on Unraveling Unicode problems in WikkaWiki by Simone

Simone — Fri, 29 Feb 2008 21:56:43 +0000

“In fixed length encodings, every symbol require a fixed number of bytes, say 4. This is the approach UTF-32 uses: every code point requires four bytes to be written, always. This solution increases the space occupation four-fold even if you are only using plain English characters. Moreover, it is not backward compatible, so you cannot read a pure English text encoded in UTF-32 with cat. ”

Although you’re right 99%, this is only true when you assume english was written in a 1-byte per character encoding and that your terminal is configured in a locale using and encoding different than UTF-32. Actually, cat is not concerned at all with encodings. cat just reads a byte stream and writes to the terminal. It’s the terminal job to map those bytes to actual characters and nothing prevents the terminal to be configured with UTF-32 as the encoding.

Comment on MacOSX Leopard and freezing keyboard by Stefano

Stefano — Mon, 18 Feb 2008 18:29:37 +0000

Apple released a patch some week later. Now it works.

Comment on Versioning file permissions in svn by Stefano

Stefano — Tue, 12 Feb 2008 18:57:26 +0000

Of course, there’s another solution: don’t keep the svn tree for direct webserver fruition. Instead, use an “installer” that takes the files from the svn, installs them in a proper place, and create the cache directory.