Hi Thuy,
I can try and help, but not sure that I have all the answers either.
>
> But still I confuse how to commit my document into this branches. Please
> help me.
> As I understand,
> 1. I need to transfer my document into xml format,
This is a pretty painful process the first time. I have copi
Hi Thuy,
Glad something worked. It would be good if you could document what you
have done with the CSS and POM, adding it to the documentation guide,
so that other users will know what to do as well (like me!). :)
Best regards,
jason
On Sat, Oct 17, 2009 at 6:02 AM, Thuy Nguyen wrote:
> Hi J
Hi there HISP Viet Nam. First of all, a great job on the user manual,
and of course the functionality! I have yet to use it, but now with
some documentation, I think I may be able to give it a try.
With the last commit, I have redone the pom.xml file a bit, as HTML
image links were broken for me.
Hi there.
Now that there has been some additional contributions to the
documentation branch, I wanted to take some time to review the
feasibility of concurrent editing. Here are my initial findings. The
Viet Nam team has produced a document on the Excel Report module and I
wanted to make a few cha
Howdy. I have managed to modify, I think, the directory structure a
bit to make the creation of multilingual version of documents a bit
more manageable. I will update the documentation guide soon on exactly
what the procedure is. Briefly, all documents for a given language
should be placed into the
I have seen this several times on Linux as well. No idea what causes it.
I seemed to be able to solve it on Linux by "touch
dhis2_user_man_mod3.xml" once (but not a second time), and another
time by opening the file, and saving it with no alterations. No clue
why. There seems to be some sort of ca
Hi Knut,
I suspect again this has to do with CygWin. Has it worked before? What
is the v: drive? Are you sure that Cygwin can access this path?
Regards,
Jason
On Tue, Nov 17, 2009 at 11:48 AM, Knut Staring wrote:
> Hi Jason,
>
> I built all the docs on my laptop several times this morning, incl
d
>> wrote:
>>>
>>> I have the same problem both in cygwin and in cmd so don't think it's
>>> cygwin. Seems to be related to connection as you get a connection time out.
>>> Mine actually just hangs forever at the same place. I would think it rel
,
Jason
On Tue, Nov 17, 2009 at 2:22 PM, Knut Staring wrote:
> It should definitely be possible to build when offline. Are you saying that
> is not the case now?
>
> Knut
>
> On Tue, Nov 17, 2009 at 12:20 PM, Jason Pickering
> wrote:
>>
>> Did you try an m
ealth Organization
> Avenue Appia 20 |1211 Geneva 27, Switzerland | Email:
> titlest...@who.int|Tel: +41 788216897
> Website: www.healthmetricsnetwork.org
>
> Better Information. Better Decisions. Better Health.
>
>
> 2009/11/17 Jason Pickering
>>
>> I do not t
Also, this is a possible resolution. Note that during the build, the
catalog files are missing.
http://www.sagehill.net/docbookxsl/ExampleCatalog.html
This seems to be highly system dependent however.
On Tue, Nov 17, 2009 at 4:17 PM, Jason Pickering
wrote:
> http://docs.codehaus.org/disp
Schweet... works for me as well. Tusend tack Jo.
Another one-line wonder commit!
On Tue, Nov 17, 2009 at 5:50 PM, Lars Helge Øverland
wrote:
>
>
> On Tue, Nov 17, 2009 at 4:42 PM, Jo Størset wrote:
>>
>> Hi,
>>
>> did some tentative changes to the pom, it seemed to work running offline
>> for
Have done some more testing, and it seems to be a great commit.
Building of the documentation is much, much faster.
I will need to update the user docs to specify that the 4.4 schema
should be used. Was this the only choice?
Regards,
Jason
2009/11/17 Jason Pickering :
> Schweet... works for
skrev Jason Pickering:
>
>> Have done some more testing, and it seems to be a great commit.
>> Building of the documentation is much, much faster.
>>
>> I will need to update the user docs to specify that the 4.4 schema
>> should be used. Was this the only choice?
Hi there. I just made a few structural changes to some of the
documents, which I think will be more manageable in the long term.
First, I have converted the India user manuals to chapters instead of
articles. The reason of this was that they really are essentially
chapters of a larger book. There a
Hi Thuy,
I think it would be a good idea. I think that we should restructure
the Excel reporting module into a complete chapter rather than an
appendix actually, as it now forms a core part of the application.
I can do this for you if you want, otherwise just take a look at the
latest commit versu
OK, give it a try based on my diffs, and you should be able to figure
it out. Let me know if you need any help.
Regards,
Jason
On Fri, Dec 4, 2009 at 1:09 PM, Thuy Nguyen wrote:
> I would be very happy to join you so that I can learn something from this.
>
>
>
> --
> --
> Thuy
> HISP Vietnam
>
On a related note, it is also worth taking a look at what the
Geonetwork (a spatial metadata catalogue) has done with DocBook with
their documentation.
http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/trunk/docs/
Regards,
jason
On Tue, Dec 8, 2009 at 7:37 PM, Jason Pickering
wrote
12-08 18:21:43 +
+++ pom.xml 2009-12-09 03:50:34 +
@@ -16,7 +16,7 @@
com.agilejava.docbkx
-
+2.0.10-SNAPSHOT
docbkx-maven-plugin
2009/12/8 Lars Helge Øverland :
>
>
> On Tue, Dec 8, 2009 at 9:45 PM, Jason Pickering
> wrote:
&g
tation is a top priority work for the tanzanian case now.
>
> Lungo
>
>
> Jason Pickering wrote:
>
> Hi Lars,
> Agreed for now.
>
> I have some extra time on my hands right now, so I can try and work on
> this a bit more if you get some more material.
>
>
f this movement.
> we have also created some pieces of documentations.
> for example how to install DHIS2 in Ubuntu, and some health programme
> specific training manuals.
> lets see how we can incoorperate this into the larger document.
>
> Lungo
>
> Jason Pickering wrote:
>
g Tools like oxygen.
>
> Lungo
>
> Original Message
> Subject: Re: [Dhis2-devs] Documentation
> From: Bob Jolliffe
> Date: Wed, December 09, 2009 2:45 pm
> To: Juma Lungo
> Cc: Jason Pickering , Arther HISP
> , John lewis ,
> dhis2-documenters@lists
ment.
> i am still downloading my serna free and its dependencies.
>
> Juma
>
>
> Original Message
> Subject: Re: [Dhis2-devs] Documentation
> From: Jason Pickering
> Date: Wed, December 09, 2009 5:02 pm
> To: "Dr. Juma Lungo"
> Cc: Bo
We are using the maven plugin (docbkx) for DocBook rendering of our
documentation. You may want to have a look at
http://development.nakedobjects.org/trac/browser/framework/branches/reflector-redesign/documentation
which seems to be good example of a very similar documentation effort.
FYI.
Try this one.
http://development.nakedobjects.org/trac/browser/framework/branches/reflector-redesign/documentation?rev=11579
Seems maybe the revision needs to be explicit?
Regards,
Jason
2009/12/10 Lars Helge Øverland :
>
>
> On Thu, Dec 10, 2009 at 4:01 PM, Jason Pickering
> wro
Yeah, the PDF is going to get only bigger and bigger, which is going
to be more and more of a problem. There are the independent chapters
from which the user manual is composed, which can be downloaded
separately.
The HTML is also getting to be too big, due to all the images. I think
the solution
A big congrats to the Vietnamese team for what looks like the first
translation of the DHIS user manual! The documentation has exploded
over the past few months, and this is a great development for the
project. I would have figured that Norwegian would have been the first
language to translate, but
Sounds like a blueprint. :)
2010/3/11 Lars Helge Øverland :
>
>
> On Thu, Mar 11, 2010 at 3:29 PM, Jason Pickering
> wrote:
>>
>> A big congrats to the Vietnamese team for what looks like the first
>> translation of the DHIS user manual! The documentation has explod
Hi there. I do not have the possibility to commit the changes, but
looked quickly at the XML
should be
In general, all images should have an explicit alignment and width
so, you should change the element attributes to be sure that all
images have something like...
wrote:
>
Hi Dao,
Great to see you starting to translate the documentation. This is
really a great step forward.
A few comments here regarding the document. I am not 100% sure of the
content of course, as I do not read Vietnamese, but here are a few
tips..
This looks like a section..
1.1.0.1
I am not
n format
> text.
>
> Please help me check out this trouble.
>
> Again thanks a lot !
>
> 2010/3/23 Jason Pickering
>>
>> Hi Dao,
>> Great to see you starting to translate the documentation. This is
>> really a great step forward.
>>
>>
"escaped" characters in
XML for proper rendering of Vietnamese characters, but I think Google
will know more than me.
Regards,
Jason
2010/3/23 Đào Văn Sâm :
> Dear Jason,
>
> I send an attached file
>
> 2010/3/23 Jason Pickering
>>
>> Hi Sam,
>>
>
I strongly suspect this is an encoding issue as mentioned yesterday.
Also, I do not really understand where the list of complete artifacts
are. Basically, Doxbkx will only build what needs to be built. I think
since the Vietnamese documents have been altered, then they will be
rebuilt. Otherwise,
on http://dhis2.org, i.e. a link to Hudson.
>> The PDF that is there now is very outdated.
>> Knut
>>
>>
>> On Wed, Mar 24, 2010 at 9:04 AM, Jason Pickering
>> wrote:
>>>
>>> I strongly suspect this is an encoding issue as mentioned yesterday.
some time.
Regards,
Jason
On Wed, Mar 24, 2010 at 10:21 AM, Jason Pickering
wrote:
> I am not sure what the issue here is. HTML builds fine for the English
> version, but the PDF looks like something is happening. I will take a
> look at it.
>
>
>
> On Wed, Mar 24, 2010 at
OK. I think this should be fixed. Lets see what Hudson does.
On Wed, Mar 24, 2010 at 10:40 AM, Jason Pickering
wrote:
> Yes, it would appear that the pom is a bit screwed up at the moment. I
> do not have time to look at this at the moment, but I can confirm that
> the English version
Yeah, I just assumed no one would do it, so I took 10 minutes I did
not have, and fixed it.
Anyway, I guess it is working now?
On Wed, Mar 24, 2010 at 1:07 PM, Jo Størset wrote:
>
> Den 24. mars 2010 kl. 10.48 skrev Jason Pickering:
>
>> OK. I think this should be fixed. Lets
A fairly interesting article on the use of DocBook XML within
InDesign. Not really sure how to get this working, but it might be
something we could consider for a more professional layout.
http://partners.adobe.com/public/developer/indesign/sdk/explodedSDK/cs.01/docs/references/sdk/group__xdocbook
Just sitting here talking to Knut, and it would seem that Google translation
may be good enough for a first pass of the translation.
Now, a few issues arise from this.
Management of the pom to generate the documentation, may become a major
problem. Currently, we need quite a bit of XML for each l
DocBkx version 2.0.10 seems to be synced to maven central now. I guess we
can remove the dependency from the pom. Jo?
Hi,
2.0.10 is synched with maven central repository.
Regards,
Cedric,
--
--
Jason P. Pickering
email: jason.p.picker...@gmail.com
tel:+260968395190
___
Currently, we really do not have any licensing on the documentation.
This is probably not a very good idea. I raise this issue, because of
some other questions about licensing of the GIS module, and how this
may conflict with the DHIS2 BSD license.
Anyway, I think we should consider using this..
projects, it is OK, but what if they are
distributed together?
Regards,
Jason
On Tue, May 4, 2010 at 11:33 PM, Knut Staring wrote:
> On Tue, May 4, 2010 at 8:29 PM, Bob Jolliffe wrote:
>> On 4 May 2010 16:34, Knut Staring wrote:
>>> On Tue, May 4, 2010 at 3:35 PM, Jason Pi
Hi Knut,
Thanks for your efforts on this. I am reluctant to move the source
just yet. I think we need to think through the translation workflow a
bit better, and not introduce too many changes at once. We have seen a
few more commits from others, which is a good thing, but of course,
getting involv
omments below.
>
> On Tue, Sep 7, 2010 at 6:32 AM, Jason Pickering
> wrote:
>> Hi Knut,
>> Thanks for your efforts on this. I am reluctant to move the source
>> just yet. I think we need to think through the translation workflow a
>> bit better, and not introduce t
Hi Romain,
This is part of the reason that we created the workflow using Serna,
brz and Launchpad. We have a set of distributed individuals that are
making changes, potentially at the same time, to the same document.
Version control systems are very good at handling and merging these
types of cha
Hi there.
Just to let you know, I have made a few updates to the documentation I
wanted to make everyone aware of.
1) Due to some changes in the DocBook stylesheets, all references to
DocBook elements must now be declared through a namespace in the XSL
document. In the main stylesheet which hand
Some of you may have noticed I have added a bibliography to the main user
manual. Let me explain more or less what I have done, and ask for feedback.
1) A directory has been added to the branch called "bibliography". Contained
in this directory are several files.
dhis2_bibliography.bib- A BIBTEX f
Hi Jens,
I think you make some good points regarding the need for a a better workflow
oriented UI. However this is a much bigger discussion I think which goes
beyond the scope of the documentation.
In terms of documentation, I think the a good way forward would be local
additions to the user manu
Hi Jens,
I took a look at one of the documents you sent. Coming from an academic
background as an engineer, I spent a lot of time in my early days using
expensive pieces of equipment with thick user manuals.It was not always
clear to me why. I think what you have started to write is more of a
pra
s the existing technical manual, a
> new health related text, and the system. And the three should be
> hyperlinked, Feasible?
> I totally algree on the idea of DocBook for implementation. The examples
> made were prototypes and not intended for anything else.
>
> Jens K
>
Hi Olav,
I did not look at the details yet, but it seems to be very useful. Is this
already in DocBook format? If so, we can find a way to weave it into the
existing manual.
Regards,
Jason
On Fri, Jun 17, 2011 at 2:26 PM, Olav wrote:
> Hi,
> I've made a small "manual" for using ireport, that e
cilities or
>>>districts.
>>>>
>>>> Jens K
>>>>
>>>>
>>>> On 17.06.2011 16:30, Lars Helge Øverland wrote:
>>>>> Hi Olav, looks very good, nice work. We have a workshop coming
>>>up
FYI.
The patch for export from JabRef (a tool to manage BibTex format
bibliographies) to DocBook bibliography format has been accepted by
the JabRef developers team. In the next version, it will be much
easier to export the DHIS2 bibliography to DocBook format. I will make
the changes to the docu
I came across an excellent intro to writing documentation in DocBook
here http://infohost.nmt.edu/tcc/help/pubs/docbook/docbook43.pdf
Much better than the stuff we have in our guide, so it is definitely
worth a read and to use as a reference.
Regards,
Jason
_
Based on some user feedback, I have made a few changes to the docs,
and would like to raise a few points.
Just wanted to highlight to all documenters that the preferred way of
referring to an internal link is with the attribute.
This attribute is described in detail here [1]This is useful for
in
Hi there. Me again.
Please note that I have fixed the issue with using admonition images.
They now appear correctly in PDF and HTML formats.
If you want to include something like a "tip", "warning", "caution",
you can do this.
They are described in more detail here
http://newbiedoc.sourceforge.
, Bob Jolliffe wrote:
> Nice reference. Though I guess most of you can (and will) ignore
> mention of 'make' and 'nxml-mode'. Otherwise the content looks very
> comprehensive and readable.
>
> On 12 September 2011 12:09, Jason Pickering
> wrote:
>>
Hi there. Just to let you know, the latest release of JabRef, an open
source reference manager, export DocBook 4.4 by default now. If you review
the documentation documentation, it will explain how to use JabRef, manage
the common references which have been included in the documentation source,
and
saved the PDF version of the
> manual as a word document (.rtf). it is after Knut mentioned committing to
> the global repository that i considered using the track changes.
>
> One other thing I am realizing is that some screenshots might have to
> change.
>
> Sam.
>
>
>
&
Hi Inés,
Are you sure you are not behind a firewall? I have seen funny things happen
when port 22 is blocked as well.
Also, be sure that if you are using Windows, that you have "Paegent"
running, and to add your SSH key.
Regards,
Jason
On Thu, Jul 19, 2012 at 6:47 AM, Bob Jolliffe wrote:
> S
Hi Inés,
First, a big congrats to you and your team. I think this is a great
step forward for both DHIS2 and the documentation effort.
I took a quick look at the output, and I think it looks great. We had
some issues with the fonts with Vietnamese, but I guess Spanish is a
bit easier to render wit
Hi Inés (Looks like you figured this out. I was just about to send this mail)
I dug a little bit on this, and figured out that this line in the POM
is causing the problem.
The file is renamed, but the links in the file are not changed.
So, I think the best thing to do would be to remove this l
Hi Lars,
In theory it should be possible, but the maven dependency (
http://mvnrepository.com/artifact/org.docbook/docbook-xml/5.0) was not
available from the repository the last time I checked. If you could get it
to work, I would see no reason not to upgrade. It would be good to have an
alternati
ing to hear what Vex
> is like.
>
> Oxygen is still the best, and fine if you have access through university
> or what have you, but otherwise very expensive so not well suited for our
> community.
>
> Bob
>
>
> On 21 October 2013 11:56, Jason Pickering wrote:
>
>>
Hi Hannan,
I can rebuild them for you, but it will only be an approximation of the
2.12 functionality. We do not have a really formal release of the docs,
rather they are sort of improved on a continual basis. We should probably
improve on this a bit.
Is PDF what you need?
Regards,
Jason
On
Hi there. Based on some good feedback last week during the Oslo DHIS2
Academy, I have made a first cut of a developer manual. As I see it, this
basically involves slicing out all of the stuff really aimed more at
developers (and in some cases implementers) and less so, users. The chapter
on the Web
Thanks for the feedback.
@Bob, I think the developers manual (as noted by others) should cover both
development of DHIS2 (Java) as well as all the stuff currently covered in
the API and Apps chapter. The "technical architecture" chapter provides
some clues, but no real detail in terms of how peopl
Hi Everyone,
The documentation for DHIS2 has been moved to GitHub from Launchpad. The
major reason for this was to allow for more modularity of the
documentation, as well as to take advantages of the features of git as a
version control system. Everything is available here
https://github.com/dhis
versioning system in my
> opinion!
>
> 2014-09-11 11:20 GMT+01:00 Jason Pickering :
>
>> Hi Everyone,
>>
>> The documentation for DHIS2 has been moved to GitHub from Launchpad. The
>> major reason for this was to allow for more modularity of the
>> documentation,
Came across this and thought I would share it. It has quite a few good
pointers and words of wisdom for working with DocBook. The first one being,
if you are using verbatim text, do not exceed 70 characters. So a lot of
the stuff in the developers manual with or needs
to be broken up manually. Wh
wrote:
> The problem is to break up lines that people will (and should be able to)
> copy and paste directly from the manual into their terminal (for
> convenience, but also in order to not make mistakes). Typically cURL
> commands etc
>
> On Tue, Sep 30, 2014 at 11:45 A
Ah..i misread the commit. I was thinking this was another problem. I had a
build on the Jenkins CI server, but it was not building the dhis2tools due
to some missing components. I will fix this next week when I am in Oslo. I
thought this was the build which was broken, but I see now from the commit
make it a bit easier for people to get the docs running
on their system and contribute.
Regards,
Jason
On Fri, Oct 17, 2014 at 8:24 AM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> Ah..i misread the commit. I was thinking this was another problem. I had a
> build on the J
Branch: refs/heads/master
Home: https://github.com/dhis2/dhis2-docs
Commit: 39a12a3cc24da0574ed0a7480092e06fe047ddc9
https://github.com/dhis2/dhis2-docs/commit/39a12a3cc24da0574ed0a7480092e06fe047ddc9
Author: Pascal Brandt
Date: 2015-06-22 (Mon, 22 Jun 2015)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/dhis2/dhis2-docs
Commit: d13caa17093cfc06a1e904eab12d7793e7931027
https://github.com/dhis2/dhis2-docs/commit/d13caa17093cfc06a1e904eab12d7793e7931027
Author: Jason Pickering
Date: 2015-10-19 (Mon, 19 Oct 2015)
Changed
Branch: refs/heads/gh-pages
Home: https://github.com/dhis2/dhis2-docs
Commit: 46ae45656224aca8326eb4abf23c528aa7fc33d4
https://github.com/dhis2/dhis2-docs/commit/46ae45656224aca8326eb4abf23c528aa7fc33d4
Author: Jason Pickering
Date: 2015-10-19 (Mon, 19 Oct 2015)
Changed
Branch: refs/heads/master
Home: https://github.com/dhis2/dhis2-docs
Commit: 123cfad83630ccc7c5f29d0c7c0be3f6789c3a6d
https://github.com/dhis2/dhis2-docs/commit/123cfad83630ccc7c5f29d0c7c0be3f6789c3a6d
Author: Jason Pickering
Date: 2015-10-30 (Fri, 30 Oct 2015)
Changed
Branch: refs/heads/2.21
Home: https://github.com/dhis2/dhis2-docs
Commit: c73e7690de1536226d21c47642a36d9061a8af67
https://github.com/dhis2/dhis2-docs/commit/c73e7690de1536226d21c47642a36d9061a8af67
Author: Jason Pickering
Date: 2015-10-30 (Fri, 30 Oct 2015)
Changed paths
Branch: refs/heads/master
Home: https://github.com/dhis2/dhis2-docs
Commit: d1e50ef1df5c18e4e440691b22988bde6e2ef138
https://github.com/dhis2/dhis2-docs/commit/d1e50ef1df5c18e4e440691b22988bde6e2ef138
Author: Jason Pickering
Date: 2015-10-30 (Fri, 30 Oct 2015)
Changed
Hi Lars,
I think there must be a way around this, and I would not be in favor at all
of ditching Serna. Its a good tool and not everyone has access to a
relatively expensive commercial tool like Oxygen.
Serna Free inserts this automatically unfortunately when it saves the
document, but lets look f
For instance, perhaps this
http://www.oxygenxml.com/forum/topic3658.html
which seems to describe a means of getting around comments.
On Wed, Apr 6, 2016 at 7:01 PM, Jason Pickering wrote:
> Hi Lars,
> I think there must be a way around this, and I would not be in favor at
> all of
/nroff/groff and certainly lack the maturity of docbook. But
> >>> maybe the world has moved to a stage that its possible to consider
> >>> editing html5/css3 documents directly? Certainly there is
> >>> considerable user friendly editing tools available. And c
t; alternatives (markdown and
>> >>> friends) none of which I am fond of, but they have enthusiastic
>> >>> supporters. To me they all seem like endless reinventions of
>> >>> roff/nroff/groff and certainly lack the maturity of docbook. But
>> &g
han products. And most of all, the content.
>
> On 7 April 2016 at 14:40, Jason Pickering
> wrote:
> > Perhaps, but see my earlier mail regarding framework wars.
> >
> > This is the same discussion we are having about testing, use this
> framework
> > or
Branch: refs/heads/master
Home: https://github.com/dhis2/dhis2-docs
Commit: b5d766e657efcc62a29b3b42780e9a55630fb70d
https://github.com/dhis2/dhis2-docs/commit/b5d766e657efcc62a29b3b42780e9a55630fb70d
Author: Jason Pickering
Date: 2016-04-09 (Sat, 09 Apr 2016)
Changed
m regretting getting
> involved in this thread at all, but I am glad you got rid of the Serna
> free comments :-) Back to work.
>
>
>
>
>
> On 8 April 2016 at 04:13, Jason Pickering
> wrote:
> > Hi Bob,
> >
> > Again, I think the fact that docbook has mo
cense model with a
>> minimum commitment period of 12 months.
>>
>> On Sat, Apr 9, 2016 at 10:08 AM, Jason Pickering <
>> jason.p.picker...@gmail.com> wrote:
>>
>>> I found what looks like a too-good-to-be-true WebApp version of Oxygen
>>> f
nior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Mon, Apr 11, 2016 at 4:42 PM, Jason Pickering <
> jason.p.picker...@gmail.com> wrote:
>
>> Hi Knut,
>>
>> If it would get you writing some docs, it would be well worth it. :)
>>
&g
mit/f27cdfb39920ae31caacbd4222024adad392a872
Author: Jason Pickering
Date: 2016-04-23 (Sat, 23 Apr 2016)
Changed paths:
M pom.xml
M src/docbkx/en/ccei_user_man_introduction.xml
M src/docbkx/en/ccei_user_manual_en.xml
M src/docbkx/en/dhis2_android_user_man.xml
M src/docbkx
Hi there.
We have completed the initial upgrade of the documents from DocBook version
4.5 to DocBook version 5. Please take note of this when producing new
documents.
If you have issues, please report them here
https://github.com/dhis2/dhis2-docs/issues
Regards,
Jason
--
Jason P. Pickering
e
-
Merge with master
Commit: f948fd151f32a28d490d798f7a8c0c265d0c139c
https://github.com/dhis2/dhis2-docs/commit/f948fd151f32a28d490d798f7a8c0c265d0c139c
Author: Jason Pickering
Date: 2016-04-25 (Mon, 25 Apr 2016)
Changed paths:
M src/docbkx/en/dhis2_user_man_using_data_visualizer.xml
M src/docb
ents. This should ensure you have
the correct revision of the submodule.
Regards,
Jason
On Sun, Apr 24, 2016 at 9:21 AM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> Hi there.
>
> We have completed the initial upgrade of the documents from DocBook
> version 4.5 to Do
17:26 Bob Jolliffe wrote:
> A small glimpse at the (open) future of publishing:
>
>
> http://www.balisage.net/Proceedings/vol10/print/Kleinfeld01/BalisageVol10-Kleinfeld01.html
>
> On 11 April 2016 at 12:11, Jason Pickering
> wrote:
> > Perhaps this is possible, but not
erate webhelp off the
> docbook already which is cool. Another fun thing to add to your hairy
> maven build :-)
>
> On 26 April 2016 at 17:35, Jason Pickering
> wrote:
>
>> Well, having spent the last week almost converting the docs to docbook 5,
>> I suggest we wait t
e:
---
Event Visualizer: minor edits; Usage Analytics: minor edits.
Commit: f7f9badda2737de402b1cfd59d71b95401600ca9
https://github.com/dhis2/dhis2-docs/commit/f7f9badda2737de402b1cfd59d71b95401600ca9
Author: Jason Pickering
Date: 2016-04-29 (Fri, 29 Apr 2016)
Chang
Hi Eileen,
There has been some effort in the past to translate the documentation into
French. The source of the documents are available here
https://github.com/dhis2/dhis2-docs/tree/master/src/docbkx/fr
but we are not providing these as built documents on the web page due
currently, as they are q
I like the "simplicity" of ASCIDOC as well. DocBook is a bit heavy, but for
good reason. With great structure, comes many possibilities, so even if it
is a bit heavy, it works for us right now. I certainly don't think we
should change the main docs at the moment.
I think it would be good alternati
Hi everyone.
We continue to experience some issues with the docs branch. Partly, this is
because of the content (XML) which can be a bit tricky to merge some times.
However, I would like to ask going forward, that all changes to the docs be
made through pull requests instead of direct commits to m
)
Changed paths:
M .travis.yml
Log Message:
---
Update to travis file.
Commit: 4484fbf4fb4b255c062dd0b61fe42db2a05ec9ae
https://github.com/dhis2/dhis2-docs/commit/4484fbf4fb4b255c062dd0b61fe42db2a05ec9ae
Author: Jason Pickering
Date: 2016-06-20 (Mon, 20 Jun 2016
Branch: refs/heads/master
Home: https://github.com/dhis2/dhis2-docs
Commit: b1b201817bf08538615a55a1c657bdb299e0f7db
https://github.com/dhis2/dhis2-docs/commit/b1b201817bf08538615a55a1c657bdb299e0f7db
Author: Jason Pickering
Date: 2016-06-20 (Mon, 20 Jun 2016)
Changed
1 - 100 of 231 matches
Mail list logo
