headers
Sina Khakbaz Heshmati | 1 May 2010 03:54
Gravatar

New DocBook Developers: Voilà je me présente!

L.S.,

Alright folks, it's time to break the ice ;) My name is Sina -aka. SinDoc [1]. I have recently joined the
DocBook community as part of the Google Summer of Code program. Dave Pawson is my mentor while I help
re-implement DocBook Website.

First things first; I assume I should post Website schema-related issues on the 'docbook' list whereas
_general_ inquiries as to the DocBook Website requirements and their implementation should be asked on
the 'docbook-apps' list. Is that OK?

I look forward to a healthy interaction and exchange of knowledge with the DocBook community and would like
to take this opportunity to thank you for having me among you.

SinDoc

[1] http://twitter.com/sindoc
Permalink | Reply | 2 comments |
headers
Øyvind A. Holm | 1 May 2010 04:59
Favicon
Gravatar

Re: DocBook XSL Stylesheets v1.75.2 uses US date format

I (Øyvind) wrote some days ago:
>  I just regenerated some documentation in a project of mine using the
>  DocBook XSL Stylesheets v1.75.2, and noticed that the generated date
>  at the man page is in the US date format:
>
>      .\"      Date: 04/25/2010
>
>  [...]
>
>      .TH "GPST" "1" "04/25/2010" "[FIXME: source]" "[FIXME: manual]"
>
>  This is ambiguous and prone to errors when the date is for example
>  "01/02/03". Is it 2003-02-01, 2003-01-02, or even 2001-02-03?

Thanks for the answers, Larry and Mauritz. I have created custom XSL
sheets before, but didn't think about doing it this time. For the
record, I ended up with this:

    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
      <xsl:import
href="/usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl"/>
      <xsl:param name="local.l10n.xml" select="document('')"/>
      <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
        <l:l10n language="en">

          <!-- Get rid of ambiguous US date format -->
          <l:context name="datetime">
            <l:template name="format" text="Y-m-d"/>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dick Hamilton | 2 May 2010 23:07
Favicon
Gravatar

RE: [docbook] New DocBook Developers: Voilà je me présente!

Sina,

Welcome to the list and congratulations on having your proposal accepted
for the Google Summer of Code program. We look forward to following your
progress.

Best Regards,
Dick Hamilton
---------------------------------
XML Press
XML for Technical Communicators
http://xmlpress.net
(970) 231-3624 

> -----Original Message-----
> From: Sina Khakbaz Heshmati [mailto:sina <at> khakbaz.com] 
> Sent: Friday, April 30, 2010 7:54 PM
> To: DocBook Mailing-List
> Subject: [docbook] New DocBook Developers: Voilà je me présente!
> 
> 
> L.S.,
> 
> Alright folks, it's time to break the ice ;) My name is Sina 
> -aka. SinDoc [1]. I have recently joined the DocBook 
> community as part of the Google Summer of Code program. Dave 
> Pawson is my mentor while I help re-implement DocBook Website.
> 
> First things first; I assume I should post Website 
> schema-related issues on the 'docbook' list whereas _general_
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sina Khakbaz Heshmati | 7 May 2010 03:28
Gravatar

Website5: Project Codename

L.S.,

Dave and I decided to start a project on GitHub [*] for our summer project i.e. Website re-implementation.
Any suggestions as to the codename?

Regards,
SinDoc

[*] Is it alright if we commit to another repository or is it better to use the DocBook repository?
Permalink | Reply | 3 comments |
headers
Richard Hamilton | 9 May 2010 10:31
Favicon
Gravatar

Re: Website5: Project Codename

Sina,

Eventually, the code will need to be merged into the docbook repository,
and possibly also dropped into a Google repository.

That said, I don't see any problem using another repository for
development. Does anyone see a problem with that?

Dick
On Fri, 2010-05-07 at 03:28 +0200, Sina Khakbaz Heshmati wrote:
> L.S.,
> 
> Dave and I decided to start a project on GitHub [*] for our summer project i.e. Website re-implementation.
Any suggestions as to the codename?
> 
> Regards,
> SinDoc
> 
> [*] Is it alright if we commit to another repository or is it better to use the DocBook repository?
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-unsubscribe <at> lists.oasis-open.org
> For additional commands, e-mail: docbook-help <at> lists.oasis-open.org
>
Permalink | Reply | 2 comments |
headers
Keith Fahlgren | 9 May 2010 22:05
Picon
Gravatar

Re: Website5: Project Codename

On Sun, May 9, 2010 at 1:31 AM, Richard Hamilton <rlhamilton <at> frii.com> wrote:
> Eventually, the code will need to be merged into the docbook repository,
> and possibly also dropped into a Google repository.
>
> That said, I don't see any problem using another repository for
> development. Does anyone see a problem with that?

