[liblouis-liblouisxml] Re: liblouis web site

  • From: Michael Whapples <mwhapples@xxxxxxx>
  • To: liblouis-liblouisxml@xxxxxxxxxxxxx
  • Date: Thu, 06 Mar 2014 22:29:36 +0000

Sorry if I did not make it clear.

What I meant is that one can write/edit the wiki pages locally in text files, using a text based mark up language (eg. markdown, I think that is the notation used by the Google Code wiki), then when you commit it and view the page in the Browser, the wiki software converts it to HTML.

I am not sure, but i would imagine that the Google Code wiki allows images.

It certainly does support document structure and linking.

Michael Whapples
On 06/03/2014 16:16, Keith Creasy wrote:
Hi.

I just want to chime in here to say that we, at least for the BrailleBlaster 
project, definitely want a form of documentation that supports images and 
visual styles. Probably XHTML. As a blind user of course I'm fine with plain 
text but many of the people using these tools are going to be sighted and some 
visual learning aids, like screen shots, other images, and perhaps Unicode 
Braille are very helpful.

I'm not sure about the Google code page wiki. Are you saying they don't support 
styles and images?



-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx 
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples
Sent: Thursday, March 06, 2014 10:43 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: liblouis web site

It is worth also noting that the standard GoogleCode wiki in the project pages 
also stores the content as plain text files and so one can edit and commit 
through the repositories to update the wiki.

Michael Wahpples
On 06/03/2014 15:34, Mesar Hameed wrote:
Hi Christian,

Will the website that you create enable us to do accessable bug
tracking?

Remember we still have a test ikiwiki instance, What were your reasons
for not wishing to go with it?
This is realy my prefered choice, since everything is in text files,
and is dynamically rendered on the server.
This means that anyone that has commit access could help with
updating/improving any documentation that we might place on the website/ship 
with liblouis.

thanks,
Mesar



On Mon 03/03/14,17:24, Christian Egli wrote:
Hi all

You might have noticed that the release announcement no longer points
to the google code site for downloads. Instead it directs the user to
a site under http://liblouis.github.io/. As we can no longer host
downloads on google code we decided to move them to liblouis.org.

So, why didn't I upload them to liblouis.org? The answer is simply
that I haven't had time. I created a new site for liblouis and used
the github hosting facilities to serve it[1]. This site is only for
liblouis the translator. I'm working on creating a unified site for
liblouis* that includes news, downloads, links, etc for liblouis and
utdml and links to BrailleBlaster. However this site is not finished
and I wanted to get the release out now (as promised). I hope to have
the unified site within a week or two. Once that's done I'll move the
content to liblouis.org.

Thanks
Christian

Footnotes:
[1]  https://github.com/liblouis/liblouis.github.io
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

-----
SBS Leser, die neue Hoerbuch-App fuer iPhone und iPad. Mehr Infos
unter http://online.sbs.ch For a description of the software, to
download it and links to project pages go to
http://www.abilitiessoft.com
For a description of the software, to download it and links to project pages go 
to http://www.abilitiessoft.com
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com

For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com

Other related posts: