I take it back, my apologizes "I you wont help solve the problem don't become part of the problem"
now translating from English to Spanish http://www.symfony-project.org/cookbook/1_1/directory_structure On Jun 9, 3:41 pm, arhak <[EMAIL PROTECTED]> wrote: > You're right! > It should be marked in capitals, but instead it is signaled as a "To > Do" somewhere in Symfony's site. > The major reason for me to not try sf1.1 is the lack of documentation, > according to Zaninotto the documentation will be almost the API's > documentation itself. > > On Jun 8, 6:08 pm, "Nicolas Garnault" <[EMAIL PROTECTED]> > wrote: > > > Hey there, > > > I was just surfing on the Symfony Cookbook for sf1.1, and I finally realized > > that the articles posted where not all "sf1.1 compliant" (for example, the > > "how to upload a file" doesn't seem to deal a lot with sfForm ...). > > Maybe I'm just a nerd but I think this is quite dangerous to put outdated > > documentation like this on the sf website *even if it is clearly and loudly > > said that this is WIP*. > > Shouldn't we tag those outdated articles and howto as "needing to be > > updated" ? I think the current way articles are posted can be dangerously > > disappointing for any user who would like to deal with sf1.1 (moreover, this > > kind of "need to be updated" indication could help in motivating people to > > update the documentation). > > > Am I wrong ? > > > Taku > > > ps : sorry for my poor english --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
