Hi Dipendra, you mean: # Copyright (C) 2010 Leon Ungier <Leon.Ungier@xxxxxxxxxxxx>, # Copyright (C) 2010 Mohammed R. Ramadan <mramadan@xxxxxxxxxx> # Copyright (C) 2010 Samuel Thibault <samuel.thibault@xxxxxxxxxxxx> As far as I know they have not contributed to the new (working) table. Not sure if attribution is needed when the previous table was not working. @Christian please add the above three lines and commit if this is appropriate. Thanks. Mesar On Wed 22/02/12,16:08, Dipendra Manocha wrote: > Hi Christian and John > > This problem was reported when we started working on improving the Indian > Language Braille tables. We took up Hindi as our first case and could not > resolve the letter and always opcode issue. Many mails were exchanged at > that time on this issue. > > Regarding names, this is about prologue of the table which has commented > lines about contributors of the table. I can make the changes on that front > to submit the table. > > Thanks > Dipendra > > > > > > > > > -----Original Message----- > From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx > [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of John J. > Boyer > Sent: 22 February 2012 15:29 > To: liblouis-liblouisxml@xxxxxxxxxxxxx > Subject: [liblouis-liblouisxml] Re: Tamil braille table > > As I understand it, the problem with the Tamil tables is that the always > opcode does not work when characters are defined as letters. However, nobody > else has reported this problem. Also, I hesitate to work with a language I > don't knnow. > > I am aware of a bug regarding emphasis that also needs fixing. I've been > looking for that one for months. However, my priority right now is > liblouisutdml because ViewPlus Technologies needs it and it is also needed > for BrailleBlaster. > > I'll let Christian discuss test suites. It would be nice to have tests that > would make certain that changes to the code don't break something else. > > John > > On Wed, Feb 22, 2012 at 10:15:27AM +0100, Christian Egli wrote: > > Hi all > > > > Mesar Hameed <mesar.hameed@xxxxxxxxx> writes: > > > > > I agree with you that unless the underlying problem is fixed, it > > > might be dificult to improve the table much further, but we wanted a > > > working solution so that tamil braille support can be included in > > > future nvda releases. > > > > So what exactly is the problem with liblouis? Has this been reported > > before? Maybe we could create a test case that clearly exhibits the > > problem then it would be easier reproduce and hence make it more > > likely to get fixed. > > > > > I feel that many problems can be found and ironed out if the > > > liblouis had an extensive test harness for the various tables. > > > > I'd be happy to work with you on this. > > > > > This is how I personally managed to quickly find a somewhat working > solution. > > > > Are you saying you have some kind of test harness? > > > > > Maybe Christian can merge in the names from the old tamil tables > > > before deleting and committing this new one. > > > > I'm confused. What am I supposed to do? > > > > Thanks > > Christian > > > > -- > > Christian Egli > > Swiss Library for the Blind, Visually Impaired and Print Disabled > > Grubenstrasse 12, CH-8045 Zürich, Switzerland > > > > ----- > > Jetzt kostenlos eidgenoessische und kantonale Abstimmungsunterlagen > > aus 17 Kantonen zum Hoeren auf CD abonnieren: medienverlag@xxxxxx For > > a description of the software, to download it and links to project > > pages go to http://www.abilitiessoft.com > > -- > John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. > http://www.abilitiessoft.com > Madison, Wisconsin USA > Developing software for people with disabilities > > For a description of the software, to download it and links to project pages > go to http://www.abilitiessoft.com > > For a description of the software, to download it and links to > project pages go to http://www.abilitiessoft.com For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com