Shreef

I wish you all muslims a happy eftar feast :-).

don’t worry, I’m not planning to make it a long heavy post ( this is the feast people ). just keep reading and stop eating cookies and biscuits.

 

The first thing in this post is about women !!

Manual Lemos the founder and manager of phpclasses.org posted in his blog about a group of women working to united all the women participating in the PHP world in one user group called PHPWomen .

I like the idea. maybe this will encourge more women to get in the PHP world. I can imagine myself working in a company and all my colleagues in the room are young pretty women know the difference between web cookies and biscuits. lol

also there is comunity for women who like Linux called LinuxChix . ( any body intersted in creating any geeky comunity for men ?!! ).

 

okay, the next thing is about the PHP Security Consortium. Ed Finkler is leading a project called PHPSecInfo. the aim of the project is providing the developers with something like phpinfo() which generates security reports about their PHP environment with suggestions to get that PHP environment more secure.

I read a little in the API but maybe I will check it later for more details. I have added that to my To-Do List . maybe I will write a full post about it after that — in shaa ALLAH.

 

where are you going?! I didn’t finish this post.

here is some funny geeky comics from The Joy of tech website

 

I have installed the new IE7 hour ago. allot of new features where added but the best thing is how the space is organized.

IE7 is nice but I had to get back to FF. the reason is that I can’t get my eyes comfortable with IE7′s blury effect and brightness. I’m using a FF extension called IE Tab , I think that you will love it if you are using FF as your main browser.

 

Another thing, I want to quote from Kevin Yank’s comment on this post :

 

As web developers, we don’t have the luxury of picking our favourite browser

and ignoring the rest. I think it’s safe to say that Firefox and its kin will remain popular

among developers, but IE7 is a new platform we must deal with, regardless of whether

or not it has a Linux version or mouse gestures.

 

Okay, it’s my birthday but a little of programming won’t be a bad thing :).

 

Andre Hoffmann who’s developing the Zend_Locale_UTF8 component is going to support the localization of numbers. f.e. you can display the numbers ( 0123456789 ) using Arabic digits ( ٠١٢٣٤٥٦٧٨٩ ) . this functionality will be used in other components like Zend_Currency and Zend_Locale_Format.

 

Andre didn’t start working on it till now. this idea is still under discussion on the ZF-i18n mailinglist. we are now building our decisions depending on scenarios of Arabic digits. if your language isn’t using the normal english digits (0123456789), it will be nice if you can help with some information to get your language’s digits supported well.

 

OT: I hope that we can get more Arabic developers working on ZF. you will get more experienced of things you didn’t think about before.

It’s 17th-10-2006 , I’m 19 now

I’m Still working on the translation of the ZF-Docs to Arabic. in my last post I was talking about the problem we faced when we was trying to get the arabic words displayed from right to left “RTL” in DocBook and what I did to hack the XSL files to get it working.

 

yesterday, one of the zend guys asked me about if modifying the DocBook XSL files is best practice or using CSS ? his point of view was that using css is more cleaner and this can be a best practice.

I have another point of view which I had to explain it to him. in our situation using markup isn’t similar to using css.

 

here is part of my replay to him:

================

 
     1- ignoring the css “direction” property is possible in any user agent as this is part of the styling . 

2- this inherits from 1 . css have to be used only for styling and we are here not styling but we are setting the direction of the data .
the directionality here is part of the data as the data will lose it’s value if not displayed in the right way. so using the markup “dir” attribute is the right solution.
it can’t be ignored by user agents and it’s part of the data and not part of the styling.

—————————————-