#quill — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #quill, aggregated by home.social.
-
The Monarch as My Silent Co-Presenter: Braille Notes That Kept a Live Accessibility Demo on Track: https://blindaccessjournal.com/2026/07/the-monarch-as-my-silent-co-presenter-braille-notes-that-kept-a-live-accessibility-demo-on-track/ #accessibility #Braille #Monarch #APH #QUILL #BITS
-
The Monarch as My Silent Co-Presenter: Braille Notes That Kept a Live Accessibility Demo on Track: https://blindaccessjournal.com/2026/07/the-monarch-as-my-silent-co-presenter-braille-notes-that-kept-a-live-accessibility-demo-on-track/ #accessibility #Braille #Monarch #APH #QUILL #BITS
-
Hey @quillforall I'm attempting, so far unsuccessfully, to connect my #WordPress installation to #Quill, so I can publish an article or 2, before the #In-Person portion of the #ACB26 convention kicks off because then I'll be super busy & probably won't have time to post once all the fun & craziness begins. What am I supposed to enter for the site address? It won't take my username & password either.
-
Hey @quillforall I'm attempting, so far unsuccessfully, to connect my #WordPress installation to #Quill, so I can publish an article or 2, before the #In-Person portion of the #ACB26 convention kicks off because then I'll be super busy & probably won't have time to post once all the fun & craziness begins. What am I supposed to enter for the site address? It won't take my username & password either.
-
@quillforall despite my success in getting #AI going in #QUILL, I asked It how a letter I had written sounded & the response I got back made 0 sense to me as a #screen-reader user.
It was filled with strange symbols. -
@quillforall despite my success in getting #AI going in #QUILL, I asked It how a letter I had written sounded & the response I got back made 0 sense to me as a #screen-reader user.
It was filled with strange symbols. -
Someone on the #Technology list asked if #Quill &/or #QuillRadio are available for#iOS, to which I responded, “no, but I 100% agree that they should be. “
To me, having applications available on the platforms, our members actively use, including #Mobile platforms, such as #Android & #iOS, is part of our core mission to, “meet people where they are.” -
Someone on the #Technology list asked if #Quill &/or #QuillRadio are available for#iOS, to which I responded, “no, but I 100% agree that they should be. “
To me, having applications available on the platforms, our members actively use, including #Mobile platforms, such as #Android & #iOS, is part of our core mission to, “meet people where they are.” -
@quillforall, In addition to helping you create #AudioBooks, can Quill help create books which are strictly text? I ask as I am currently in the process of working on one and would like to finish it this year, if it all possible. Also, I just reset my PC & before I installed anything, even #JAWS, I installed #Quill!
-
@quillforall, In addition to helping you create #AudioBooks, can Quill help create books which are strictly text? I ask as I am currently in the process of working on one and would like to finish it this year, if it all possible. Also, I just reset my PC & before I installed anything, even #JAWS, I installed #Quill!
-
All the people I've come across on here shitting on #quill because it lets people choose the features they want are clearly dumb enough to fail to realise that there are people that wanna do things in one app, not bounce between 20 different things, for instance, writing a readme, then needing to go to either GH Desktop or the terminal to then commit and push the changes, there are people that want to be able to do that right where they are, they just finished writing the file in the text editor, they then hit a few keys and bring up the GitHub commit dialog or whatever. If someone doesn't need the GitHub features, boom, they can get rid of them in a couple of key presses. Get a grip people!
-
A recap of my last 24 hours. Dead-tired after a sleepless night, but I talked to a customer anyways.
Then, having discussed of Obsidian in another situation, I discovered I misunderstood the term "vault" on @quillforall translation, because the term has two meanings in two different contexts. Credential vault is one thing, the vault used on QUILL is kind of organization where files reside and connect with each other.
I sent another pull request with the fix, and it returned 12/13 tests passed. Compiling and checking were all smooth, who knows what happens!
Then, I struggled with WordPress Full Site Editing and MultiSite network but I'll talk about it in another day. I think it's time to say that the world could turn upside-down now, and I won't hear it at all! -
A recap of my last 24 hours. Dead-tired after a sleepless night, but I talked to a customer anyways.
Then, having discussed of Obsidian in another situation, I discovered I misunderstood the term "vault" on @quillforall translation, because the term has two meanings in two different contexts. Credential vault is one thing, the vault used on QUILL is kind of organization where files reside and connect with each other.
I sent another pull request with the fix, and it returned 12/13 tests passed. Compiling and checking were all smooth, who knows what happens!
Then, I struggled with WordPress Full Site Editing and MultiSite network but I'll talk about it in another day. I think it's time to say that the world could turn upside-down now, and I won't hear it at all! -
my subscriber app doesn't accept Quill's podcasts.
https://community-access.github.io/quill/podcast/feed.xml
Reason: This XML file does not appear to have any style information associated with it. The document tree is shown below.
-
my subscriber app doesn't accept Quill's podcasts.
https://community-access.github.io/quill/podcast/feed.xml
Reason: This XML file does not appear to have any style information associated with it. The document tree is shown below.
-
@quillforall @NightDrake
@quillforall Hello- I am havign trouble exporting documents on mac OS. I installed pandoc via its website but according to #quill I don't have pandoc. What do I do? sorry to but in on conversation but I couldn't figure out spelling of mastodon username. -
@quillforall @NightDrake
@quillforall Hello- I am havign trouble exporting documents on mac OS. I installed pandoc via its website but according to #quill I don't have pandoc. What do I do? sorry to but in on conversation but I couldn't figure out spelling of mastodon username. -
I write this post publicly, not just for @quillforall folks, whom I promised the test with Braille to. I will share it here, because this experiment can be useful to other blind Braille users as well.
Guess what?
PoEdit, the translation editor for Windows, version 3.9.1, has the same bug found on QUILL 0.8.0 Beta 1. Braille display with JAWS screen reader doesn't detect selection highlighting with 7 and 8 dots under each single character and space.NVDA behaves correctly instead, both on QUILL and PoEdit, characters are properly selected. Unfortunately I have no idea whether Narrator can work with Focus Braille display, otherwise I'd have no issues in testing this as well.
This makes me suppose it's a @freedomscientific JAWS bug. I have mentioned them here as well, to make them aware. I have no idea of how to report a bug directly to them.
I think that not many blind professionals have reported the bug, as maybe most of them use commercial software more often, such as the Microsoft Office suite or, like me, simply surrendered to it.
As far as I can rememmber, the bug has always been there.
Today it's the first time I have properly identified it, and hopefully I can report it, as in 2006 I already tried to report an issue and it was fixed about 7 years later, it was even worse than this one because it prevented from using Sticky Keys for one-handed people. And my ex, who's blind and his left hand is injured, was definitely stuck. A vendor literally said in front of both of us "this bug has low priority as few people use sticky keys". Literally saying to a mobility impaired user, "you paid me but I don't cover your needs because you don't count". That was solved in JAWS 15.0, and the bug was there since 4.5.
NotePad++ editor behaves even more strangely for text selection, I always thought it was random but I managed to test it in deep today:
let's assume you have a blank file, so it starts with the line "1"; from margins and borders, in notepad++ settings, line number view must be checked on.
JAWS behavior: Notepad++ blank file, you type a sample sentence, let's say "QUILL for all".
You place the cursor on the q, then you select the whole line. You'll notice that the two l's of "quill for all" will not have the Braille cursor highlights.
What JAWS does: it highlights all the characters, including the line number. It behaves the opposite of how it should. It should highlight the text but not the line number. And the non-highlighted characters increase according to how long the line number is, space included. So, if "QUILL for all" is written on the 2800th line, the line number will be 2800, then space, then Q. Result? Braille display will highlight the line number with related space, then QUILL FO. Other letters are visually selected, but left behind.
If I deactivate the line numbers view, JAWS selects everything correctly. But then it's more difficult for me to work on code files, managing the lines.NVDA behaviour: in notepad++ it doesn't read line numbers, but selects correctly with proper Braille highlighting. In fact I have learnt to work with both. When I must check lines I turn JAWS on, when I have to select and correct, especially after second or third revision, I use NVDA.
BTW, I think this about Notepad++ is not concerning JAWS but Notepad++ itself.
My 2 cents. Hope it helps.
#blind #braille #bugReport #quill #QuillForAll -
I write this post publicly, not just for @quillforall folks, whom I promised the test with Braille to. I will share it here, because this experiment can be useful to other blind Braille users as well.
Guess what?
PoEdit, the translation editor for Windows, version 3.9.1, has the same bug found on QUILL 0.8.0 Beta 1. Braille display with JAWS screen reader doesn't detect selection highlighting with 7 and 8 dots under each single character and space.NVDA behaves correctly instead, both on QUILL and PoEdit, characters are properly selected. Unfortunately I have no idea whether Narrator can work with Focus Braille display, otherwise I'd have no issues in testing this as well.
This makes me suppose it's a @freedomscientific JAWS bug. I have mentioned them here as well, to make them aware. I have no idea of how to report a bug directly to them.
I think that not many blind professionals have reported the bug, as maybe most of them use commercial software more often, such as the Microsoft Office suite or, like me, simply surrendered to it.
As far as I can rememmber, the bug has always been there.
Today it's the first time I have properly identified it, and hopefully I can report it, as in 2006 I already tried to report an issue and it was fixed about 7 years later, it was even worse than this one because it prevented from using Sticky Keys for one-handed people. And my ex, who's blind and his left hand is injured, was definitely stuck. A vendor literally said in front of both of us "this bug has low priority as few people use sticky keys". Literally saying to a mobility impaired user, "you paid me but I don't cover your needs because you don't count". That was solved in JAWS 15.0, and the bug was there since 4.5.
NotePad++ editor behaves even more strangely for text selection, I always thought it was random but I managed to test it in deep today:
let's assume you have a blank file, so it starts with the line "1"; from margins and borders, in notepad++ settings, line number view must be checked on.
JAWS behavior: Notepad++ blank file, you type a sample sentence, let's say "QUILL for all".
You place the cursor on the q, then you select the whole line. You'll notice that the two l's of "quill for all" will not have the Braille cursor highlights.
What JAWS does: it highlights all the characters, including the line number. It behaves the opposite of how it should. It should highlight the text but not the line number. And the non-highlighted characters increase according to how long the line number is, space included. So, if "QUILL for all" is written on the 2800th line, the line number will be 2800, then space, then Q. Result? Braille display will highlight the line number with related space, then QUILL FO. Other letters are visually selected, but left behind.
If I deactivate the line numbers view, JAWS selects everything correctly. But then it's more difficult for me to work on code files, managing the lines.NVDA behaviour: in notepad++ it doesn't read line numbers, but selects correctly with proper Braille highlighting. In fact I have learnt to work with both. When I must check lines I turn JAWS on, when I have to select and correct, especially after second or third revision, I use NVDA.
BTW, I think this about Notepad++ is not concerning JAWS but Notepad++ itself.
My 2 cents. Hope it helps.
#blind #braille #bugReport #quill #QuillForAll -
Struggling with Poedit for Windows. Poedit 3.9.1. No idea of how to make it jump from an untranslated lime to another.
It's much better than working with Notepad++ for translations as there's no risk to confuse MSGID with MSGSTR. Performing latest #Quill 50% translation. It's a challenge I have accepted and I'd like the folks from @quillforall to be able to have a complete release in Italian when 1.0 is released. I believe in this project, it still has many things to fix, but #blind community in general should remember it's a young project and it should grow. Wondering if on AppleVis community it has already been mentioned. Never heard about it, just here on Fediverse. -
Struggling with Poedit for Windows. Poedit 3.9.1. No idea of how to make it jump from an untranslated lime to another.
It's much better than working with Notepad++ for translations as there's no risk to confuse MSGID with MSGSTR. Performing latest #Quill 50% translation. It's a challenge I have accepted and I'd like the folks from @quillforall to be able to have a complete release in Italian when 1.0 is released. I believe in this project, it still has many things to fix, but #blind community in general should remember it's a young project and it should grow. Wondering if on AppleVis community it has already been mentioned. Never heard about it, just here on Fediverse. -
I spent literally the whole day in translating the #quill software's interface into Italian then opened a pull request about it. Now, it's just matter of waiting! What I want to do is giving both feedback and concrete help to @quillforall project and maybe to bring it for the #diday - Digital Independence Day. But, I wait at least for the 1.0 release they're planning. And I'm counting on a more constructive collaboration with @bitsacb as well, in the limits of my possibilities.
There are good community-based realities in the USA, and in Europe. I tend to share my skills where I think they're needed. -
I spent literally the whole day in translating the #quill software's interface into Italian then opened a pull request about it. Now, it's just matter of waiting! What I want to do is giving both feedback and concrete help to @quillforall project and maybe to bring it for the #diday - Digital Independence Day. But, I wait at least for the 1.0 release they're planning. And I'm counting on a more constructive collaboration with @bitsacb as well, in the limits of my possibilities.
There are good community-based realities in the USA, and in Europe. I tend to share my skills where I think they're needed. -
The features for QUILL 1.0 are now locked in and you can see the listing on the web site - http://www.quillforall.org ... Now we will strictly focus on bug fixes, polish, rough edges and stability. #QUILL
-
The features for QUILL 1.0 are now locked in and you can see the listing on the web site - http://www.quillforall.org ... Now we will strictly focus on bug fixes, polish, rough edges and stability. #QUILL
-
"Pick up an oar."
Recently, BITS President Bishop invited us to picture everyone picking up an oar and rowing together to create new solutions, improve accessibility, and build something better for our community.
This afternoon, we were gratified to witness that vision come to life right here on Mastodon. Members and friends came together in real time to help investigate a reported issue with @quillforall, sharing ideas, testing possibilities, and moving the project forward.
Moments like these are what BITS is all about. Innovation isn't just about software. It's about people. When each of us picks up an oar, we all move accessibility forward together.
Learn more about BITS:
https://bits-acb.orgLearn more about Quill:
https://quillforall.org/ -
"Pick up an oar."
Recently, BITS President Bishop invited us to picture everyone picking up an oar and rowing together to create new solutions, improve accessibility, and build something better for our community.
This afternoon, we were gratified to witness that vision come to life right here on Mastodon. Members and friends came together in real time to help investigate a reported issue with @quillforall, sharing ideas, testing possibilities, and moving the project forward.
Moments like these are what BITS is all about. Innovation isn't just about software. It's about people. When each of us picks up an oar, we all move accessibility forward together.
Learn more about BITS:
https://bits-acb.orgLearn more about Quill:
https://quillforall.org/ -
I have just opened an issue on Github about Braille in quill - the accessible Windows screen reader-based writing suite. SPOILER: Braille users don't feel the difference between selected and non-selected text.
Issue here:
-
I have just opened an issue on Github about Braille in quill - the accessible Windows screen reader-based writing suite. SPOILER: Braille users don't feel the difference between selected and non-selected text.
Issue here:
-
@itsfoss Even though this was meant for people who are blind or low vision, maybe people who are sighted might benefit as well. http://quillforall.org #quill #quillforall
-
@itsfoss Even though this was meant for people who are blind or low vision, maybe people who are sighted might benefit as well. http://quillforall.org #quill #quillforall
-
It showed the HTML, so I will just post the link. http://quillforall.org #quill #quillforall
-
It showed the HTML, so I will just post the link. http://quillforall.org #quill #quillforall
-
Now, let's see what happens if I use HTML to post a hyperlink to Mastodon. <a href="http://quillforall.org">quill for all web site</a> #quill #quillforall
-
Now, let's see what happens if I use HTML to post a hyperlink to Mastodon. <a href="http://quillforall.org">quill for all web site</a> #quill #quillforall
-
This is a test to see if I can post to Mastodon from Quill. If you are seeing this post, it means it worked. #quill #quillforall
-
This is a test to see if I can post to Mastodon from Quill. If you are seeing this post, it means it worked. #quill #quillforall
-
-
-
All posts about QUILL will move to the new @quillforall account. Please consider following that account to keep updated about all things QUILL. We appreciate your support and patience. #QUILL
-
All posts about QUILL will move to the new @quillforall account. Please consider following that account to keep updated about all things QUILL. We appreciate your support and patience. #QUILL
-
@JeffBishop Have you thought of establishing a dedicated #Quill support account on Mastodon? That way, you personally wouldn't have to deal with Quill queries and it could allow other trusted Quill experts to help manage the account. If I've been under a rock and this has already been done, please forgive me.
-
@JeffBishop Have you thought of establishing a dedicated #Quill support account on Mastodon? That way, you personally wouldn't have to deal with Quill queries and it could allow other trusted Quill experts to help manage the account. If I've been under a rock and this has already been done, please forgive me.
-
One or two people recently posted that when typing the letter S in #Quill it would bring up Snippets and typing G brings up a gallery. I now can't locate those posts but I'm also seeing this? Did anyone figure out a way to resolve this? This is with 0.7.0 beta 1.
-
One or two people recently posted that when typing the letter S in #Quill it would bring up Snippets and typing G brings up a gallery. I now can't locate those posts but I'm also seeing this? Did anyone figure out a way to resolve this? This is with 0.7.0 beta 1.
-
The last of the braille features: Braille → Translation → Back-Translate (draft) now works on a selection: highlight part of a braille file and QUILL back-translates just that passage to
draft text (it still back-translates the whole file when nothing is selected), telling you which it used. This makes it easy to recover the source wording
of a single paragraph for review. Back-translation requires the optional QUILL Braille Pack. #QUILL -
The last of the braille features: Braille → Translation → Back-Translate (draft) now works on a selection: highlight part of a braille file and QUILL back-translates just that passage to
draft text (it still back-translates the whole file when nothing is selected), telling you which it used. This makes it easy to recover the source wording
of a single paragraph for review. Back-translation requires the optional QUILL Braille Pack. #QUILL -
Validate BRF Layout lists everything it finds so you can choose a warning and jump straight
to it; Next Warning and Previous Warning step you through them with spoken position and detail; and Warnings Summary tells you the total and the most common
issues. Validation only reads your file — it never changes it.
#QUILL -
Validate BRF Layout lists everything it finds so you can choose a warning and jump straight
to it; Next Warning and Previous Warning step you through them with spoken position and detail; and Warnings Summary tells you the total and the most common
issues. Validation only reads your file — it never changes it.
#QUILL -
A new Braille Validation menu checks a braille file for common layout problems, lines or pages that are too long, pages that look stuck, missing page
breaks, mixed line endings, stray non-braille characters, malformed or missing page indicators, page-numbering gaps or duplicates, inconsistent running
heads, and files that are Unicode braille rather than NABCC. #QUILL -
A new Braille Validation menu checks a braille file for common layout problems, lines or pages that are too long, pages that look stuck, missing page
breaks, mixed line endings, stray non-braille characters, malformed or missing page indicators, page-numbering gaps or duplicates, inconsistent running
heads, and files that are Unicode braille rather than NABCC. #QUILL -
Your progress is saved in a
small companion file beside the braille file, so it travels with your document and the braille itself is never modified.
#QUILL -
Your progress is saved in a
small companion file beside the braille file, so it travels with your document and the braille itself is never modified.
#QUILL -
A new Braille Proofing menu lets you keep track of proofreading without ever changing the braille file. You can mark the current braille page as proofed,
needs review, or clear its mark; add a note to a page; hear a spoken progress summary (how many pages are proofed, how many need review, and your estimated
completion); list proofed pages or pages needing review and jump straight to one; and export a plain-text proofing report. #QUILL -
All issues reported as of noon my time have been resolved in the editor that we could reproduce. #QUILL
-
QUILL remembers your place in braille files
When you reopen a braille file (.brf, .brl, .pef, .ueb), QUILL now returns your cursor to where you left off and tells you exactly where that is — for
example, "BRF file opened. 87 braille pages detected. Last position: braille page 12, line 14, cell 31." Your place is saved in a small companion file
beside the braille file, so the braille file itself is never changed. Restore is skipped in safe mode or when sidecar saving is turned off. #QUILL