This is meant for people to be able to edit the standard application language files in your CI install, which work with the CI Language Class. The basic idea is that you have a master language, and then this allows translators to translate into other languages.

Features

• UTF8 support
• Handles php in language strings
• Synchronises language keys with ‘master’ language
• Checks php for syntax errors

Download

Download version 0.5.1 here

Installation

1. Unpack archive tar -zxvf translator-0.5.tgz
2. Copy files into appropriate location in your CI install (or just unpack archive over your install)
3. If your language files are in an exotic location, edit config/translator.php
4. set language files to be writable by your webserver
5. that’s it!

Usage

1. (If you haven’t already) Create your master language files and keys e.g.:
   language/english/file1_lang.php $lang['file1_some_key'] = 'some key'; $lang['file2_another_key'] = 'another key'; etc.
2. Create corresponding ‘slave’ language files e.g.:
   language/japanese/file1_lang.php
   NB You don’t have to create the keys, just the empty writable files
3. Make sure language files are webserver writable
4. Fire up your new controller i.e. index.php/translator and go!

Screen Shots

The post CodeIgniter Language File Translator appeared first on Mr Kirkland.

So it took me a while to figure this one out, therefore thought it would be worth posting here…

Facebook currently allows only one url type declaration per style block. So if you have multiple url declarations in your style, you get this error. The solution is to simply seperate the url declarations into separate style blocks:

<style type="text/css">
#div1 { background: url(http://www.imageserver.com/img1.jpg); }
#div2 { background: url(http://www.imageserver.com/img2.jpg); }
</style>

To become:

<style type="text/css">
#div1 { background: url(http://www.imageserver.com/img1.jpg); }
</style>
<style type="text/css">
#div2 { background: url(http://www.imageserver.com/img2.jpg); }
</style>


The post CSS Internal Error: incomplete URL list appeared first on Mr Kirkland.

As you already know Internet Explorer takes great care to interpret HTML and CSS in it’s own special way and only sometimes does this co-incide with the W3C‘s specification. The padding on Submit Buttons is one such nuisance.

Simply, IE simply ingores any horizontal padding you specify with css. The solution, I discovered, it to use the “overflow: visible” for all such elements e.g.

Before

<input type="submit" value="Internet explorer ignores my padding" style="padding: 20px;" />


After:

<input type="submit" value="Internet explorer respects my padding" style="padding: 20px; overflow: visible;" />

NB For this example I’ve put the style inline with the html – for real use this should be separated from the html in an external style sheet.

The post Internet Explorer Submit Button Horizontal Padding appeared first on Mr Kirkland.