Επιλέξτε πρώτο το Firefox!
Από την πρώτη Μαρτίου 2010, οι χρήστες Windows στην Ευρωπαϊκή Ένωση έχουν την επιλογή για το λογισμικό του περιηγητή (web browser). Η επιλογή θα ενεργοποιηθεί μέσω του συστήματος WindowsUpdate.
Μπορείτε να δείτε πως φαίνεται η ελληνική σελίδα από το σύνδεσμο επιλογής λογισμικού περιήγησης για την Ευρωπαϊκή Ένωση.
Επιλέξτε πρώτο το Mozilla Firefox διότι πρώτο μέλημα του λογισμικού είναι η ασφάλειά σας.
Η δικτυακός τόπος browserchoice.eu παρέχεται από τη Microsoft. Τη λειτουργία του browserchoice.eu την έχει επιβάλει η Ευρωπαϊκή Ένωση όταν καταδίκασε τη Microsoft σε πρόσφατη δίκη περί μονοπωλίου.
Στους όρους χρήσης του browserchoice.eu η Microsoft αναφέρει για το θέμα αυτό
ΚΟΙΝΟΠΟΙΗΣΕΙΣ
Η τοποθεσία BrowserChoice.eu σχεδιάστηκε σύμφωνα με μια απόφαση της νομοθεσίας περί ανταγωνισμού της Ευρωπαϊκής Επιτροπής τον Δεκέμβριο του 2009.
© 2009 Microsoft Corporation. Με επιφύλαξη κάθε νόμιμου δικαιώματος.
Google Street View enters Europe
Google Street View has entered Europe. The Wikipedia article has up to date information on the countries covered already (France, Italy, Spain). In addition, there is information of the countries that will get covered in the future.
The colored areas are the areas that Google Street View data is available. These areas appear when you drag the yellow doll from the zoom area at the left, and you hover it over the map.
Apparently, the privacy concerns did not stop Street View from entering Europe. The faces of the people and the car number plates are blurred in most cases. If you search a bit, it is possible to find cases that a traffic plate or face have not been blurred (example, example).
Firefox 3 statistics, and the Greek language
Firefox 3 was released on the 17th June, 2008 and up to now, an impressive 22 million copies have been downloaded.
kkovash had a peek at the stats and produced a nice post with diagram for the downloads of the localised versions of Firefox 3 (that is, excluding en-US).
Downloads at [Release+3] days (20th June 2008)
Dark red signifies that there have been more than 100,000 downloads originating from the respective country. It is quite visible that most European countries managed to surpass the 100,000 threshold. Greece at that point was hovering to about 50,000 downloads. In the Balkan region, Turkey was the first country to grab the red badge.
It is interesting to see that Iran has been No 2 in the whole of Asia (No 1 has been Japan). Only now China managed to reach the second place, and pushed Iran in the third place. When taking into account the population gap and the political situation, Iran achieved a amazing feat.
In the first few days, a few countries only managed to jump fast over the 100K mark. It appears that these countries have strong social network communities, that urged friends to grab a copy of Firefox 3.
This is a recent screenshow (26th June 2008), at [Release+9] days. Greece has achieved Red status the other day. In the Balkan region, Turkey, Romania and Bulgaria had reached 100,000 first.
In the EU region, it is notable that Ireland, at 76,000 downloads, is lagging behind.
Another observation is that the countries from Africa are lagging significantly from the rest of the world. Low broadband Internet penetration and limited number of Internet users is likely to be the reason.
How many downloads have there been for the Greek localisation of Firefox 3;
kkovash reveals that there have been about 60,000 downloads for the Greek localisation of Firefox 3. This would approximately mean that more than 60% of the downloads in Greece have been for the localised version. Great news.
Looking into the symbol files
In the previous post, we talked about the ANTLR grammar that parses the XKB layout files.
The grammar is available at http://code.google.com/p/keyboardlayouteditor/source/browse. I’ll rather push to the freedesktop repository once the project is completed. Now it’s too easy for me, just doing svn commit -m something.
Below you can see the relevant layout files for each country (and in some cases, language), and how the grammar deals with them. First column is filenames from the CVS XKB symbols subdirectory (to be moved eminently to GIT). Last’s week discussion with Sergey helped me figure out issues with the symbol files, simplify what information is needed, and what can be eliminated. Second column has Not OK if something is wrong. Third column tries to explain what was wrong.
| ad | ||
| af | ||
| al | ||
| altwin | ||
| am | ||
| ara | ||
| az | ||
| ba | ||
| bd | ||
| be | ||
| bg | ||
| br | ||
| braille | ||
| bt | ||
| by | ||
| ca | ||
| capslock | ||
| cd | ||
| ch | ||
| cn | ||
| compose | ||
| ctrl | ||
| cz | ||
| de | ||
| dk | ||
| ee | ||
| epo | ||
| es | ||
| et | ||
| eurosign | ||
| fi | ||
| fo | ||
| fr | ||
| gb | NOK | Non-UTF8 |
| ge | ||
| gh | ||
| gn | ||
| gr | ||
| group | NOK | virtualMods= AltGr |
| hr | ||
| hu | NOK | Non-UTF8 |
| ie | ||
| il | NOK | key.type=”FOUR_LEVEL” (typically: key.type[something]=….) |
| in | NOK | key.type=”FOUR_LEVEL” (typically: key.type[something]=….) |
| inet | ||
| iq | ||
| ir | ||
| is | ||
| it | ||
| jp | NOK | key <BKSP> { type=”", // empty? symbols[Group1]= [ bracketright, braceright ] }; |
| keypad | NOK | overlay1=<KO7> }; // what’s “overlay”? |
| kg | ||
| kh | ||
| kpdl | ||
| kr | ||
| kz | ||
| la | ||
| latam | ||
| latin | ||
| level3 | NOK | virtual_modifiers LAlt, AlGr; virtualMods= Lalt |
| level5 | ||
| lk | ||
| lt | ||
| lv | ||
| ma | ||
| mao | ||
| me | ||
| mk | ||
| mm | ||
| mn | ||
| mt | ||
| mv | ||
| nbsp | NOK | Non-UTF8 |
| ng | ||
| nl | ||
| no | ||
| np | ||
| olpc | ||
| pc | NOK | key <AA00> { type=”SOMETHING” } instead of { type[Group1]=”SOMETHING” } |
| pk | ||
| pl | ||
| pt | ||
| ro | ||
| rs | ||
| ru | ||
| se | ||
| shift | NOK | actions [Group1] = [ |
| si | ||
| sk | ||
| srvr_ctrl | NOK | key <AA00> { type=”SOMETHING” } instead of { type[Group1]=”SOMETHING” } |
| sy | ||
| th | ||
| tj | ||
| tr | ||
| ua |
Non-UTF-8 are the files that have characters that are not UTF-8 (are iso-8859-1).
Some layouts have key.type = “something” and others key.type[SomeGroup] = “something”. Apparently, the format allows to infer which is the group that the type acts upon? That’s weird. Would it be better to put the group information? Is it required that the group is not set?
Some files have virtualMods, which I do not know what it is. Is it used?
Parsing XKB files with antlr
antlr (well, antlr3) is an amazing tool that replaces lex/flex, yacc/bison.
One would use antlr3 if they want to deal with Domain-Specific Languages (DSL), an example of which are the text configuration files.
In our case, we use antlr3 to parse some of the XKB configuration files, those found in /etc/X11/xkb/symbols/??.
Our aim is to be able to easily read and write those configuration files. Of course, once we have them read, we do all sorts of processing.
The stable version of antlr3 is 3.0.1, which happened to give lots of internal errors. It has not been very useful, so I tried a few times the latest beta version 3.1b, and eventually managed to get it to work. If I am not mistaken, 3.1 stable should be announced in a few days.
When using antlr, you have the choice of several target languages, such as Java, C, C++ and Python. I am using the Python target, and the latest version that is available from the antlr3 repository.
Here is the tree of the gb layout file,
tree = (SECTION (MAPTYPE (MAPOPTIONS partial default alphanumeric_keys xkb_symbols) (MAPNAME “basic”)) (MAPMATERIAL (TOKEN_INCLUDE “latin”) (TOKEN_NAME Group1 (VALUE “United Kingdom”)) (TOKEN_KEY (KEYCODEX AE02) (KEYSYMS 2 quotedbl twosuperior oneeighth)) (TOKEN_KEY (KEYCODEX AE03) (KEYSYMS 3 sterling threesuperior sterling)) (TOKEN_KEY (KEYCODEX AE04) (KEYSYMS 4 dollar EuroSign onequarter)) (TOKEN_KEY (KEYCODEX AC11) (KEYSYMS apostrophe at dead_circumflex dead_caron)) (TOKEN_KEY (KEYCODEX TLDE) (KEYSYMS grave notsign bar bar)) (TOKEN_KEY (KEYCODEX BKSL) (KEYSYMS numbersign asciitilde dead_grave dead_breve)) (TOKEN_KEY (KEYCODEX LSGT) (KEYSYMS backslash bar bar brokenbar)) (TOKEN_INCLUDE “level3(ralt_switch_multikey)”))) (SECTION (MAPTYPE (MAPOPTIONS partial alphanumeric_keys xkb_symbols) (MAPNAME “intl”)) (MAPMATERIAL (TOKEN_INCLUDE “latin”) (TOKEN_NAME Group1 (VALUE “United Kingdom – International (with dead keys)”)) (TOKEN_KEY (KEYCODEX AE02) (KEYSYMS 2 dead_diaeresis twosuperior onehalf)) (TOKEN_KEY (KEYCODEX AE03) (KEYSYMS 3 sterling threesuperior onethird)) (TOKEN_KEY (KEYCODEX AE04) (KEYSYMS 4 dollar EuroSign onequarter)) (TOKEN_KEY (KEYCODEX AE06) (KEYSYMS 6 dead_circumflex NoSymbol onesixth)) (TOKEN_KEY (KEYCODEX AC11) (KEYSYMS dead_acute at apostrophe bar)) (TOKEN_KEY (KEYCODEX TLDE) (KEYSYMS dead_grave notsign bar bar)) (TOKEN_KEY (KEYCODEX BKSL) (KEYSYMS numbersign dead_tilde bar bar)) (TOKEN_KEY (KEYCODEX LSGT) (KEYSYMS backslash bar bar bar)) (TOKEN_INCLUDE “level3(ralt_switch)”))) (SECTION (MAPTYPE (MAPOPTIONS partial alphanumeric_keys xkb_symbols) (MAPNAME “dvorak”)) (MAPMATERIAL (TOKEN_INCLUDE “us(dvorak)”) (TOKEN_NAME Group1 (VALUE “United Kingdom – Dvorak”)) (TOKEN_KEY (KEYCODEX BKSL) (KEYSYMS numbersign asciitilde)) (TOKEN_KEY (KEYCODEX AE02) (KEYSYMS 2 quotedbl twosuperior NoSymbol)) (TOKEN_KEY (KEYCODEX AE03) (KEYSYMS 3 sterling threesuperior NoSymbol)) (TOKEN_KEY (KEYCODEX AE04) (KEYSYMS 4 dollar EuroSign NoSymbol)) (TOKEN_KEY (KEYCODEX LSGT) (KEYSYMS backslash bar)) (TOKEN_KEY (KEYCODEX AD01) (KEYSYMS apostrophe at)))) (SECTION (MAPTYPE (MAPOPTIONS partial alphanumeric_keys xkb_symbols) (MAPNAME “mac”)) (MAPMATERIAL (TOKEN_INCLUDE “latin”) (TOKEN_NAME Group1 (VALUE “United Kingdom – Macintosh”)) (TOKEN_KEY (KEYCODEX AE02) (KEYSYMS 2 at EuroSign)) (TOKEN_KEY (KEYCODEX AE03) (KEYSYMS 3 sterling numbersign)) (TOKEN_INCLUDE “level3(ralt_switch)”)))
When traversing the tree, we can then pretty-print the layout at wish:
partial default alphanumeric_keys xkb_symbols “basic” {
name[Group1] = “United Kingdom”;
include “latin”
include “level3(ralt_switch_multikey)”
key <AE02> = { [ 2 , quotedbl , twosuperior , oneeighth ] };
key <AE03> = { [ 3 , sterling , threesuperior , sterling ] };
key <AE04> = { [ 4 , dollar , EuroSign , onequarter ] };
key <AC11> = { [ apostrophe , at , dead_circumflex , dead_caron ] };
key <TLDE> = { [ grave , notsign , bar , bar ] };
key <BKSL> = { [ numbersign , asciitilde , dead_grave , dead_breve ] };
key <LSGT> = { [ backslash , bar , bar , brokenbar ] };
};
… snip …
The code is currently hosted at code.google.com (keyboardlayouteditor) and I intend to move it shortly to FDO.
Take Back The Tech #2!
Last year we talked about the Take Back The Tech, an initiative by the Association for Progressive Communications, Women’s Networking Support Programme (APC WNSP) to stop violence against women with the use of Information and Communication Technologies (ICT), that took place between the 25th November and the 10th December. The same initiative runs this year during the same days (25th November to 10th December). At the time of writing this the event is at Day 8 of the 16-day event.

Violence Against Women (VAW) can also be perpetrated through the use of ICT (such as being a victim of targeted spyware or malicious online intimidation). Therefore, a better use of ICT (Take Back The Tech!) would help mitigate online-related VAW and reclaim the control of technology.
You can start your own campaign and join the existing ones that are in place. In Europe there are existing campaigns in the UK and Skopje.
Here is the announcement for this year,
***************************
ka-BLOG! TAKE BACK THE TECH!
www.takebackthetech.net
25 Nov to 10 Dec
***************************ka-BLOG! Calling all bloggers to contaminate the blogosphere with
activism on VAW for 16 days.ka-BLOG is a 16-day blog fest for the Take Back the Tech Campaign. It
is open to anyone and everyone – girls, boys, everyone beyond and more
– who want to share their thoughts on violence against women, and how
online communications can exacerbate or help eliminate VAW.We welcome bloggers in different languages!
ka-BLOG with us
![]()
For more information, go http://www.takebackthetech.net, or email jac
AT apcwomen DOT org[FYI. In Filipino slang, "ka-BLOG" would mean someone you blog with.]
Say No to OOXML
Click on the image above to visit the petition page.
I copy here the terms of the petition to say no on the standardisation of MSOOXML at ISO.
I ask the national members of ISO to vote “NO” in the ballot of ISO DIS 29500 (Office OpenXML or OOXML format) for the following reasons:
- There is already a standard ISO26300 named Open Document Format (ODF): a dual standard adds costs, uncertainty and confusion to industry, government and citizens;
- There is no provable implementation of the OOXML specification: Microsoft Office 2007 produces a special version of OOXML, not a file format which complies with the OOXML specification;
- There is missing information from the specification document, for example how to do a autoSpaceLikeWord95 or useWord97LineBreakRules;
- More than 10% of the examples mentioned in the proposed standard do not validate as XML;
- There is no guarantee that anybody can write a software that fully or partially implements the OOXML specification without being liable to patent damages or patent license fees by Microsoft;
- This standard proposal conflicts with other ISO standards, such as ISO 8601 (Representation of dates and times), ISO 639 (Codes for the Representation of Names and Languages) or ISO/IEC 10118-3 (cryptographic hash);
- There is a bug in the spreadsheet file format which forbids to enter any date before the year 1900: such bugs affects the OOXML specification as well as software versions such as Microsoft Excel 2000, XP, 2003 or 2007.
- This standard proposal has not been created by bringing together the experience and expertise of all interested parties (such as the producers, sellers, buyers, users and regulators), but by Microsoft alone.
This project is an initiative by the Foundation for a Free Information Infrastructure (FFII), the non-profit that helped achieve the rejection of the EU software patent directive in July 2005.
Update #1: Currently (26Jun07 – noon) there are 8805 signatures.
Update #2: Currently (26Jun07 – evening) there are 9481 signatures.
Update #3:
IT IS URGENT THAT YOU CONTACT YOUR STANDARDISATION BODY IN YOUR COUNTRY AND EXPLAIN THEM WHY OOXML IS BROKEN; SENDING A NICE LETTER TO YOUR STANDARDISATION BODY IN YOUR COUNTRY IS MORE IMPORTANT THEN SIGNING THE PETITION
My Akismet spam count in WordPress
Here is the Akismet spam count of my WordPress blog,
All spam deleted.
Caught SpamAkismet has caught 316,645 spam for you since you first installed it.
You have no spam currently in the queue. Must be your lucky day.
![]()
WordPress
Documentation — Support Forums
2.1 — 0.10 seconds
The OLPC and Greek
(oh, I am writing this through a lousy Net connection; thanks Engelados)
I tried out the latest OLPC image, specifically build 218, on Qemu and my aim was to get Greek support configured, if it was not there already.
The OLPC does not currently come with a good set of Greek fonts; you will need to install a set of fonts such as DejaVu or GFS Didot.
Installing means adding the font files in the directory /usr/share/fonts/. The current font configuration files in the OLPC favour Bitstream Vera, therefore you would need to move the bitstream subdirectory outside the fonts directory. DejaVu is based on Bitstream Vera and therefore you will not notice any change once you upgrade. Also, Fedora Core 6 and Ubuntu Linux are based on DejaVu. You need DejaVu, as Bitstream Vera does not currently support Greek. Both DejaVu and GFS Didot are free and open-source fonts.
Note: This screenshot shows DejaVu Sans, not GFS Didot. Sorry for the typo.
This is the OLPC running the cut-down version of the Abiword wordprocessor. Click on the image to view the full size.
This is the OLPC showing the same document above with GFS Didot. The font looks quite nice and similar to old greek textbooks. There is a small issue however, it does not have the character coverage of DejaVu. For example, notice that the Euro sign is missing from GFS Didot. Also, other glyphs such as fancy bullet characters are missing as well. Normally, the OLPC software should replace those missing characters with the correct characters from another font. Apparently something is wrong here and needs further investigation.
Writing support for the Greek language has to be configured separately in the OLPC. The case with other languages appears to be that the default layout is that of the language; apparently there is no need to switch between Brazilian Portuguese and English. For the Greek language it appears that it is good to be able to switch between Greek and English.
There are several places that you can add Greek writing support. The most common is in /etc/X11/xorg.conf. Having gone through the configuration files, I think that /etc/X11/Xkbmap is also a good place and saves us from touching the core Xorg configuration file.
To write the full set of Greek letters, one needs to set the extended variant for the Greek layout, and also try to set the Compose key (for ano teleia). These things should be simplified…
I am not sure how the OLPC looks like (the only photos I saw where not focusing on the keyboard). Perhaps it would be useful to have a test machine at my disposal (hint, hint).
Jim Gettys wrote at his blog about the different languages that the first generation of the OLPC should support. Both Kinyarwanda and Kiswahili use the latin alphabet, therefore there are no significant issues with font support or writing support.
p.s.
Greece will carry out a pilot with OLPC laptops next September.
International Call for Artists’ film and video
AT HOME IN EUROPE
Generous European Culture2000 funding enables ISIS Arts (UK) and it’s
international project partners BEK (Norway), InterSpace (Bulgaria) and
RIXC (Latvia) to curate a NEW SCREENING PROGRAMME around the theme of
European Identity for the Big M, ISIS Art’s inflatable touring space.
Daily, more and more European people decide to live in other European
countries. With a shifting concept of nationality it becomes
increasingly important to consider what it means to be European. Is
there such a thing as European Identity and how does it relate to
national identity?
For this programme we invite submissions of films or video works on this
theme from artists of any nationality.
Selected works will become part of the new screening programme which
will tour to the four partnering countries between May 2007 and
September 2007.
Work will be selected through open submission. In order to be considered
individual works must:
- Have a running time of 5 minutes or less
- Be single channel and non interactive
- Address the project theme
Selected artists will receive an exhibition fee of € 300 (The Big M is
not a commercial venture and admission is free). Copyright remains
solely with the artist.
The Big M is a highly stylised inflatable structure that functions as a
temporary and mobile venue for the presentation of video and digital
media. Unique in both design and function, the Big M provides an
alternative to the conventional gallery setting and exhibits work by
emerging and established artists to diverse audiences.
See: http://www.isisarts.org.uk/index2.html
To submit pieces for consideration please send work on DVD, CD Rom (720x
576 dpi QuickTime movie) or mini DV, titled and with a synopsis of 50
words maximum, a CV and a stamped addressed envelope (if you want your
materials returned) to:
BEK
C Sundtsg 55
9. etage
5004 Bergen
Norway
Deadline for receipt of submissions is the 3rd of February 2007
Further inquiries to isis at isisarts dot org dot uk
Further project information can be found on
To submit pieces for consideration please send work on DVD, CD Rom (720x
576 dpi QuickTime movie) or mini DV, titled and with a synopsis of 50
words maximum, a CV and a stamped addressed envelope (if you want your
materials returned) to:
BEK
C Sundtsg 55
9. etage
5004 Bergen
Norway
Deadline for receipt of submissions is the 3rd of February 2007
Further inquiries to isis at isisarts dot org dot uk
Further project information can be found on
Simos Xenitellis on Ubuntu Font Beta and Greek
Popular posts
- How to install the 64-bit Adobe Flash Player 10 for Linux in Ubuntu Linux?
- Laptop without Windows, an update for Dell, Asus, Acer, Compaq
- Αναβαθμιστείτε από hotmail σε GMail.com
- How to type Greek, Greek Polytonic in Linux
- ΝΑΙ! Mozilla Firefox No1 στην Ελλάδα!
- OpenType support in OpenOffice 3.2 (Greek)
- Workaround for bad fonts in Google Earth 5 (Linux)
- Ελληνικό ελεύθερο λογισμικό text to speech (TTS)
- Ελληνικό διαβατήριο
- Microsoft Windows tax refund, from Dell
- Installing Greek spelling and hyphenation in OpenOffice.org 2.0
- Στατιστικά χρήσης Mozilla Firefox στην Ευρώπη
- Διανομή Linux για μικρά συστήματα
- Επίπεδο στάθμης της θάλασσας στην Ελλάδα
- Ελληνικά θέματα για WordPress
- Ορθογραφία και συλλαβισμός σε OpenOffice.org 2.0
- Είναι ο nkour μπελάς;
- Πάροχοι mobile internet (3G) στην Ελλάδα και GNOME/Linux
- The bashrc bash configuration files
- Περισσότερες γραμματοσειρές
- Τι είναι τα αρχεία .odt;
- Can you read Coptic?
- Το αυγό και η κότα
- Ποιά είναι η εσωτερική έκδοση του OpenOffice.org μ...
- Αεροφωτογραφίες της Ελλάδας από το Υπουργε...
- Picasa, Hello και Blogspot
- Έτοιμη η μετάφραση του WordPress!
- Μετατροπή συντεταγμένων μεταξύ WGS 84 (π.χ. GPS) ...
- Χαρτογράφηση με OpenStreetMap (OSM) και Ελλάδα
- Stix Fonts, eventually out.
- “The Thing about Volunteers and Civility” (#modernperlbooks.com)
- OpenOffice.org και ελληνικές γραμματοσειρές
Tags
webpage
- IRC #ubuntu-gr
- Ελληνικό GNOME
- Ελληνικός Firefox
- Κοινότητα ELLAK.gr
- Κοινότητα Ubuntu-gr
- Πλανήτης GNOME.gr
- Πλανήτης ΕΛ/ΛΑΚ
- Προσωπική Σελίδα
- Φόρουμ Ubuntu-gr
Categories
- activism (9)
- blog (12)
- fdo (8)
- fonts (16)
- general (216)
- gnome (31)
- i18n (39)
- language (32)
- Linux (30)
- multimedia (10)
- olpc (2)
- open-source (45)
- pgo (8)
- photography (5)
- Planet Ubuntu (6)
- planetellak (109)
- pofo (3)
- polytonic (13)
- security (9)
- travel (6)
- ubuntu (39)
- uncategorized (184)
- WordPress (5)
Calendar
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jul | ||||||
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | 31 | |||||
Archives
- July 2010 (1)
- June 2010 (4)
- May 2010 (3)
- April 2010 (3)
- February 2010 (2)
- January 2010 (3)
- August 2009 (1)
- July 2009 (1)
- June 2009 (6)
- May 2009 (8)
- April 2009 (2)
- February 2009 (3)
- January 2009 (2)
- December 2008 (3)
- November 2008 (6)
- October 2008 (5)
- August 2008 (3)
- July 2008 (7)
- June 2008 (6)
- May 2008 (7)
- April 2008 (2)
- March 2008 (8)
- February 2008 (6)
- January 2008 (1)
- December 2007 (4)
- November 2007 (3)
- October 2007 (2)
- August 2007 (5)
- July 2007 (5)
- June 2007 (6)
- May 2007 (6)
- April 2007 (11)
- March 2007 (10)
- February 2007 (4)
- January 2007 (5)
- December 2006 (2)
- November 2006 (3)
- October 2006 (6)
- September 2006 (2)
- July 2006 (7)
- June 2006 (19)
- May 2006 (30)
- April 2006 (6)
- March 2006 (12)
- February 2006 (20)
- January 2006 (11)
- December 2005 (12)
- November 2005 (9)
- October 2005 (15)
- September 2005 (9)
- August 2005 (20)
- July 2005 (15)
- June 2005 (15)
- May 2005 (11)
- April 2005 (12)
- March 2005 (18)
- February 2005 (11)
- January 2005 (3)
- December 2004 (9)
- November 2004 (19)
- October 2004 (3)
- September 2004 (11)
- August 2004 (10)
- July 2004 (6)
- June 2004 (18)
- May 2004 (20)
- April 2004 (17)






