Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

was the disconnect with the screen reader. Did the underlying development toolbox undergo any version changes from ( <4.2.0 ) to (4.2.0...4.2.1) to (4.2.2) ?? Great that normal transmission has resumed. Jonathan -Original Message- From: Tomas Kalibera Sent: Thursday, 22 December 2022

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

hursday, 22 December 2022 6:53 am To: Andrew Hart ; Jonathan Godfrey Cc: R-devel@r-project.org Subject: Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1. Hi Andrew, thanks a lot for your testing and I am looking forward to what you find out about the fixes in R-devel. You asked abou

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

Hi Andrew, thanks a lot for your testing and I am looking forward to what you find out about the fixes in R-devel. You asked about changes between 4.2.1 and 4.2.2 relevant to this. I don't think you overlooked anything, I looked now again at the source code diff and I didn't find anything re

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

HI Tomas, Thanks a lot for not letting this go. It is truly appreciated. I had been using Rterm directly as Jonathan had suggested since we discussed this a number of months ago on the R-devel list. However, about a week and a half ago I accidentally launched Rgui for R 4.2.2 (which I install

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

Dear Andrew, Jonathan, I had a closer look and tried to improve accessibility in Rgui, please see below. I would be grateful for feedback. Rgui supports three cursor types, which can be selected via Edit/GUI preferences/Cursor blink. The default is "partial", but for screen readers, please

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

On 9/22/22 23:15, Andrew Hart via R-devel wrote: On 22/09/2022 16:42, Toby Hocking wrote: Another option is to use https://emacspeak.sourceforge.net/ (version of emacs editor/ide which can speak letters/words/lines -- has a blind maintainer) with http

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

On 9/22/22 23:15, Andrew Hart via R-devel wrote: On 22/09/2022 16:42, Toby Hocking wrote: Another option is to use https://emacspeak.sourceforge.net/ (version of emacs editor/ide which can speak letters/words/lines -- has a blind maintainer) with http

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

3 September 2022 4:24 am To: Andrew Hart Cc: R-devel@r-project.org; Tomas Kalibera ; Jonathan Godfrey Subject: Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1. Tomas Kalibera has related that he has some scars from fighting with some unexpected interactions between UTF-8 and the GraphApp library

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

know why I hadn't seen Andrew's first message given I get other list traffic. Jonathan -Original Message- From: peter dalgaard Sent: Friday, 23 September 2022 4:24 am To: Andrew Hart Cc: R-devel@r-project.org; Tomas Kalibera ; Jonathan Godfrey Subject: Re: [Rd] Problem with

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

On 22/09/2022 16:42, Toby Hocking wrote: Another option is to use https://emacspeak.sourceforge.net/ (version of emacs editor/ide which can speak letters/words/lines -- has a blind maintainer) with https://ess.r-project.org/

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

On 9/22/22 18:24, peter dalgaard wrote: Tomas Kalibera has related that he has some scars from fighting with some unexpected interactions between UTF-8 and the GraphApp library that is used for RGui and I think he said that screen readers were involved. I wouldn't be surprised if this is a le

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

Another option is to use https://emacspeak.sourceforge.net/ (version of emacs editor/ide which can speak letters/words/lines -- has a blind maintainer) with https://ess.r-project.org/ (interface for editing and running R code from within emacs) On Thu, Sep 22, 2022 at 9:42 AM Duncan Murdoch wrote

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

On 22/09/2022 9:48 a.m., Andrew Hart via R-devel wrote: Hi. I'm having an issue with R 4.2.1 on Windows but I'm not sure if this is the right place to ask about it. If it's not, I'm hoping someone can point me in the right direction. I'm blind and have been using R for about 11 years now. The ba

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

Tomas Kalibera has related that he has some scars from fighting with some unexpected interactions between UTF-8 and the GraphApp library that is used for RGui and I think he said that screen readers were involved. I wouldn't be surprised if this is a leftover issue. (This is obviously a kind of

Re: [Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

There was a long apparently related thread back in May: https://stat.ethz.ch/pipermail/r-devel/2022-May/081708.html but that problem was supposedly patched in 4.2.1 ... On 2022-09-22 9:48 a.m., Andrew Hart via R-devel wrote: Hi. I'm having an issue with R 4.2.1 on Windows but I'm not sure if

[Rd] Problem with accessibility in R 4.2.0 and 4.2.1.

Hi. I'm having an issue with R 4.2.1 on Windows but I'm not sure if this is the right place to ask about it. If it's not, I'm hoping someone can point me in the right direction. I'm blind and have been using R for about 11 years now. The base build available on CRAN is quite accessible and wor