User:Lvl/Devel/Questions pending
Questions awaiting answers on the dev. list
link to the dev list archives
Unless I missed something, here are some topics I'm interested in for which questions are waiting for an answer or some kind of decision. I'm trying to put that here, because of the limitations of the developpers mailing list (no ability to link to a previous message easily, or to post a response if you don't have that message in your own mailbox)
Disclaimer: This is not ready for discussion with fellow developpers. Work in progress.
July 2009
Special access rights for testing internationalisation
- I don't think translators need to fully test the site in a language if we properly gettext() the strings, including adding appropriate "// TRANSLATOR:" hints. If we do want to have some language reviewer to validate privileged pages it would probably be simplest to do that on a case-by-case basis. cpeel
What should not be internationalised
- I think having the admin interface translated would be nice, but is a very low priority (as you've already specified on the User:Lvl/Devel/Distributed gettext fixing effort page. Ditto tasks.php. Things like the PPV reports are going to be an oddity because the locale that sends them out ('cause those are sent via email, right?) may not be the locale that the user reads. We should identify these types of problems (jpgraph code has this challenge) but I don't think we need to dwell on fixing them at the moment. We should not translate obsolete code. Identifying and removing obsolete code is a whole other ballgame however :/ cpeel
naming scheme to translate FAQ documents
- perhaps this should be revisited if we move the docs to the wiki.
doing many simple changes over many files
A question about maintenance mode
August 2009
DP coding convention Michael and Casey agreeing to moving these to separate wiki pages. probably depends on agreement about long lines and gettext stuff.
Site customization Michael's views on customisation. No answers yet.
October 2009
- TODO, check that forum pointed to by the install doc.
about column postprocessor in users table
comments on files in Coachmike's sandbox
- apparently these files had already been reviewed. No idea if what I wrote was meaningful or not. Still no idea on how to move forward on the translation front.
November 2009
More detailed
multiple lines and gettext
multiline strings and xgettext?
lvl2@cl... wrote: > I suspect that this sentence in our Best Practices: > >> "Don't break the string over multiple lines: xgettext will >> only pick up the first. (Yes, this can lead to some long lines.)" > > is not (or no longer) true.
I had a discussion on Jabber with Michael, and we agreed to reword the Best Practices. Solved.
long lines in best practices
On Thu, Jul 30, 2009 at 11:50 AM, Casey Peel<cpeel@ke...> wrote: > On Wed, 2009-07-29 at 17:05 +0200, laurent vogel wrote: > >> Speaking about coding standards, are there any kind of requirement >> to avoid exceedingly long lines? > > We haven't (yet) established any recommendation about exceedingly long > lines. I generally try to keep my lines between 80-100 characters max but > I'm not very consistent. > > It appears that 80 characters is pretty common (allowing for overflow to 120 > in some cases): > http://framework.zend.com/manual/en/coding-standard.php-file-formatting.html > http://pear.php.net/manual/en/standards.indenting.php > http://paul-m-jones.com/?p=276 > > Do others have thoughts about adopting this as part of our DP coding > standard?
Don just answered that PEAR is nice. No other comments.