Went to look for something on the wiki today, nd found a lot of work to do instead

[B. Henry]

A few years ago Rob asked for an article on text file differences between operating systems.
I wrote it, put it in the dropbox folder, and thought it had gotten pushed up to the wiki. Well it didn't unles someone tokk it down later which I doubt
happend.
I Changed a couple lines and put it up several hours ago, but looking around at parts of the wiki I've never read or only glanced at years ago found
quite a few changes that needed to be made, ie. one would have thought Vinux4 was our latest release more often than not from content I saw.
I did a bit of organizational work as well/hope people find the changes positive. I moved some comments and tips from the getting started page to the
FAQ after updating a bit. I added a couple more entriesas well, fixed a dead link somewhere else, etc.
I'll do a bit more work next time I have a couple of hours, but have a couple of request for content I'm not the best person to write.
There's a small list of core Vinux software articles. I'll do some work on the nano article as I use that editor daily and know a few things about it.
There's no Libreoffice article at all as far as I know. Could someone who uses LO apps regularly write a couple of articles, or a couple of folks write
an article a piece, a few LO geeks form a team or something?
I mean the help and documentation are generally excellent, so little is needed actually, but a few paragraphs from an accessibility point of view would
be an important eddition to the default software section.
I may have started something on gpodder, but if not someone should/it can be a bit confusing at first.I'll look for my notes and report back on that
one, but even if I have something would not at all mind working with someone else to get an article written and posted soon.
Voxin users: is the installing voxin on vinux4 article completely accurate for vinux5? If so, I'll change the name to indicate that instuctions apply to
vinux4 and 5, if not, please, someone who use voxiin do the required updates.
I've never installed Voxin on a V5 box, and usually don't bother to install it for myself, so that's not my department.
We need a skype article I think. We have an skcmd article and a pidgin skype article, and I put some of the basics in to an FAQ question and answer,
but I'd like to see more than fits the FAQ format, i.e. a bit on navigating the interface. It'd be a short article I think, but enough to let people
know what to expect as it's rather different from the last windows skkype interface I looked at, honestly better in some ways I think.
Which other default Vinux software needs a bit of coverage?
I'm going to go in and add a one line description of each program in the list.
Now they are just links.
Evince needs a short article I think.
Caja, not sure what else. The image viewers at lest should be named or something, features don't seem to vary between the mate and gnome offerings do
they?
I not particularly convinced we should be shipping clamtk over other packages that we don't include, but it's there, and is a well known application,
and not always that nice to use with orca as I recall/not used it in a while. Could use an article.
I have a pretty good idea of what kinds of questions are asked not only pon the Vinux list, but the orca one as well, so can add a few more, but what do
others think is not in the FAQ that should be?
I don't think I ever finished my speakup article, although there's enough there to post. I'm pretty sure it's not up, and I sure did not see it
today/read every entry on the site map a couple of times to try and get a fair idea of the overall state of things.
Two more I'll probably do are one on installing dropbox, and working with the text-entry interface in system-settings. They willl be short and
sweet, hve the basic info organized, just a matter of cleanng up wording and running a spell check.
The rescue disk and flash drive articles are years out of date at best, not going to take that one on myself this season, hint, hint...
I have a coule other questions regarding the wiki that I want to think over a bit myself before I ask them, but this is some of what I see that needs
doing. I'd encourage anyone who's written an article to update it if that is needed.
Thanks for reading this laundry list.
There's still the quickstart guide that needs writing as well if anyone feels like taking on a biger project.





--
B.H.
Registerd Linux User 521886

[Joe Nosay]

Have you thought about importing the frequently asked questions and help articles from another source?

--
You received this message because you are subscribed to the Google Groups "vinux documentation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vinux-documenta...@googlegroups.com.
To post to this group, send email to vinux-doc...@googlegroups.com.
Visit this group at https://groups.google.com/group/vinux-documentation.
For more options, visit https://groups.google.com/d/optout.

[B. Henry]

What other source?
This should be mostly Vinux specific, so no other source would exist, well does exist, unless it's hiding somewhere in the dark web I am not aware
of...lol
If you can think of some good FAQ regarding general Linux accessiblity and or Ubuntu, that is certainly a posibility.
We should probably link to one or two FAQs, especially a general Ubuntu one, and we could probably adapt one or more questions from existing FAQs for
our own FAQ, so if you can give specific examples you think would be good and useful whether as is or with some modification, please share.
We don't want this thing to be too large, nor to reinvent the wheel, so some limited importation or building on existing content might be a good idea.
I want to add an entry about installing non-free codecs etc, and that would be the same for us as it would for any Ubuntu 14.04 system, and we could
even include a legacy command for vinux4/ubuntu 12.04 systems.
It'd be pretty easy to write, but if you can give me one that's good as is, well please share.

--
B.H.
Registerd Linux User 521886

Joe Nosay wrote:
Wed, Apr 06, 2016 at 04:30:37PM -0400

> Have you thought about importing the frequently asked questions and help
> articles from another source?

> an email to [2]vinux-documenta...@googlegroups.com.

> To post to this group, send email to

> [3]vinux-doc...@googlegroups.com.
> Visit this group at
> [4]https://groups.google.com/group/vinux-documentation.
> For more options, visit [5]https://groups.google.com/d/optout.

>
> --
> You received this message because you are subscribed to the Google Groups
> "vinux documentation" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to [6]vinux-documenta...@googlegroups.com.

> To post to this group, send email to

