latex-access-devel — A list for people who develop, (or who are interested in the development of) lat

[Latex-access-devel] FW: Github Organisation

[Nathaniel S. <sch...@gm...>]

Hi all,

 

I note that over the last few months, there has been some updated activity
with the repository that was imported to Github. I was wondering who the
exact members are, since they have not publicly disclosed their membership
(I assume that Lukasz is one of them but can't be sure)?

 

I was wondering if it would be possible for an owner to give me, more than
contributor but also collaborator rights to the organisation? I am happy to
be explicitly denied direct push rights to the organisation's repositories
and their branches, although directly gaining push access to the website
repo would be nice.

 

Thanks,

 

Nathaniel

[Latex-access-devel] SF.net SVN: latex-access:[497] latex_access

[<ala...@us...>]

Revision: 497
          http://sourceforge.net/p/latex-access/code/497
Author:   alastair-irving
Date:     2020-05-24 11:54:44 +0000 (Sun, 24 May 2020)
Log Message:
-----------
Remove some iteritems

Modified Paths:
--------------
    latex_access/nemeth.py
    latex_access/speech.py

Modified: latex_access/nemeth.py
===================================================================
--- latex_access/nemeth.py	2020-05-24 11:54:36 UTC (rev 496)
+++ latex_access/nemeth.py	2020-05-24 11:54:44 UTC (rev 497)
@@ -34,7 +34,7 @@
         for letter in range (65,91):
             new_table["%c" % (letter)] = self.upperLetter
             
-        for (k,v) in new_table.iteritems():
+        for (k,v) in new_table.items():
             self.table[k]=v
 
 

Modified: latex_access/speech.py
===================================================================
--- latex_access/speech.py	2020-05-24 11:54:36 UTC (rev 496)
+++ latex_access/speech.py	2020-05-24 11:54:44 UTC (rev 497)
@@ -31,7 +31,7 @@
         new_table={"^":self.super,"_":("<sub>","</sub>"),"\\pmod":("mod <sub>","</sub>"),"\\sqrt":self.sqrt,"\\frac":self.frac,"\\tfrac":self.frac,"\\dfrac":self.frac,"\\int":self.integral,"\\iint":self.iintegral,"\\iiint":self.iiintegral,"\\mathbf":("<bold>","</bold>"),"\\mathbb":("<bold>","</bold>"),"\\mathcal":("<mathcal>","</mathcal>"),
                    "\\log":self.log,"\\ang":self.ang,"\\tag":self.tag,"\\hat":("","hat"),"\\widehat":("","hat"),"\\bar":("","bar"),"\\overline":("","bar"),"\\dot":("","dot"),"\\ddot":("","double dot"),"\\sum":self.sum,"\\prod":self.prod,"\\bigcup":self.union,"\\bigcap":self.intersection}
 
-        for (k,v) in new_table.iteritems():
+        for (k,v) in new_table.items():
             self.table[k]=v        
         self.space=" "
     

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

[Latex-access-devel] SF.net SVN: latex-access:[496] latex_access

[<ala...@us...>]

Revision: 496
          http://sourceforge.net/p/latex-access/code/496
Author:   alastair-irving
Date:     2020-05-24 11:54:36 +0000 (Sun, 24 May 2020)
Log Message:
-----------
Update imports for Python3

Modified Paths:
--------------
    latex_access/latex_access.py
    latex_access/nemeth.py
    latex_access/settings.py
    latex_access/speech.py
    latex_access/ueb.py

Modified: latex_access/latex_access.py
===================================================================
--- latex_access/latex_access.py	2017-06-03 10:35:00 UTC (rev 495)
+++ latex_access/latex_access.py	2020-05-24 11:54:36 UTC (rev 496)
@@ -17,9 +17,9 @@
 import re
 import types
 import os.path
-from path import get_path
+from .path import get_path
 import codecs
-import routing
+from . import routing
 
 # Regular expression to match LaTeX commands
 latex_command=re.compile(r"\\(([a-zA-Z]+)|[,!;\{\}\[\];:])")

Modified: latex_access/nemeth.py
===================================================================
--- latex_access/nemeth.py	2017-06-03 10:35:00 UTC (rev 495)
+++ latex_access/nemeth.py	2020-05-24 11:54:36 UTC (rev 496)
@@ -16,8 +16,8 @@
 module.'''
 
 
-import latex_access
-from latex_access import get_arg
+from . import latex_access
+from .latex_access import get_arg
 
 class nemeth(latex_access.translator):
     '''Class for nemeth translations.'''

Modified: latex_access/settings.py
===================================================================
--- latex_access/settings.py	2017-06-03 10:35:00 UTC (rev 495)
+++ latex_access/settings.py	2020-05-24 11:54:36 UTC (rev 496)
@@ -13,8 +13,8 @@
 #    You should have received a copy of the GNU General Public License along with this program; if not, visit <http://www.gnu.org/licenses>
 
 import os
-import ueb
-import nemeth
+from . import ueb
+from . import nemeth
 
 globals
 # Global settings for latex-access, these are the default values

Modified: latex_access/speech.py
===================================================================
--- latex_access/speech.py	2017-06-03 10:35:00 UTC (rev 495)
+++ latex_access/speech.py	2020-05-24 11:54:36 UTC (rev 496)
@@ -16,8 +16,8 @@
 '''Module to provide speech output for latex_access.'''
 
 
-import latex_access
-from latex_access import get_arg
+from . import latex_access
+from .latex_access import get_arg
 
 #Define a list of words to use as denominators of simple fractions
 denominators=[" over zero"," over1 "," half"," third"," quarter"," fifth"," sixth"," seventh"," eight"," ninth"]

Modified: latex_access/ueb.py
===================================================================
--- latex_access/ueb.py	2017-06-03 10:35:00 UTC (rev 495)
+++ latex_access/ueb.py	2020-05-24 11:54:36 UTC (rev 496)
@@ -16,9 +16,9 @@
 module.'''
 
 
-import latex_access
-from latex_access import get_arg
-from latex_access import get_optional_arg
+from . import latex_access
+from .latex_access import get_arg
+from .latex_access import get_optional_arg
 
 class ueb(latex_access.translator):
     '''Class for ueb translations.'''

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

[Latex-access-devel] New Mailing List

[Nathaniel S. <sch...@gm...>]

Hi all,

this is just a courtesy notice to announce that In view of recent developments, the latex-access mailing list has been moved from sourceForge to groups.io.  Github integration Has been set up, so pushed commits will be sent to the mailing list.  I will probably no longer be making posts to the original list.   Subscription involves standard procedure: subscribe by sending an email to lat...@gr... and  Reply to the confirmation email.Contribute to the list by emailing latex -ac...@gr....

Regards,

Nathaniel Schmidt

Sent from my iPhone 7

Re: [Latex-access-devel] Latex-Access Development Update: Ported / Migrated to Git From SVN

[Nathaniel S. <sch...@gm...>]

Hi Alastair,

Thank you for your email, and for pointing us to Derricks github repository.  I had been wondering where that code got to.  I will take your suggestion into consideration regarding the mailing list and leave it up to you as to what you want to do with the original SourceForge project.

Nathaniel Schmidt

Sent from my iPhone 7

> On 7 Nov 2019, at 7:39 am, Alastair Irving <ala...@gm...> wrote:
> 
> Hi All
> 
> 
> As people have probably gathered I haven't done any active development of latex-access for quite some time now and probably won't be doing so in the foreseable future.  If there are still people making use of the code then I'm very happy for them to continue development and look forward to seing what improvements are made.
> 
> 
> The move from SF to Github had been something I'd been intending to do for ages so thank you Nathaniel for that.  It would be best if there was a single repository for the code so I should probably plan to remove us from SF at some point, or at least add a link to the Github page.  It might therefore make sense to find a new home for this mailing list.
> 
> 
> A couple of years ago Derek Riemer emailed about his work on the NVDA addon, which is at
> 
> https://github.com/derekriemer/latex-access-matrix
> 
> I don't know the status of that work but it might be worth merging anything useful from it.
> 
> 
> Best wishes
> 
> 
> Alastair
> 
> 
> 
> 
> 
> 
> 
>> On 06/11/2019 11:41, Nathaniel Schmidt wrote:
>> Hi all,
>> 
>> Since I am (a) getting bounce-backs from the original latex-access project manager’s email address; and (b) have received no response as of yet from the latex-access development mailing list, I have decided, for now, to take matters into my own hands.  I have migrated the source code repository from SVN on SourceForge to Git on GitHub, using Github's importing tool.  The code is licensed under NGPL2.0, so I see no problem with this.  If anyone wants push access then privately send me your GitHub username.  distributed version control is more pragmatically viable than centralised control anyway, allowing one to work off-line.  I have not changed the name spaces of authors in original SVN commits.  The project is small enough that any contributors could probably just collaborate with only the original master branch; however, if it gets more complicated than this, then since I am not terribly experienced with Git, I would prefer to work with a GitHub Flow branching strategy.  Note that this is very different from a GitFlow branching strategy.  Also, to keep things simple, I would probably want to work from a shared repository model, rather than fork-and-pull model.  In other words, I would strongly recommend that other users / contributors do not fork the online repository to their own Github account!  So I will probably either not except any pull-requests from forked repos, or if I do, I will only accept pull-requests from a forked repo if I can also be absolutely assured that the contributor‘s local master branch has been linked with the remote original master branch via the appropriate Git commands.  My moderate understanding and somewhat limited experience probably won’t cope with much beyond that…
>> 
>> If anyone not experienced with version control systems or software development needs further help or clarification for anything, then let me know.  Repo can be cloned at.
>> https://github.com/SugarCaneNS/latex-access.git
>> 
>> Kind regards,
>> 
>> Nathaniel Schmidt
>> 
>> Sent from my iPhone 7
>> 
>> _______________________________________________
>> Latex-access-devel mailing list
>> Lat...@li...
>> https://lists.sourceforge.net/lists/listinfo/latex-access-devel
> 

Re: [Latex-access-devel] Latex-Access Development Update: Ported / Migrated to Git From SVN

[Alastair I. <ala...@gm...>]

Hi All


As people have probably gathered I haven't done any active development 
of latex-access for quite some time now and probably won't be doing so 
in the foreseable future.  If there are still people making use of the 
code then I'm very happy for them to continue development and look 
forward to seing what improvements are made.


The move from SF to Github had been something I'd been intending to do 
for ages so thank you Nathaniel for that.  It would be best if there was 
a single repository for the code so I should probably plan to remove us 
from SF at some point, or at least add a link to the Github page.  It 
might therefore make sense to find a new home for this mailing list.


A couple of years ago Derek Riemer emailed about his work on the NVDA 
addon, which is at

https://github.com/derekriemer/latex-access-matrix

I don't know the status of that work but it might be worth merging 
anything useful from it.


Best wishes


Alastair







On 06/11/2019 11:41, Nathaniel Schmidt wrote:
> Hi all,
>
> Since I am (a) getting bounce-backs from the original latex-access project manager’s email address; and (b) have received no response as of yet from the latex-access development mailing list, I have decided, for now, to take matters into my own hands.  I have migrated the source code repository from SVN on SourceForge to Git on GitHub, using Github's importing tool.  The code is licensed under NGPL2.0, so I see no problem with this.  If anyone wants push access then privately send me your GitHub username.  distributed version control is more pragmatically viable than centralised control anyway, allowing one to work off-line.  I have not changed the name spaces of authors in original SVN commits.  The project is small enough that any contributors could probably just collaborate with only the original master branch; however, if it gets more complicated than this, then since I am not terribly experienced with Git, I would prefer to work with a GitHub Flow branching strategy.  Note that this is very different from a GitFlow branching strategy.  Also, to keep things simple, I would probably want to work from a shared repository model, rather than fork-and-pull model.  In other words, I would strongly recommend that other users / contributors do not fork the online repository to their own Github account!  So I will probably either not except any pull-requests from forked repos, or if I do, I will only accept pull-requests from a forked repo if I can also be absolutely assured that the contributor‘s local master branch has been linked with the remote original master branch via the appropriate Git commands.  My moderate understanding and somewhat limited experience probably won’t cope with much beyond that…
>
> If anyone not experienced with version control systems or software development needs further help or clarification for anything, then let me know.  Repo can be cloned at.
> https://github.com/SugarCaneNS/latex-access.git
>
> Kind regards,
>
> Nathaniel Schmidt
>
> Sent from my iPhone 7
>
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel

Re: [Latex-access-devel] Latex-Access Development Update: Ported / Migrated to Git From SVN

[Nathaniel S. <sch...@gm...>]

Hi Kevin,

Thanks so much for doing this. I did not have access to Alastair’s Gmail address. I only had ala...@sj..., and the SourceForge address.

Nathaniel Schmidt

Sent from my iPhone 7

>> On 6 Nov 2019, at 11:12 pm, Kevin Fjelsted <kfj...@gm...> wrote:
> I have included email addresses for Derek Scott Riemer <Der...@co...>, Alastair Irving <ala...@gm...>,  two individuals that I know have contributed to the development in the hope that these addresses facilitate  communication.
> As a student and user of Latex-Access, I rely on the tool heavily and would love to see a unified platform for continued development and enhancement!
> -Kevin
> 
> 
>> On Nov 6, 2019, at 5:41 AM, Nathaniel Schmidt <sch...@gm...> wrote:
>> 
>> Hi all,
>> 
>> Since I am (a) getting bounce-backs from the original latex-access project manager’s email address; and (b) have received no response as of yet from the latex-access development mailing list, I have decided, for now, to take matters into my own hands.  I have migrated the source code repository from SVN on SourceForge to Git on GitHub, using Github's importing tool.  The code is licensed under NGPL2.0, so I see no problem with this.  If anyone wants push access then privately send me your GitHub username.  distributed version control is more pragmatically viable than centralised control anyway, allowing one to work off-line.  I have not changed the name spaces of authors in original SVN commits.  The project is small enough that any contributors could probably just collaborate with only the original master branch; however, if it gets more complicated than this, then since I am not terribly experienced with Git, I would prefer to work with a GitHub Flow branching strategy.  Note that this is very different from a GitFlow branching strategy.  Also, to keep things simple, I would probably want to work from a shared repository model, rather than fork-and-pull model.  In other words, I would strongly recommend that other users / contributors do not fork the online repository to their own Github account!  So I will probably either not except any pull-requests from forked repos, or if I do, I will only accept pull-requests from a forked repo if I can also be absolutely assured that the contributor‘s local master branch has been linked with the remote original master branch via the appropriate Git commands.  My moderate understanding and somewhat limited experience probably won’t cope with much beyond that…
>> 
>> If anyone not experienced with version control systems or software development needs further help or clarification for anything, then let me know.  Repo can be cloned at.
>> https://github.com/SugarCaneNS/latex-access.git
>> 
>> Kind regards,
>> 
>> Nathaniel Schmidt
>> 
>> Sent from my iPhone 7
>> 
>> _______________________________________________
>> Latex-access-devel mailing list
>> Lat...@li...
>> https://lists.sourceforge.net/lists/listinfo/latex-access-devel

Re: [Latex-access-devel] Latex-Access Development Update: Ported / Migrated to Git From SVN

[Kevin F. <kfj...@gm...>]

I have included email addresses for Derek Scott Riemer <Der...@co...>, Alastair Irving <ala...@gm...>,  two individuals that I know have contributed to the development in the hope that these addresses facilitate  communication.
As a student and user of Latex-Access, I rely on the tool heavily and would love to see a unified platform for continued development and enhancement!
-Kevin


> On Nov 6, 2019, at 5:41 AM, Nathaniel Schmidt <sch...@gm...> wrote:
> 
> Hi all,
> 
> Since I am (a) getting bounce-backs from the original latex-access project manager’s email address; and (b) have received no response as of yet from the latex-access development mailing list, I have decided, for now, to take matters into my own hands.  I have migrated the source code repository from SVN on SourceForge to Git on GitHub, using Github's importing tool.  The code is licensed under NGPL2.0, so I see no problem with this.  If anyone wants push access then privately send me your GitHub username.  distributed version control is more pragmatically viable than centralised control anyway, allowing one to work off-line.  I have not changed the name spaces of authors in original SVN commits.  The project is small enough that any contributors could probably just collaborate with only the original master branch; however, if it gets more complicated than this, then since I am not terribly experienced with Git, I would prefer to work with a GitHub Flow branching strategy.  Note that this is very different from a GitFlow branching strategy.  Also, to keep things simple, I would probably want to work from a shared repository model, rather than fork-and-pull model.  In other words, I would strongly recommend that other users / contributors do not fork the online repository to their own Github account!  So I will probably either not except any pull-requests from forked repos, or if I do, I will only accept pull-requests from a forked repo if I can also be absolutely assured that the contributor‘s local master branch has been linked with the remote original master branch via the appropriate Git commands.  My moderate understanding and somewhat limited experience probably won’t cope with much beyond that…
> 
> If anyone not experienced with version control systems or software development needs further help or clarification for anything, then let me know.  Repo can be cloned at.
> https://github.com/SugarCaneNS/latex-access.git
> 
> Kind regards,
> 
> Nathaniel Schmidt
> 
> Sent from my iPhone 7
> 
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel

[Latex-access-devel] Latex-Access Development Update: Ported / Migrated to Git From SVN

[Nathaniel S. <sch...@gm...>]

Hi all,

Since I am (a) getting bounce-backs from the original latex-access project manager’s email address; and (b) have received no response as of yet from the latex-access development mailing list, I have decided, for now, to take matters into my own hands.  I have migrated the source code repository from SVN on SourceForge to Git on GitHub, using Github's importing tool.  The code is licensed under NGPL2.0, so I see no problem with this.  If anyone wants push access then privately send me your GitHub username.  distributed version control is more pragmatically viable than centralised control anyway, allowing one to work off-line.  I have not changed the name spaces of authors in original SVN commits.  The project is small enough that any contributors could probably just collaborate with only the original master branch; however, if it gets more complicated than this, then since I am not terribly experienced with Git, I would prefer to work with a GitHub Flow branching strategy.  Note that this is very different from a GitFlow branching strategy.  Also, to keep things simple, I would probably want to work from a shared repository model, rather than fork-and-pull model.  In other words, I would strongly recommend that other users / contributors do not fork the online repository to their own Github account!  So I will probably either not except any pull-requests from forked repos, or if I do, I will only accept pull-requests from a forked repo if I can also be absolutely assured that the contributor‘s local master branch has been linked with the remote original master branch via the appropriate Git commands.  My moderate understanding and somewhat limited experience probably won’t cope with much beyond that…

If anyone not experienced with version control systems or software development needs further help or clarification for anything, then let me know.  Repo can be cloned at.
https://github.com/SugarCaneNS/latex-access.git

Kind regards,

Nathaniel Schmidt

Sent from my iPhone 7

[Latex-access-devel] New Email and Sf Account

[Nathaniel S. <sch...@gm...>]

Hi All,
> 
> I had initially sent this email to Alastair privately but thought it might be better to duplicate it up here.  I haven’t communicated with you guys for a while – probably not for about five years or so – but I am the initial contributor to the NVDA global plug-in code for Latex-Access.  due to my studies in  psychological science and disability related issues with my academic work, I have generally put off coding for a while, so I’ve been a bit off the grid.  My old email no longer works and I can’t remember the password to my old SourceForge  account so I have made a new one with my current email, with the username sugarcanens.  I was wondering if either Alastair or Robin would be happy to Remove my old one from the SVN commits and add the new account?
> 
> The main reason for this is because, with the community’s permission, I would like to make a couple more contributions.  The L-A Python package is no longer useful to me personally; however, as there have been one or two people using the global plug-in in the past, I feel it is probably a reasonable coding courtesy to keep the plug-in up-to-date.  specifically, I would like to add two suggestions:
> (1) Make the plug-in into a specific app module rather than a global plug-in.  this, I think, should not be too difficult.  The current arrangement is (and has always been) extremely sloppy.  I only did it because I only felt mildly competent with coding in Python and wanted an easy solution for myself.  Global keystrokes like control+M would clash too frequently with other applications.  The plug-in needs to be relevant to a specific application rather than being globally triggered from within specific editable text controls within any window for any application.  Creating an app module would mean that all the end-user needs to do is rename the AppModule to the name of the executable file for their chosen text editor.  Alternatively, to make it even easier, we could package the plug-in as an add-on and make a request to be allowed to upload it to the NVDA add-ons community, so long as it passes the test of usability.
> 
> (2) Make at least the COM object registrations / creation For this project in general compatible with both Python 2 and 3.  I am hoping that bridging the gap could be as simple as (a) adding a try... Except clause to either Import cPickle as pickle, or otherwise simply import pickle, since Python 3 prioritises the Excelerator C module anyway but one cannot explicitly import cPickle.  (b) Update latex_access_com.py to reflect this change.  I have recently switched from python 2.7 to 3.8 and I am trying to get used to the syntax and standard library.  I am hoping this won’t break anything major,  I’m not sure if it might mean that end users may or may not have to re-register the com objects if one committed the changes but I don’t think so.  The preprocessor COM object seems to register using Python 3 but the latex_access one doesn’t.
> (3) update the NVDA plug-in readme to reflect these changes.
> 
> Do you have any further thoughts on my propositions?
> 
> Kind regards,
> 
> 
> Nathaniel Schmidt
> 
> Sent from my iPhone 7

Re: [Latex-access-devel] question about translate method

[Kevin F. <kfj...@gm...>]

Yes it is still alive!
> On May 9, 2018, at 11:10 AM, Velegi István <iv...@gm...> wrote:
> 
> Hi all,
> 
> 
> Is this list still alive? If yes, I will post my questions about the latex_access class.
> 
> 
> Bests,
> 
> Istwan
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel

[Latex-access-devel] question about translate method

[Velegi I. <iv...@gm...>]

Hi all,


Is this list still alive? If yes, I will post my questions about the 
latex_access class.


Bests,

Istwan

Re: [Latex-access-devel] NVDA

[Derek S. R. <Der...@co...>]

Sorry, this took me forever to respond to.

On Sat, Jun 3, 2017 at 12:25 PM, Alastair Irving <
ala...@gm...> wrote:

> Your addon looks great so I'd be happy to include it in latex-access.  If
> you give me your sourceforge username I'll attempt to give you access to
> the SVN repository.  I suppose I should move the whole project to Github at
> some point.
>
Either way, Actually, we could make mine a submodule? I am I think
dri...@gm... on sourceforge.

>
> A few comments:
>
> 1. You should apply my bug fix from earlier to your addon so that the read
> line function works when latex-access is turned off.  Its a one word fix,
> speech to controlTypes.
>
I think I did. One of those is deprecated,  and I thought I changed it, but
maybe I forgot.

> 2. I agree that its better not to use COM objects, once your addon is part
> of trunk it should be easy to build an addon with the latest code.
> Incidentally how does one build your addon?  I got it installed by copying
> the files manually but I couldn't work out how to build using your
> sconsstruct file.
>
Are you familiar with scons? In short
pip install markdown, then install scons, then just scons in that dir
should build an nvda-addon file (That's the official  addon template in
use).

> 3. What are your thoughts on Braille?  It would be amazing if we could get
> propper support in VDA including cursor routing.    I wondered if it would
> be possible to define a braille region object in VDA for latex which
> handles the translation and routing.  I don't know much about NVDA
> development but would be happy to help with the latex-access side of things.
>
This is what I'm doing. The challenge is that our router has your routing
table, then NVDA's routing table. I either need to go through both of them,
or come up with an algorithm to combine the two into one set of indexes.
That'There is a method to get a braille region.
My next step is to implement the whole sub super thing to make lower and
higher pitched speech (Or sub and super) depending on settings (That dialog
will be after that). I redesigned the addon quite heavily from what's in
trunk, so forgive me if you can't recognize the code from what it was. It
should be more scalable now (If my several years of addon development are
teaching me lessons).
Cheers, and I'm glad this project is still around.

>
>
> Best wishes
>
> Alastair
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel
>



-- 

Derek Riemer: Improving the world one byte at a time!

   - University of Colorado Boulder Department of computer science, 4th
   year undergraduate student.
   - Accessibility enthusiast.
   - Proud user of the NVDA screen reader.
   - Open source enthusiast.
   - Skier.

Personal website <http://derekriemer.com>

Re: [Latex-access-devel] NVDA

[Derek S. R. <Der...@co...>]

I'm about to go out of town this week so I won't respond until next
weekend! I will fix those (Oh, reason constants? Yeah, they were just
deprecated). I'm playing with doing a custom braille region. It's
complicated, because I have both NVDA's routing table and latex-accesses
routing table. I need to either use both one after another, or design a
merge routing tables algorithm.

Follow the build install instructions here.
https://github.com/nvdaaddons/AddonTemplate

On Sat, Jun 3, 2017 at 12:25 PM, Alastair Irving <
ala...@gm...> wrote:

> Hi All
>
> Firstly appologies, when my old email address finally stopped working I
> must have forgotten to resubscribe to my own mailing list so haven't been
> receiving messages for quite a while.  Until my commit earlier I just
> assumed the list was silent.
>
> Secondly to respond to Derek's message:
>
> Your addon looks great so I'd be happy to include it in latex-access.  If
> you give me your sourceforge username I'll attempt to give you access to
> the SVN repository.  I suppose I should move the whole project to Github at
> some point.
>
> A few comments:
>
> 1. You should apply my bug fix from earlier to your addon so that the read
> line function works when latex-access is turned off.  Its a one word fix,
> speech to controlTypes.
> 2. I agree that its better not to use COM objects, once your addon is part
> of trunk it should be easy to build an addon with the latest code.
> Incidentally how does one build your addon?  I got it installed by copying
> the files manually but I couldn't work out how to build using your
> sconsstruct file.
> 3. What are your thoughts on Braille?  It would be amazing if we could get
> propper support in VDA including cursor routing.    I wondered if it would
> be possible to define a braille region object in VDA for latex which
> handles the translation and routing.  I don't know much about NVDA
> development but would be happy to help with the latex-access side of things.
>
>
> Best wishes
>
> Alastair
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel
>



-- 

Derek Riemer: Improving the world one byte at a time!

   - University of Colorado Boulder Department of computer science, 4th
   year undergraduate student.
   - Accessibility enthusiast.
   - Proud user of the NVDA screen reader.
   - Open source enthusiast.
   - Skier.

Personal website <http://derekriemer.com>

[Latex-access-devel] NVDA

[Alastair I. <ala...@gm...>]

Hi All

Firstly appologies, when my old email address finally stopped working I 
must have forgotten to resubscribe to my own mailing list so haven't 
been receiving messages for quite a while.  Until my commit earlier I 
just assumed the list was silent.

Secondly to respond to Derek's message:

Your addon looks great so I'd be happy to include it in latex-access.  
If you give me your sourceforge username I'll attempt to give you access 
to the SVN repository.  I suppose I should move the whole project to 
Github at some point.

A few comments:

1. You should apply my bug fix from earlier to your addon so that the 
read line function works when latex-access is turned off.  Its a one 
word fix, speech to controlTypes.
2. I agree that its better not to use COM objects, once your addon is 
part of trunk it should be easy to build an addon with the latest code.  
Incidentally how does one build your addon?  I got it installed by 
copying the files manually but I couldn't work out how to build using 
your sconsstruct file.
3. What are your thoughts on Braille?  It would be amazing if we could 
get propper support in VDA including cursor routing.    I wondered if it 
would be possible to define a braille region object in VDA for latex 
which handles the translation and routing.  I don't know much about NVDA 
development but would be happy to help with the latex-access side of things.


Best wishes

Alastair

Re: [Latex-access-devel] SF.net SVN: latex-access:[495] nvda/latex_access.py

[Derek S. R. <Der...@co...>]

Guys,
I have an NVDA addon which is vastly improved on a github repo under
https://github.com/derekriemer/latex-access-matrix
I actually thought this project was dead, because noone responded to me
asking if you guys want my changes back, and how we go about doing this.
I'd be happy to contribute the back, and I'm planning to make this plugin
and the routing stuff work, which means I'll be getting rid of using COM
altogether since it doesn't support getting routing incexes.
Thanks.

On Sat, Jun 3, 2017 at 4:35 AM, <ala...@us...>
wrote:

> Revision: 495
>           http://sourceforge.net/p/latex-access/code/495
> Author:   alastair-irving
> Date:     2017-06-03 10:35:00 +0000 (Sat, 03 Jun 2017)
> Log Message:
> -----------
> Bug fix with read line function in NVDA plugin not working when processing
> is off.
>
> Modified Paths:
> --------------
>     nvda/latex_access.py
>
> Modified: nvda/latex_access.py
> ===================================================================
> --- nvda/latex_access.py        2015-03-13 19:58:35 UTC (rev 494)
> +++ nvda/latex_access.py        2017-06-03 10:35:00 UTC (rev 495)
> @@ -118,7 +118,7 @@
>                                 speech.speakMessage (spokenLine)
>                                 braille.handler.message (brailledLine)
>                         else:
> -                               speech.speakTextInfo(info,
> unit=textInfos.UNIT_LINE,reason=speech.REASON_CARET)
> +                               speech.speakTextInfo(info,
> unit=textInfos.UNIT_LINE,reason=controlTypes.REASON_CARET)
>                 else:
>                         speech.speakSpelling(info.text)
>         script_reportCurrentLine.__doc__ = _("If latex-access translation
> is on, Translates the current line into nemeth braille and speech.  If
> translation is turned off, the current line is spoken as normal.  If this
> keystroke is pressed twice, the current line is spellt out.")
>
> This was sent by the SourceForge.net collaborative development platform,
> the world's largest Open Source development site.
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel
>



-- 

Derek Riemer: Improving the world one byte at a time!

   - University of Colorado Boulder Department of computer science, 4th
   year undergraduate student.
   - Accessibility enthusiast.
   - Proud user of the NVDA screen reader.
   - Open source enthusiast.
   - Skier.

Personal website <http://derekriemer.com>

[Latex-access-devel] SF.net SVN: latex-access:[495] nvda/latex_access.py

[<ala...@us...>]

Revision: 495
          http://sourceforge.net/p/latex-access/code/495
Author:   alastair-irving
Date:     2017-06-03 10:35:00 +0000 (Sat, 03 Jun 2017)
Log Message:
-----------
Bug fix with read line function in NVDA plugin not working when processing is off.

Modified Paths:
--------------
    nvda/latex_access.py

Modified: nvda/latex_access.py
===================================================================
--- nvda/latex_access.py	2015-03-13 19:58:35 UTC (rev 494)
+++ nvda/latex_access.py	2017-06-03 10:35:00 UTC (rev 495)
@@ -118,7 +118,7 @@
 				speech.speakMessage (spokenLine)
 				braille.handler.message (brailledLine)
 			else:
-				speech.speakTextInfo(info,unit=textInfos.UNIT_LINE,reason=speech.REASON_CARET)
+				speech.speakTextInfo(info,unit=textInfos.UNIT_LINE,reason=controlTypes.REASON_CARET)
 		else:
 			speech.speakSpelling(info.text)
 	script_reportCurrentLine.__doc__ = _("If latex-access translation is on, Translates the current line into nemeth braille and speech.  If translation is turned off, the current line is spoken as normal.  If this keystroke is pressed twice, the current line is spellt out.")

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

[Latex-access-devel] Translating latex-access into polish and a few questions

[Lukasz G. <wul...@gm...>]

Hello,
my friend and I wanted to translate latex-access into polish. During the translation some things weren’t clear for us. In the file speech_modified.py why are you adding <sup> and </sup> to the translations of superscripts in line 78? Which LaTeX formula is translated in line 109 to 114. I’m asking, because for me all of roots formulas are translated above. What the primes are used for example during the translation of superscripts? We also have a problem with translating superscripts into polish braille notation. In our notation after the base of the power we have the power sign which is dots 3 4 6 and then we have lowered digits. For example dots 2 5 6 means 4 in the index of the power. We are not sure how to make the digits lowered. Thanks for any help.
Lukas

[Latex-access-devel] Fwd: Help Please

[Kevin F. <kfj...@gm...>]

Dan;
Based on my real use experience using Latex-Access in a class situation, Latex-Access the program for which this list is established already works well with the JAWS screen reader as well as to a lesser degree with NVDA.
Perhaps through this list we can assist you or your technical resources in getting it up and running?
-Kevin
kfj...@gm... <mailto:kfj...@gm...>


> Begin forwarded message:
> 
> From: Dan Wilson <dan...@ba...>
> Subject: [Latex-access-devel] Help Please
> Date: March 31, 2017 at 1:09:50 AM CDT
> To: "lat...@li..." <lat...@li...>
> 
> Good morning,
>  
> Does anyone know of any companies or individuals in the UK who can provide the complete solution to make the LATEX format accessible to a screen reader like JAWS?
>  
> We would be willing to pay for these services and the provision of any relevant software required. This is for 2 blind maths students who are about to begin studying from September this year.
>  
> Any help would be greatly appreciated.
>  
> Best Regards
> 
> Dan
> 
> 
> Dan Wilson
> Assessment Team Manager
> 07749 519 517
> Switch: 01204 534 311
> dan...@ba... <mailto:dan...@ba...>
> www.barrybennett.co.uk <http://www.barrybennett.co.uk/>	
> 
>  <http://www.barrybennett.co.uk/our-training-sessions.html>
> 
> P Please consider the environment before printing this email <http://thinkbeforeprinting.org/>
> Email Disclaimer:
> This message and its attachments is intended for the above named only, and may be privileged or confidential.
> If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone. If you have received this message in error please destroy it and contact the sender via return e-mail. All reasonable precautions have been taken to ensure that no viruses are present in this e-mail. As Barry Bennett Ltd cannot accept responsibility for loss or damage arising from the use of this message or attachments we recommend that you undertake your virus checking procedures prior to use.
> Please note that Barry Bennett Ltd does not enter into any form of contract via this medium, nor is our staff authorised to do so on our behalf. Any opinions expressed in this e-mail are those of the sender, and will not reflect the opinions of Barry Bennett Ltd unless specifically stated. 
> Any calls made to Barry Bennett Ltd may be recorded for training and monitoring purposes.
> Registered address: DTE, The Exchange, 5 Bank Street, Bury, BL9 0DN
> Registration No: 1006315 England
> VAT Registration No: 147 1468 61
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________>
> Latex-access-devel mailing list
> Lat...@li... <mailto:Lat...@li...>
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel <https://lists.sourceforge.net/lists/listinfo/latex-access-devel>

[Latex-access-devel] Help Please

[Dan W. <dan...@ba...>]

Good morning,

Does anyone know of any companies or individuals in the UK who can provide the complete solution to make the LATEX format accessible to a screen reader like JAWS?

We would be willing to pay for these services and the provision of any relevant software required. This is for 2 blind maths students who are about to begin studying from September this year.

Any help would be greatly appreciated.

Best Regards

Dan



Dan Wilson
Assessment Team Manager
07749 519 517
Switch: 01204 534 311
dan...@ba...
www.barrybennett.co.uk<http://www.barrybennett.co.uk>


[http://www.barrybennett.co.uk/soclink/logolink.png]

[http://www.barrybennett.co.uk/soclink/training-esig.png]<http://www.barrybennett.co.uk/our-training-sessions.html>

P Please consider the environment before printing this email<http://thinkbeforeprinting.org>

Email Disclaimer:
This message and its attachments is intended for the above named only, and may be privileged or confidential.
If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone. If you have received this message in error please destroy it and contact the sender via return e-mail. All reasonable precautions have been taken to ensure that no viruses are present in this e-mail. As Barry Bennett Ltd cannot accept responsibility for loss or damage arising from the use of this message or attachments we recommend that you undertake your virus checking procedures prior to use.
Please note that Barry Bennett Ltd does not enter into any form of contract via this medium, nor is our staff authorised to do so on our behalf. Any opinions expressed in this e-mail are those of the sender, and will not reflect the opinions of Barry Bennett Ltd unless specifically stated.
Any calls made to Barry Bennett Ltd may be recorded for training and monitoring purposes.
Registered address: DTE, The Exchange, 5 Bank Street, Bury, BL9 0DN
Registration No: 1006315 England
VAT Registration No: 147 1468 61

Re: [Latex-access-devel] Problems getting latex-access to work in a Raspi with BRLTTY

[Daniel D. <dan...@gm...>]

It's been the better part of 5 years since I've done any work on this.

I quickly tested and brltty segfaults for me, so you'll need to investigate
that. I don't have time to look into it right now.


   - install.py works for me - I don't know what your issue is. Make sure
   you run the script with the working directory the same as where the install.
   py is located.
   - Ensure that the latex-access python modules are in the pythonpath and
   you can load / translate a test string in the python shell.
   - Make sure /etc/brltty/ContractionTables/latex-access.ctb is executable
   and points to python v2.
   - Set brltty to use the latex-access table and 6 dot contracted Braille.
   You should be able to verify this in the prefs menu.


Sorry I can not help further. Not sure if anyone else is still maintaining
this stuff - Alastair may be able to chip in with some extra.



On Fri, Jul 15, 2016 at 9:08 AM, Amanda Lacy <la...@gm...> wrote:

> Here are the steps I've taken:
>
> I tried to run install.py but it wouldn't copy any files even if I ran
> it as root. I have no idea why. Instead I copied all the files in
> latex-access/latex_access to
> /usr/lib/python2.7/dist-packages/latex_access. I think that's all the
> script does.
>
> I added the line
> contraction-table latex-access
> to /etc/brltty.conf. This is because BRLTTY will not let you save that
> setting through its menu.
>
> In the BRLTTY menu, I changed the Braille style to contracted. The
> latex-access manual says to change it to 6-dot contracted, but there
> is no such option.
>
> I opened a test latex file in nano, found a line with an equation and
> hit control-m. The Braille did not change.
>
> What else should I try? Apparently I'm missing something. Thanks.
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel
>

[Latex-access-devel] Problems getting latex-access to work in a Raspi with BRLTTY

[Amanda L. <la...@gm...>]

Here are the steps I've taken:

I tried to run install.py but it wouldn't copy any files even if I ran
it as root. I have no idea why. Instead I copied all the files in
latex-access/latex_access to
/usr/lib/python2.7/dist-packages/latex_access. I think that's all the
script does.

I added the line
contraction-table latex-access
to /etc/brltty.conf. This is because BRLTTY will not let you save that
setting through its menu.

In the BRLTTY menu, I changed the Braille style to contracted. The
latex-access manual says to change it to 6-dot contracted, but there
is no such option.

I opened a test latex file in nano, found a line with an equation and
hit control-m. The Braille did not change.

What else should I try? Apparently I'm missing something. Thanks.

[Latex-access-devel] (no subject)

[Theodore C. <the...@tr...>]

[Latex-access-devel] Nemeth

[Devanshu A. <agr...@go...>]

Hello,

I am a JAWS (13.0) user, and I have been using Latex-Access since August
2014. I have not updated Latex-Access since I first installed it, since I
have made many personal customizations to the python files (for example, I
use the comma (') in translations to force JAWS to pause for a moment while
reading).

While Latex-Access has worked very well for me, I admit that it is still
sometimes difficult to follow mathematics by audio. I have therefore
recently begun experimenting with the Nemeth feature of Latex-Access. I use
a 40-cell Braille Display. I encountered the following problems:

1. When there is a long equation, the Braille Display only displays the
beginning of the equation, even if the cursor is near the end of the line.
As a result, I cannot see the rest of the equation in Braille.

2. This problem is related to Problem 1. When an equation is long and only
the beginning of it is displayed, I tried to use the wheels on the Braille
display to see the rest of the equation. But this does not work.

3. I tried using the router keys on the Braille display to move the cursor
to a particular point in the equation. But this does not work, and JAWS
simply routes to the desktop.

I believe Problem 3 will be nontrivial to fix, since it will require
mapping from the Braille translation back to the original latex. I think
this can be done, but it will require a bit of work.

But I believe Problem 1 (and hence Problem 2 as well) should be simple to
fix. Looking at the source code, it appears to me that the two relevant
functions are BrailleBuildLine (in latex.jss) and nemeth (in
latex_access_com.py). This is what I tried: In BrailleBuildLine, I defined
an additional string
    upto = GetFromStartOfLine()
This string is passed to the nemeth function along with input. This way,
the nemeth function knows exactly where the cursor is. I then modified
nemeth to return only 40 characters of the output, where the 40 characters
are chosen based on the position of the cursor (where the position is
determined by upto).

Unfortunately, my modifications did not work. I narrowed down my problem to
the following issue: In the BrailleBuildLine function, I noticed that if I
modify the line
     input = Getline()
to the line
     input = "hello"
then there is absolutely no change; that is, the Braille display translates
latex into Braille as it usually does instead of displaying "hello" as I
was expecting.

What could be the problem? Is there something wrong with my approach? Are
there functions in some files that I am overlooking?

Please note that after every modification I was trying, I was restarting
JAWS and used the ctrl + alt + shift + r command.

Also, please note that I am using the Latex-Access scripts from August 2014
(along with some small modifications I have made to it). So if some of the
issues with the Nemeth feature have already been resolved, then just let me
know.

Thanks in advance,

Devanshu

Re: [Latex-access-devel] Did my email with the matrix browser script make it?

[Alastair I. <ala...@sj...>]

Yes, it did.  Unfortunately I haven't had time to test the script yet.  
I'll try and look at it over the weekend.

Alastair



On 19/03/2015 16:30, derek riemer wrote:
>
> Thanks.
> -- 
> ------------------------------------------------------------------------
>
>
>     Derek Riemer
>
> Department of Computer science Undergrad, proud CILA member, music 
> lover, avid skier, and much more.
>
> "Not everything that is faced can be changed, but nothing can be 
> changed until it is faced." - James Baldwin
>
> email me at der...@co... <mailto:der...@co...>
> Phone: (303) 906-2194
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
>
>
> _______________________________________________
> Latex-access-devel mailing list
> Lat...@li...
> https://lists.sourceforge.net/lists/listinfo/latex-access-devel