Questions of code standards

I wish to propose a package I developed called Services_Shipping (I hope) that provides a unified driver-based abstract shipping API, similar to how MDB2 provides portable database package and Payment_Process provides driver-based transactions. I code in a different way than PEAR's coding style standards, mainly I use tabs and don't like spaces between my opening brackets. I use Eclipse currently and will likely create an Eclipse formatting profile for formatting to PEAR standard. 1.) Anyone currently code using tabs and have an Eclipse or bash script (using some whitepsace program) that formats to PEAR standards? 2.) My PEAR package has 80+ source files, is this a problem? I am not interested in combining source files into larger ones. 3.) Should I include my 2 driver packages (UPS and DHL) in my original proposal for Services_Shipping (these would be Services_Shipping_UPS and Services_Shipping_DHL, correct?) 4.) Should I generate documentation (phpDocumentor) and include the documentation or only submit my code and PEAR will generate the doc? 5.) After proposal will I get a reason why my package isn't accepted so I may fix the issues and re-submit? Is there a limit on how quick I may re-submit my proposal? Peace My PHP Ganstas, Kristopher Ives