> [7]vinux-doc...@googlegroups.com.
> Visit this group at
> [8]https://groups.google.com/group/vinux-documentation.
> For more options, visit [9]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. mailto:burt1...@gmail.com
> 2. mailto:vinux-documentation%2Bunsu...@googlegroups.com
> 3. mailto:vinux-doc...@googlegroups.com
> 4. https://groups.google.com/group/vinux-documentation
> 5. https://groups.google.com/d/optout
> 6. mailto:vinux-documenta...@googlegroups.com
> 7. mailto:vinux-doc...@googlegroups.com
> 8. https://groups.google.com/group/vinux-documentation
> 9. https://groups.google.com/d/optout

[Bill Taylor]

-Good call, Burt!

One thing That I would like to see added is a section on Braille. We
call ourselves 'Linux for the blind' , but Braille seems to have
problems, for which answers are not available on the support list.

I wonder could we get Braille users to put together some articles, as
we don't seem to have any regular users on the Development Team.

I was very impressed when a manager of Vision Australia chaired a
meeting locally, and presented a speech, head up, apparently watching
people's reactions. Her hands were flying across a wide book, reading!
She is of course, totally blind.

Bill

[Luke Yelavich]

On 7 Apr 2016, at 8:18 AM, Bill Taylor <bill...@gmail.com> wrote:
>
> I was very impressed when a manager of Vision Australia chaired a meeting locally, and presented a speech, head up, apparently watching people's reactions. Her hands were flying across a wide book, reading! She is of course, totally blind.

Yeah, I’ve done that before, but with actual braille on paper, rather than a refreshable display.

I am a Braille reader, and have a display, but since I haven’t kept it up, I am not the fastest, so tend to favour speech. I could probably contribute something, but I find Braille is rather clunky in Linux, unless you live on the console, and these days I am not a console only fan, particularly since you often need a web browser to get things done.

By clunky, I mean the experience of getting a display going and working with it is not as polished as it could be.

Luke

[B. Henry]

Bill,unfortunately I've never had the chance to use, much less own an electronic braille device, but for some, those with hearing impairment, and math
students braille is a neceity.
It's a major enjancement to the computing experience for others, and I can not agree with you more that we should try to support Braille as much as we
can, both displays and printers/embossers, not sure if there's an actual difference in how those terms are used sometimes or not.
Hopefully someone or better yet a group of users can step up and help us with this, and if need be we can hack around any existing issues if not come up
with quality long term fixes for problems.
Documentation is not sexy perhaps, but support is certainly an important part of the Vinux experience, and should not be neglected as it has been for a
while. I take as much responsibility as anyone, but will be straight up with the community in saying that there are other things that interest me more
at this time, and I'm not going to try and do it all, well all that I'm qualified to do better said, e.g. I could not do anything with braille if I
wanted to.
Again, just a few hours here and there can make a big difference folks, so please, consider helping out. One article per person could bring us up to
speed if we had a couple of dozen volenteers, and don't forget, this is not publishing a book, i.e. you don't have to do everything perfectly all at
once. Wikis are all about taking something good enough and making it better, taking something good and making it great, and taking something very basic
and expanding uppon it.
I'm not trying to lay a guilt trip on anyone, just asking for help.

--
B.H.
Registerd Linux User 521886

Bill Taylor wrote:
Thu, Apr 07, 2016 at 08:18:00AM +1000

> --
> You received this message because you are subscribed to the Google Groups "vinux documentation" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to vinux-documenta...@googlegroups.com.
> To post to this group, send email to vinux-doc...@googlegroups.com.
> Visit this group at https://groups.google.com/group/vinux-documentation.
> For more options, visit https://groups.google.com/d/optout.

[B. Henry]

Luke and all,

> I am a Braille reader, and have a display, but since I haven’t kept it up, I am not the fastest, so tend to favour speech. I could probably contribute something, but I find Braille is rather clunky in Linux, unless you live on the console, and these days I am not a console only fan, particularly since you often need a web browser to get things done.
>
> By clunky, I mean the experience of getting a display going and working with it is not as polished as it could be.

Where does work most need to be done?
Are drivers not there or in a poor state, or is something else not going on?
Thanks in advance for any feedback, technical, or from an end user's point of view.

--
B.H.
Registerd Linux User 521886

Luke Yelavich wrote:
Thu, Apr 07, 2016 at 09:48:20AM +1000

> On 7 Apr 2016, at 8:18 AM, Bill Taylor <bill...@gmail.com> wrote:
> >
> > I was very impressed when a manager of Vision Australia chaired a meeting locally, and presented a speech, head up, apparently watching people's reactions. Her hands were flying across a wide book, reading! She is of course, totally blind.
>
> Yeah, I’ve done that before, but with actual braille on paper, rather than a refreshable display.
>
>

> Luke

[Luke Yelavich]

On 7 Apr 2016, at 10:08 AM, B. Henry <burt1...@gmail.com> wrote:
>
> Where does work most need to be done?
> Are drivers not there or in a poor state, or is something else not going on?
> Thanks in advance for any feedback, technical, or from an end user's point of view.

Driver wise, I think things are good. As far as I know, modern/new braille displays are supported for the most part just fine.

The integration of BrlTTY and Orca could probably be better, not sure how exactly, and the process of setting up and using a display, especially if you want to use more advanced functions could be better. Right now, you have to edit the BrlTTY configuration file to do anything beyond basic setup and use, especially if you want to use your display via bluetooth. (Yes, this is not possible to do purely via the GUI.)

Luke