[quoted lines by Rich Morin on 2016/07/07 at 09:17 -0700]
>It appears that using a tag at the end of an causes a blank line to
>be added.
I suspect you're right, although, being blind, I can't experiment with it while
looking at a screen. My guess is that a newline is explicitly ensured at th
> There still needs to be a paragraph break before ".arch.rpm".
The leading disparity shows up (on my Mac) in both Google Chrome and
Safari. I have a theory about this, but no specific solution to offer.
It appears that using a tag at the end of an causes a blank
line to be added. So, for exa
Dave Mielke (2016/07/07 01:21 -0400):
> Okay. This turns out to be a difference between my ancient web server at home
> and the modern web serer on brltty.com. The Download page is now clean. Now I
> guess I should clean up the other pages. :-(
If you want some help you can let us know.
Shérab.
Samuel Thibault (2016/07/07 08:44 +0200):
> Shérab, on Thu 07 Jul 2016 07:02:49 +0200, wrote:
> > Dave Mielke (2016/07/06 23:54 -0400):
> > > First: It's saying that the encoding in the XML header (utf-8) isn't
> > > matching
> > > the encoding in the HTTP header (iso-8859-1). This is correct alt
Shérab, on Thu 07 Jul 2016 07:02:49 +0200, wrote:
> Dave Mielke (2016/07/06 23:54 -0400):
> > First: It's saying that the encoding in the XML header (utf-8) isn't
> > matching
> > the encoding in the HTTP header (iso-8859-1). This is correct although I'm
> > not
> > sure why because the HTML HE
[quoted lines by Rich Morin on 2016/07/06 at 20:30 -0700]
>I still think the Old Releases section should have its own page.
This is now done.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
EMa
[quoted lines by Shérab on 2016/07/07 at 07:02 +0200]
>I believe this meta thing could be removed because it is redundant with
>the HTTP headers sent by nginx as can be seen with
>
>cd /tmp; curl -D headers http://www.brltty.com/download.html > /dev/null
The element sets the HTTP header.
>I don
Hi,
Dave Mielke (2016/07/06 23:54 -0400):
> First: It's saying that the encoding in the XML header (utf-8) isn't matching
> the encoding in the HTTP header (iso-8859-1). This is correct although I'm
> not
> sure why because the HTML HEAD section does have:
>
>
I believe this meta thing co
[quoted lines by Dave Mielke on 2016/07/06 at 23:54 -0400]
>First: It's saying that the encoding in the XML header (utf-8) isn't matching
>the encoding in the HTTP header (iso-8859-1). This is correct although I'm not
>sure why because the HTML HEAD section does have:
>
>
Still don't know wh
[quoted lines by Rich Morin on 2016/07/06 at 20:30 -0700]
>The page uses "flavour" (British), rather than "flavor" (US). Not a
>problem, unless it's unintentional.
I'm Canadian.
>I still think the Old Releases section should have its own page.
I agree. Just don't want to mess with too much at
On Jul 6, 2016, at 16:51, Dave Mielke wrote:
> [quoted lines by Rich Morin on 2016/07/06 at 05:04 -0700]
>
> Please check the Download page to see if the formatting has improved and/or
> if
> there are any new problems. There are a few validator errors to fix, still,
> but
> I'd appreciate a
On Wed, 6 Jul 2016, Rich Morin wrote:
> I had assumed that you supported tmux, possibly via the screen interface.
> Given that you don't, no entry is needed. OTOH, you might consider doing
> a tmux driver at some point.
That could be a good thing especially if the patch needed to export the
scr
[quoted lines by Rich Morin on 2016/07/06 at 05:04 -0700]
Please check the Download page to see if the formatting has improved and/or if
there are any new problems. There are a few validator errors to fix, still, but
I'd appreciate a progress report.
--
Dave Mielke | 2213 Fox Crescen
Dave Mielke (2016/07/06 16:46 -0400):
> This is actually a nice service. It'll take a while to make it happy, though,
> since it wants lowercase element and attribute names whereas ours are
> uppercase. :-(
http://vim.wikia.com/wiki/Changing_all_HTML_tags_to_lowercase#WikiaArticle
Could this he
[quoted lines by Shérab on 2016/07/06 at 20:27 +0200]
>You may want to use W3C's validator:
>
>https://validator.w3.org/#validate-by-uri
>
>It reports a few errors that do not seem related to the issues discussed
>in this thread but it may be interesting to fix the page anyway and e.g.
>specifying
On Jul 6, 2016, at 07:45, Dave Mielke wrote:
> [quoted lines by Rich Morin on 2016/07/06 at 07:21 -0700]
>
>> Screen vs tmux
>> https://www.wikivs.com/wiki/screen_vs_tmux
>
> I didn't know about tmux. I still don't understand your suggestion
> on this point, though. Why introduce a term (tmux)
Hi,
Dave Mielke (2016/07/06 10:33 -0400):
> I understand, but rendering is up to the individual browsers. For all I know,
> adding a dummy paragraph at the end of or text might cause too much
> space when some other browser is being used. To me, therefore, if the spacing
> is messed up when t
[quoted lines by Rich Morin on 2016/07/06 at 07:21 -0700]
>Screen vs tmux
>https://www.wikivs.com/wiki/screen_vs_tmux
I didn't know about tmux. I still don't understand your suggestion on this
piont, though. Why introduce a term (tmux) that isn't relevant?
--
Dave Mielke | 2213 Fox C
[quoted lines by Rich Morin on 2016/07/06 at 07:18 -0700]
>Your call, of course. FWIW, I always try to use the capitalization
>that the package's author prefers (eg, BRLTTY, BrlAPI), even if it
>seems odd or inconsistent.
Yes, I'm very much the same. For whatever reason, this particular one bugs
On Jul 6, 2016, at 07:11, Dave Mielke wrote:
> [quoted lines by Rich Morin on 2016/07/06 at 05:04 -0700]
>
>> TCL -> Tcl
>
> I know about this one, but I'm kind of stubborn about it. The C and the L,
> after all, also stand for words in their own right. To me, therefore, it's
> simpl
On Jul 6, 2016, at 06:48, Dave Mielke wrote:
>> If `tmux` uses the `screen` driver, this should be mentioned in the
>> `screen` entry and cross-references in a separate entry. If not,
>> explain how `tmux` is supported.
>
> I don't understand. For starters, what's tmux?
Screen vs tmux
https://w
[quoted lines by Rich Morin on 2016/07/06 at 05:04 -0700]
> TCL -> Tcl
I know about this one, but I'm kind of stubborn about it. The C and the L,
after all, also stand for words in their own right. To me, therefore, it's
simply incorrect to only capitalize the first letter.
> XWind
[quoted lines by Rich Morin on 2016/07/06 at 05:04 -0700]
>because no good deed goes unpunished, here are some more nits!
:-)
>If `tmux` uses the `screen` driver, this should be mentioned in the
>`screen` entry and cross-references in a separate entry. If not,
>explain how `tmux` is supported.
On Jul 5, 2016, at 15:03, Dave Mielke wrote:
> [quoted lines by Rich Morin on 2016/07/05 at 09:29 -0700]
>> I would add a descriptive section on "Distribution Formats", near the top
>> of the page (eg, just below the "Copyright and Disclaimer").
>
> Please check it out and comment.
My first co
Rich Morin, on Tue 05 Jul 2016 12:30:21 -0700, wrote:
> Given that the manual in question starts as SGML, I wouldn't be
> surprised if it can generate high-quality PDF, but Samuel will know
> for sure.
The SGML toolchain goes through LaTeX, but the structure is preserved,
so indexing etc. should
[quoted lines by Rich Morin on 2016/07/05 at 09:29 -0700]
>I would add a descriptive section on "Distribution Formats", near the top
>of the page (eg, just below the "Copyright and Disclaimer").
Please check it out and comment.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the v
On Jul 5, 2016, at 12:24, Dave Mielke wrote:
> How searchable is PDF?
That depends on how it was produced. The worst case scenario is a set
of pages that were simply scanned in as images. This isn't accessible
as text, let alone searchable. In a better scenario, the text would be
accessible, b
[quoted lines by Rich Morin on 2016/07/05 at 09:29 -0700]
>The cleaned up text version is a huge improvement, but it would be great
>to have a printable and searchable version that retained the style info
>(eg, italic, bold, link). This could be a single HTML page or a PDF document.
How searchable
Rich Morin, on Tue 05 Jul 2016 09:29:12 -0700, wrote:
> On Jul 5, 2016, at 03:43, Dave Mielke wrote:
> > Are you looking for something like a PDF version, or is the cleaned up text
> > version good enough?
>
> The cleaned up text version is a huge improvement, but it would be great
> to have a p
On Jul 5, 2016, at 03:43, Dave Mielke wrote:
> Are you looking for something like a PDF version, or is the cleaned up text
> version good enough?
The cleaned up text version is a huge improvement, but it would be great
to have a printable and searchable version that retained the style info
(eg,
[quoted lines by Rich Morin on 2016/07/04 at 11:07 -0700]
>I dislike reading manuals from a computer screen, but I couldn't find
>an easy way to print the manual. Am I missing something?
Are you looking for something like a PDF version, or is the cleaned up text
version good enough?
>The downl
Rich Morin, on Mon 04 Jul 2016 14:53:28 -0700, wrote:
> However, I still wonder what
> BrlAPI changes may need to added to the 2006 document.
Most probably none :)
Samuel
___
This message was sent via the BRLTTY mailing list.
To post a message, send an
On Jul 4, 2016, at 14:10, Dave Mielke wrote:
> [quoted lines by Rich Morin on 2016/07/04 at 11:07 -0700]
>> BrlAPI 1.0
>> http://mielke.cc/brltty/doc/BrlAPIref/index.html
>>
>> The page in question appears to be rather dated,
>
> In what way does it look dated?
When I went to research this, I
[quoted lines by Rich Morin on 2016/07/04 at 11:07 -0700]
># The BrlAPI Programmers' Reference
>
>The "Documentation" page (http://mielke.cc/brltty/documentation.html)
>contains a link (The BrlAPI Programmers' Reference) to:
>
> BrlAPI 1.0
> http://mielke.cc/brltty/doc/BrlAPIref/index.html
>
>T
Hello,
Rich Morin, on Mon 04 Jul 2016 11:07:12 -0700, wrote:
> The "Documentation" page (http://mielke.cc/brltty/documentation.html)
> contains a link (The BrlAPI Programmers' Reference) to:
>
> BrlAPI 1.0
> http://mielke.cc/brltty/doc/BrlAPIref/index.html
>
> The page in question appears t
While perusing the BRLTTY and BrlAPI web pages, I ran into several
issues (see below). No guarantees, but let me know if some editing
assistance would be welcomed.
-r
# The BrlAPI Programmers' Reference
The "Documentation" page (http://mielke.cc/brltty/documentation.html)
contains a link (The
36 matches
Mail list logo
