<?xml version="1.0" encoding="iso-8859-1"?>
<?xml-stylesheet href="http://hugi.to/blog/styles/rss.css" type="text/css"?>
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>
 <channel>
  <title>Reto&#039;s Weblog</title>
  <link>http://hugi.to/blog</link>
  <description>&lt;p&gt;Just Blogging...&lt;/p&gt;
</description>
  <pubDate>Fri, 08 Jan 2010 23:46:17 +0100</pubDate>
  <generator>http://www.lifetype.net</generator>
    <item>
   <title>Optimizing PNG Compression</title>
   <description>
    &lt;p&gt;
While creating some screenshots and saving them with &lt;a href=&quot;http://www.gimp.org/&quot; title=&quot;The GIMP Website&quot;&gt;the GIMP&lt;/a&gt;, I felt the PNG files were rather big and I was looking for a tool that would do better compression. PNG files usually are saved with lossless compression, not like JPEG files, where you always loose some image information with every percent of higher compression.
&lt;/p&gt;
&lt;p&gt;
As usual googling helped and I quickly found the two very handy command line tools pngcrush and pngnq. &lt;a href=&quot;http://pmt.sourceforge.net/pngcrush/&quot; title=&quot;pngcrush Website&quot;&gt;pngcrush&lt;/a&gt; is an optimizer for PNG files and tries to create optimized PNG files without compromising their quality (e.g. as small as possible but lossless). &lt;a href=&quot;http://pngnq.sourceforge.net/&quot; title=&quot;pngnq Website&quot;&gt;pngnq&lt;/a&gt; on the other hand creates &lt;a href=&quot;http://en.wikipedia.org/wiki/Quantization_%28image_processing%29&quot; title=&quot;Wikipedia Article about Quantization&quot;&gt;quantized&lt;/a&gt; PNG images, which means that the compression is not lossless anymore.
&lt;/p&gt;
&lt;p&gt;
Both tools are available for various platforms such as Linux, Windows and Mac. As usual the&amp;nbsp; &lt;strike&gt;ubuntu-way&lt;/strike&gt; debian-way is straight forward and as easy as:
&lt;/p&gt;
&lt;p&gt;
&lt;code&gt;$ apt-get install pngnq pngcrush&lt;/code&gt;
&lt;/p&gt;
&lt;p&gt;
The screenshots below illustrate the different qualities and file sizes to expect with default settings on all three tools. In some occasions individual tweaking may result in even better results, but the default settings work for me just fine in this case.
&lt;/p&gt;
&lt;p&gt;
Summary on a 957x957 pixel screenshot:&lt;br /&gt;
Original (The GIMP, level 9): ~287 kb&lt;br /&gt;
Processed by pngcrush: ~284kb&lt;br /&gt;
Processed by pngnq: ~82kb&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;
Screenshot saved with GIMP 2.4.2, compression level 9 (default/maximum) ~287kb:&lt;br /&gt;
&lt;a id=&quot;res_68&quot; href=&quot;http://hugi.to/blog/resources/1/hugi.to-screen-gimp-comp-level-9.png&quot;&gt;&lt;img src=&quot;http://hugi.to/blog/resources/1/previews-med/hugi.to-screen-gimp-comp-level-9.png&quot; border=&quot;0&quot; alt=&quot;PNG saved with GIMP&quot; /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Screenshot saved with GIMP and optimized with pngcrush ~284kb:&lt;br /&gt;
&lt;a id=&quot;res_69&quot; href=&quot;http://hugi.to/blog/resources/1/hugi.to-screen-pngcrush.png&quot;&gt;&lt;img src=&quot;http://hugi.to/blog/resources/1/previews-med/hugi.to-screen-pngcrush.png&quot; border=&quot;0&quot; alt=&quot;PNG optimized with pngcrush&quot; /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Screenshot saved with GIMP and quantized with pngnq ~82kb:&lt;br /&gt;
&lt;a id=&quot;res_70&quot; href=&quot;http://hugi.to/blog/resources/1/hugi.to-screen-pngnq.png&quot;&gt;&lt;img src=&quot;http://hugi.to/blog/resources/1/previews-med/hugi.to-screen-pngnq.png&quot; border=&quot;0&quot; alt=&quot;PNG compressed with pngnq&quot; /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Conclusion&lt;/strong&gt;: The GIMP has a rather effizient compression on level 9 as pngcrush could not achieve much better results (only about 1% reduced filesize). But you are limited to use lossless compression with the GIMP. So using pngnq may be usefull in some situations. The filesize reduction is usually significant (up to 70% as compared to the output of the GIMP). 
&lt;/p&gt;
   </description>
   <link>http://hugi.to/blog/archive/2008/01/06/optimizing-png-compression</link>
   <comments>http://hugi.to/blog/archive/2008/01/06/optimizing-png-compression</comments>
   <guid>http://hugi.to/blog/archive/2008/01/06/optimizing-png-compression</guid>
      <dc:creator>reto</dc:creator>
      
    <category>How To</category>
         <pubDate>Sun, 06 Jan 2008 22:49:56 +0100</pubDate>
   <source url="http://hugi.to/blog/rss.php?blogId=1&amp;profile=rss20">Reto&#039;s Weblog</source>
                                                  </item>
    <item>
   <title>Tweaking Firefox Tabs</title>
   <description>
    &lt;p&gt;I found it quite annoying that the close-tab buttons (&lt;img src=&quot;http://hugi.to/blog/resource/how-tos/Firefox-close-button.png/download&quot; border=&quot;0&quot; alt=&quot;Firefox Close Button&quot; title=&quot;Firefox Close Button&quot; /&gt;) on each tab disappear if tabs get shrinked to the minimum (e.g. if horizontal scrolling of tabs gets activated because of the number of open tabs in one window).&lt;/p&gt;&lt;p&gt;Luckily FF let&amp;#39;s you configure about anything related to the UI. It&amp;#39;s only a matter of editing two config values to leave the close buttons visible all the time! &lt;/p&gt;&lt;p&gt;Open a new, empty tab and type &lt;a href=&quot;http://hugi.to/blog/about:config&quot;&gt;about:config&lt;/a&gt; into the address bar. Search the two config entries &amp;quot;&lt;a href=&quot;http://kb.mozillazine.org/Browser.tabs.tabMinWidth&quot;&gt;Browser.tabs.tabMinWidth&lt;/a&gt;&amp;quot; (defaults to 100) and &amp;quot;&lt;a href=&quot;http://kb.mozillazine.org/Browser.tabs.tabClipWidth&quot;&gt;Browser.tab.tabClipWidth&lt;/a&gt;&amp;quot; (defaults to 140). While tabMinWidth defines the minimum width a tab can be shrinked to, tabClipWidth defines the minimum width where the close button is still displayed on unfocused tabs. If you change &lt;strong&gt;tabMinWidth to 101&lt;/strong&gt; and &lt;strong&gt;tabClipWidth to 100&lt;/strong&gt; tabs are always closeable with just one click. See the screenshots below for a better understanding of the issue.&lt;/p&gt;&lt;p&gt;Default Firefox 2.0 setting:&lt;/p&gt;&lt;p&gt;&lt;a id=&quot;res_54&quot; href=&quot;http://hugi.to/blog/resource/how-tos/ff-tab-default.png/download&quot;&gt;&lt;img src=&quot;http://hugi.to/blog/resource/how-tos/mediumpreview/ff-tab-default.png&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Custom Firefox 2.0 (tabs can always be closed with one click):&lt;/p&gt;&lt;p&gt;&lt;a id=&quot;res_53&quot; href=&quot;http://hugi.to/blog/resource/how-tos/ff-tab-custom.gif/download&quot;&gt;&lt;img src=&quot;http://hugi.to/blog/resource/how-tos/mediumpreview/ff-tab-custom.gif&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;The setting in the about:config:&lt;/p&gt;&lt;p&gt;&lt;a id=&quot;res_55&quot; href=&quot;http://hugi.to/blog/resource/how-tos/ff-tab-settings.png/download&quot;&gt;&lt;img src=&quot;http://hugi.to/blog/resource/how-tos/mediumpreview/ff-tab-settings.png&quot; border=&quot;0&quot; /&gt;&lt;/a&gt; &lt;/p&gt;&lt;p&gt;Enjoy!&amp;nbsp;&lt;/p&gt;
   </description>
   <link>http://hugi.to/blog/archive/2007/01/23/tweaking-firefox-tabs</link>
   <comments>http://hugi.to/blog/archive/2007/01/23/tweaking-firefox-tabs</comments>
   <guid>http://hugi.to/blog/archive/2007/01/23/tweaking-firefox-tabs</guid>
      <dc:creator>reto</dc:creator>
      
    <category>Geek Stuff</category>
      
    <category>How To</category>
         <pubDate>Tue, 23 Jan 2007 21:50:43 +0100</pubDate>
   <source url="http://hugi.to/blog/rss.php?blogId=1&amp;profile=rss20">Reto&#039;s Weblog</source>
                                                  </item>
    <item>
   <title>Ubuntu PXE install via Windows</title>
   <description>
    &lt;p&gt;This article expains in step by step instruction how to install &lt;a href=&quot;http://www.ubuntu.com/&quot; title=&quot;Ubuntu Website&quot;&gt;Ubuntu&lt;/a&gt; over the network (although it&amp;#39;s easy to adapt the how-to to other linux distros) via a Windows 2000/XP client. &lt;/p&gt;&lt;h3&gt;Introduction&lt;/h3&gt;&lt;p&gt;The &lt;a href=&quot;http://en.wikipedia.org/wiki/Preboot_Execution_Environment&quot; title=&quot;Wikipedia Article on PXE&quot;&gt;Preboot Execution Environment&lt;/a&gt; (PXE) is nothing new, but rarely used in home office environments because it&amp;#39;s most of the time easier to install any operating system from a CD, DVD or even a USB storage device. But what, if you have neither optical drives nor USB storage devices? The only requisites for a PXE installation are a working computer (any OS with TFTP Servers available will do) and Internet access. &lt;/p&gt;&lt;h3&gt;The Problem&lt;/h3&gt;&lt;p&gt; With the new Intel Southbridge (ICH8R) parallel ATA Drives are no longer supported by the chipset natively, which means most motherboard manufacturers add third party controllers on their boards to provide p-ata interfaces. These third party controllers however are not well supported on Linux at the moment. Especially not directly in the kernel, which means you would have to pre-compile your own installer to access any p-ata CD-Rom. Another reason for using PXE might be subnotebooks without CD/DVD-ROM. The only option you have there is an installation via USB or over the network (PXE). &lt;/p&gt;&lt;h3&gt;Step 1: Prerequisites&lt;/h3&gt; &lt;p&gt;First get yourself a copy of the &lt;a href=&quot;http://tftpd32.jounin.net/&quot; title=&quot;Windows TFTP Server&quot;&gt;free TFTP server&lt;/a&gt; by Philippe Jounin. Second we need the ubuntu installer files. Of course it doesn&amp;#39;t make much sense to download one of the ubuntu CD images if we only need the small installer. The installer will choose the nearest mirror and download all the files needed automatically during the installation.&lt;br /&gt; The browsable Ubuntu archives are at &lt;a href=&quot;http://archive.ubuntu.com/ubuntu/dists/&quot; title=&quot;Ubuntu Archive&quot;&gt;http://archive.ubuntu.com/ubuntu/dists/&lt;/a&gt;. But as we only need the installer, we can ftp to &lt;a href=&quot;ftp://archive.ubuntu.com/ubuntu/dists/edgy/main/installer-i386/current/images/&quot;&gt;ftp://archive.ubuntu.com/ubuntu/dists/edgy/main/installer-i386/current/images/&lt;/a&gt; and download the folder &lt;strong&gt;netboot&lt;/strong&gt; (ignore any symlinks, they may give you errors during the download).&lt;br /&gt; That&amp;#39;s all we need to boot our Ubuntu installer over the network. Let&amp;#39;s setup the TFTP server.  &lt;/p&gt;&lt;h3&gt;Step 2: Setting up a TFTP Server on Windows&lt;a id=&quot;res_52&quot; href=&quot;http://hugi.to/blog/resource/how-tos/tftp32-screen.png/download&quot;&gt;&lt;img src=&quot;http://hugi.to/blog/resource/how-tos/preview/tftp32-screen.png&quot; border=&quot;0&quot; alt=&quot;TFTP32 DHCP Settings&quot; title=&quot;TFTP32 DHCP Settings&quot; align=&quot;right&quot; /&gt;&lt;/a&gt;&lt;/h3&gt;&lt;ol&gt;&lt;li&gt;Create a directory, preferably on your C Drive. We&amp;#39;ll name it &lt;strong&gt;tftp&lt;/strong&gt; for now.&lt;/li&gt;&lt;li&gt;copy the tftpd32.exe to c:tftp&lt;/li&gt;&lt;li&gt;Start the server by clicking on the exe&lt;/li&gt;&lt;li&gt;switch to the tab &amp;quot;DHCP Server&amp;quot; and fill in your network setup. Note that the PC you want to boot must be in the same Subnet. Enter &lt;strong&gt;pxelinux.0&lt;/strong&gt; as the boot file. The Screenshot on the right shows my setup.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Now we need to copy the Ubuntu netboot installer over to our tftp root directory:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;copy the folder &lt;strong&gt;ubuntu-installer&lt;/strong&gt; to c:tftp&lt;/li&gt;&lt;li&gt;copy the folder &lt;strong&gt;pxelinux.cfg&lt;/strong&gt; from ubuntu-installer/i386/ to c:tftp&lt;/li&gt;&lt;li&gt;copy the file &lt;strong&gt;pxelinux.0&lt;/strong&gt; from ubuntu-installer/i386/ to c:tftp&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;This is how your tftp folder should look like:&lt;/p&gt;&lt;p&gt;c:tftppxelinux.cfgdefault&lt;br /&gt;c:tftpubuntu-installeri386&amp;lt;some more files/folders&amp;gt;&lt;br /&gt;c:tftppxelinux.0&lt;br /&gt;c:tftptftpd32.exe &lt;/p&gt;&lt;h3&gt;Step 3: Booting Ubuntu&lt;br /&gt;&lt;/h3&gt;&lt;p&gt;To boot from tftp you may need to activate booting from the network interface in the BIOS. This may be done in the boot sequence settings or directly in the onboard ethernet device settings. After that, restart, lean back and watch the activities in the log viewer tab of the tftpd.&lt;/p&gt;&lt;p&gt;&lt;br /&gt;Note: Ubuntu will let you choose a mirror and download all the files you need. The whole procedure will work with any other debian flavour almost identically. There is a nice how to on doing a PXE install via Linux instead of windows at the &lt;a href=&quot;http://wiki.koeln.ccc.de/index.php/Ubuntu_PXE_Install&quot;&gt;CCC Wiki&lt;/a&gt;.&amp;nbsp; &lt;/p&gt;
   </description>
   <link>http://hugi.to/blog/archive/2006/12/23/ubuntu-pxe-install-via-windows</link>
   <comments>http://hugi.to/blog/archive/2006/12/23/ubuntu-pxe-install-via-windows</comments>
   <guid>http://hugi.to/blog/archive/2006/12/23/ubuntu-pxe-install-via-windows</guid>
      <dc:creator>reto</dc:creator>
      
    <category>How To</category>
         <pubDate>Sat, 23 Dec 2006 23:10:21 +0100</pubDate>
   <source url="http://hugi.to/blog/rss.php?blogId=1&amp;profile=rss20">Reto&#039;s Weblog</source>
                    </item>
    <item>
   <title>Googlebot and Site Redirects</title>
   <description>
    &lt;p&gt;
At a first glance it seems like there is nothing on the web, that can hide from beeing indexed by Google. Not only html but 
&lt;a class=&quot;out&quot; href=&quot;http://www.google.com/help/faq_filetypes.html&quot;&gt;twelve(!) other filetypes&lt;/a&gt; are getting indexed at the moment.&lt;br /&gt;
But Google is much pickier as one could assume, whereas its reasons are evident and reasonable:
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;1. Redirects&lt;/strong&gt;&lt;br /&gt;
Googlebot (Google&#039;s Spider) doesn&#039;t follow the &amp;quot;http/1.1 302 Found&amp;quot;
status code (resource temporarily moved). Instead you should use a
&amp;quot;http/1.1 301 Moved Permanently&amp;quot; header to make Google follow the
redirect.&lt;br /&gt;
To make the long story short: If you&#039;re using PHP to do the redirect (and many are using PHP these days) you should add the 
status code header manually because PHP sends a 302 Found status code by default.&lt;br /&gt;
&lt;br /&gt;
This stops Google and therefore is only usefull if your site is really under maintenance at the moment:
&lt;/p&gt;
&lt;div class=&quot;code&quot;&gt;
&lt;code&gt;&lt;span style=&quot;color: #000000&quot;&gt;
&lt;span style=&quot;color: #0000bb&quot;&gt;&amp;lt;?php&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;header&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #dd0000&quot;&gt;&#039;Location:&amp;nbsp;http://www.foo.com/bar/&#039;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;);&lt;br /&gt;
&lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;?&amp;gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;/code&gt;
&lt;/div&gt;
&lt;p&gt;
This makes Google follow the redirect and index the Site:&amp;nbsp;
&lt;/p&gt;
&lt;div class=&quot;code&quot;&gt;
&lt;code&gt;&lt;span style=&quot;color: #000000&quot;&gt;
&lt;span style=&quot;color: #0000bb&quot;&gt;&amp;lt;?php&lt;br /&gt;
&amp;nbsp;&amp;nbsp;header&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #dd0000&quot;&gt;&#039;HTTP/1.1&amp;nbsp;301&amp;nbsp;Moved&amp;nbsp;Permanently&#039;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;);&lt;br /&gt;
&amp;nbsp; &lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;header&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #dd0000&quot;&gt;&#039;Location:&amp;nbsp;http://www.foo.com/bar/&#039;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;);&lt;br /&gt;
&lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;?&amp;gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;/code&gt;
&lt;/div&gt;
&lt;p&gt;
If you prefer to do the redirects within an .htaccess
file (on Apache, of course), you could do it like this. Every Request
to foo.com/ is redirected to foo.com/bar/:&amp;nbsp;
&lt;/p&gt;
&lt;div class=&quot;code&quot;&gt;
&lt;code&gt;&lt;span style=&quot;color: #000000&quot;&gt;
&amp;nbsp;#Redirect&amp;nbsp;(this&amp;nbsp;will&amp;nbsp;result&amp;nbsp;in&amp;nbsp;a&amp;nbsp;301&amp;nbsp;permanently&amp;nbsp;moved&amp;nbsp;status&amp;nbsp;code)&lt;br /&gt;
&amp;nbsp;RedirectMatch&amp;nbsp;permanent&amp;nbsp;^/$&amp;nbsp;http://www.foo.com/bar/&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;/code&gt;
&lt;/div&gt;
&lt;p&gt;
I expect it&#039;s faster and less resource intensive to set up an .htaccess file because there 
is no need to parse any php code at all. Though it won&#039;t matter in most cases anyway. (untested assumption)
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;2. Sessions&lt;/strong&gt;&lt;br /&gt;
Google doesn&#039;t follow links with a session attached. If you&#039;ve enabled session.use_trans_sid in your php.ini you should check if Google is requesting the page. If your site displays fine without the use of sessions simply don&#039;t start one if google is visiting. ;-)
&lt;/p&gt;
&lt;div class=&quot;code&quot;&gt;
&lt;code&gt;&lt;span style=&quot;color: #000000&quot;&gt;
&lt;span style=&quot;color: #0000bb&quot;&gt;&amp;lt;?php&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #ff8000&quot;&gt;//&amp;nbsp;session&amp;nbsp;is&amp;nbsp;not&amp;nbsp;started&amp;nbsp;to&amp;nbsp;serve&amp;nbsp;google&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;if(&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;stristr&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;(&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;$_SERVER&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;color: #dd0000&quot;&gt;&#039;HTTP_USER_AGENT&#039;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;],&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #dd0000&quot;&gt;&#039;google&#039;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;)&amp;nbsp;===&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;false&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;)&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;{&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;session_start&lt;/span&gt;&lt;span style=&quot;color: #007700&quot;&gt;();&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;}&lt;br /&gt;
&lt;/span&gt;&lt;span style=&quot;color: #0000bb&quot;&gt;?&amp;gt;&lt;br /&gt;
&lt;/span&gt;
&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;/code&gt;
&lt;/div&gt;
&lt;p&gt;
Add as many search engine bots as you like. A more sophisticated method (like  &lt;a class=&quot;out&quot; href=&quot;http://php.net/preg_match&quot;&gt;regular expressions&lt;/a&gt;) is not needed here, but would of 
course work, too.
&lt;/p&gt;
   </description>
   <link>http://hugi.to/blog/archive/2003/10/02/googlebot-and-site-redirects</link>
   <comments>http://hugi.to/blog/archive/2003/10/02/googlebot-and-site-redirects</comments>
   <guid>http://hugi.to/blog/archive/2003/10/02/googlebot-and-site-redirects</guid>
      <dc:creator>reto</dc:creator>
      
    <category>How To</category>
      
    <category>Code</category>
         <pubDate>Thu, 02 Oct 2003 19:45:34 +0200</pubDate>
   <source url="http://hugi.to/blog/rss.php?blogId=1&amp;profile=rss20">Reto&#039;s Weblog</source>
     </item>
    <item>
   <title>Some Tips and Tricks for your EPOC Device</title>
   <description>
    &lt;ul&gt;
	&lt;li&gt;Shortcut &lt;strong&gt;Shift+Ctrl+Fn+S&lt;/strong&gt;:&lt;br /&gt;
	Creates a screenshot in mbm format.
	&lt;/li&gt;
	&lt;li&gt;Shortcut &lt;strong&gt;Fn+&#039;app&#039;&lt;/strong&gt;:&lt;br /&gt;
	Creates a new file (e.g. type Fn+&#039;Word&#039; for a new Word file)
	&lt;/li&gt;
	&lt;li&gt;Shortcut &lt;strong&gt;Ctrl+Shift+E&lt;/strong&gt;:&lt;br /&gt;
	&#039;Kills&#039; the marked application if you are in the &amp;quot;open files / programs&amp;quot; dialog.
	&lt;/li&gt;
	&lt;li&gt;Shortcut: &lt;strong&gt;Ctrl+Tab&lt;/strong&gt;:&lt;br /&gt;
	Drive &#039;z&#039; (ROM) is now browseable.
	&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;Extras bar&lt;/strong&gt;:&lt;br /&gt;
	If you rearrange the Extras bar, make sure you save the settings in the 
	Shell.ini. Simply go to the Control Panel, hit &amp;quot;Extras bar&amp;quot; 
	or &amp;quot;Enter&amp;quot; and close the dialog with &amp;quot;OK&amp;quot;. Otherwise 
	you will loose the settings when you do a soft reset.
	&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;User dictionary&lt;/strong&gt;:&lt;br /&gt;
	You can find the User.dic in c:\system\data\. It is a plain txt-file, 
	which you can import in Word, edit and then export again.
	&lt;/li&gt;
&lt;/ul&gt;
   </description>
   <link>http://hugi.to/blog/archive/2000/08/22/some-tips-and-tricks-for-your-epoc-device</link>
   <comments>http://hugi.to/blog/archive/2000/08/22/some-tips-and-tricks-for-your-epoc-device</comments>
   <guid>http://hugi.to/blog/archive/2000/08/22/some-tips-and-tricks-for-your-epoc-device</guid>
      <dc:creator>reto</dc:creator>
      
    <category>How To</category>
         <pubDate>Tue, 22 Aug 2000 19:43:25 +0200</pubDate>
   <source url="http://hugi.to/blog/rss.php?blogId=1&amp;profile=rss20">Reto&#039;s Weblog</source>
     </item>
   </channel>
</rss>