I would prefer that DocBook-XSL code continued to be consolidated in
the SVN repository at
https://docbook.svn.sourceforge.net/svnroot/docbook (feel free to use
a branch). That said, if there are compelling reasons for hosting it
elsewhere *OR* if the project would work better as a standalone entity
that interoperated well with DocBook-XSL (and there are a lot of
downsides to integrating into a project as huge as DocBook-XSL), go
for it.

Keith
Permalink | Reply | 1 comment |
headers
Dick Hamilton | 10 May 2010 18:20
Favicon
Gravatar

RE: Website5: Project Codename

Keith's note and this thread are causing me to lean more strongly
towards using the standard repository.

But, if you do end up with a separate repository, please make sure that
it is open for reading by anyone, so we have the same level of access as
we currently have to the DocBook repository.

Dick
---------------------------------
XML Press
XML for Technical Communicators
http://xmlpress.net
(970) 231-3624 

> -----Original Message-----
> From: Keith Fahlgren [mailto:abdelazer <at> gmail.com] 
> Sent: Sunday, May 09, 2010 2:05 PM
> To: Richard Hamilton
> Cc: Sina Khakbaz Heshmati; docbook <at> lists.oasis-open.org; 
> docbook-developers
> Subject: Re: [docbook] Website5: Project Codename
> 
> 
> On Sun, May 9, 2010 at 1:31 AM, Richard Hamilton 
> <rlhamilton <at> frii.com> wrote:
> > Eventually, the code will need to be merged into the 
> docbook repository,
> > and possibly also dropped into a Google repository.
> >
> > That said, I don't see any problem using another repository for
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Quadling | 13 May 2010 10:48
Gravatar

What should the return type be for constructorsynopsis and destructorsynopsis.

Hi.

I'm refining some documentation (PHP) which has used methodsynopsis
for the constructor and the destructor ...

  <methodsynopsis>
   <type>void</type>
   <methodname>HttpRequestPool::__construct</methodname>
   <methodparam choice="opt">
      <type>HttpRequest</type>
      <parameter>request</parameter>
   </methodparam>
  </methodsynopsis>

is now ...

  <constructorsynopsis>
   <void />
   <methodname>HttpRequestPool::__construct</methodname>
   <methodparam choice="opt">
      <type>HttpRequest</type>
      <parameter>request</parameter>
    </methodparam>
  </constructorsynopsis>

Is this "correct"?

For "void", the tdg says "An empty element in a function synopsis
indicating that the function in question takes no arguments", but
later says "The Void element produces generated text that indicates
(Continue reading)

Permalink | Reply | 2 comments |
headers
Richard Quadling | 13 May 2010 11:09
Gravatar

Re: What should the return type be for constructorsynopsis and destructorsynopsis.

On 13 May 2010 09:48, Richard Quadling <rquadling <at> googlemail.com> wrote:
> Hi.
>
> I'm refining some documentation (PHP) which has used methodsynopsis
> for the constructor and the destructor ...
>
>  <methodsynopsis>
>   <type>void</type>
>   <methodname>HttpRequestPool::__construct</methodname>
>   <methodparam choice="opt">
>      <type>HttpRequest</type>
>      <parameter>request</parameter>
>   </methodparam>
>  </methodsynopsis>
>
>
> is now ...
>
>  <constructorsynopsis>
>   <void />
>   <methodname>HttpRequestPool::__construct</methodname>
>   <methodparam choice="opt">
>      <type>HttpRequest</type>
>      <parameter>request</parameter>
>    </methodparam>
>  </constructorsynopsis>
>
> Is this "correct"?
>
> For "void", the tdg says "An empty element in a function synopsis
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stefan Seefeld | 13 May 2010 17:32
Picon
Favicon

Re: What should the return type be for constructorsynopsis and destructorsynopsis.

On 05/13/2010 04:48 AM, Richard Quadling wrote:
> Hi.
>
> I'm refining some documentation (PHP) which has used methodsynopsis
> for the constructor and the destructor ...
>
>    <methodsynopsis>
>     <type>void</type>
>     <methodname>HttpRequestPool::__construct</methodname>
>     <methodparam choice="opt">
>        <type>HttpRequest</type>
>        <parameter>request</parameter>
>     </methodparam>
>    </methodsynopsis>
>
>
> is now ...
>
>    <constructorsynopsis>
>     <void />
>     <methodname>HttpRequestPool::__construct</methodname>
>     <methodparam choice="opt">
>        <type>HttpRequest</type>
>        <parameter>request</parameter>
>      </methodparam>
>    </constructorsynopsis>
>
> Is this "correct"?
>
> For "void", the tdg says "An empty element in a function synopsis
(Continue reading)

Permalink | Reply | 0 comments |

Gmane