On Mon, Aug 09, 2010 at 04:19:52PM +0530, Baiju M wrote: > On Mon, Aug 9, 2010 at 3:56 PM, Baiju M <[email protected]> wrote: > > Hi Justin, > > > > On Sat, Aug 7, 2010 at 2:50 AM, Justin Ryan <[email protected]> wrote: > >>> > >>> Of course, there's quite a few, so I'll do my best to condense.. > >>> > >> > >> Here's a start: > >> > >> http://bluebream.bitmonk.net/doc/1.0/manual/i18nl10n.html > >> > >> just based on http://wiki.zope.org/zope3/i18noverview.html so far, > >> will continue incorporating others.. > > > > Great ! > > > > I have added these details to our doc issue tracker: > > http://wiki.zope.org/bluebream/16NativeLanguageSupportI18nAndL10n > > > > FYI, The message factory class named is changed to "MessageFactory" > > from MessageIDFactory: > > > > from zope.i18nmessageid import MessageFactory > > I was looking at source of your document: > http://bluebream.bitmonk.net/doc/1.0/_sources/manual/i18nl10n.txt > > Currently I am using 69 as the maximum width of each line. > But I think we increase that up to 80 characters.
Better make that 76: leave some space for the unified diff's "+"/"-"
and a level of email quoting ("> ").
> With very long lines, it is difficult to review patches in Unified
> diff format [1] from a terminal. It's Okay to use more than
> 80 characters in lines where you cannot break lines (source code).
>
> [1] http://en.wikipedia.org/wiki/Diff
Marius Gedminas
--
But perhaps ISO's central secretariat follows just the common industry
practice pioneered by Microsoft: "We will get it right in the third
release."
-- Markus Kuhn on ISO 10646 PDF CD-ROM edition
signature.asc
Description: Digital signature
_______________________________________________ bluebream mailing list [email protected] https://mail.zope.org/mailman/listinfo/bluebream
