Sorry guys, to be clear it's not a problem with liblouisudtml build or running but probably the way I've configured it. I've added a fix to the tables to solve the italic bug. It uses a UTF-8 character which represents the braille character. It's this I couldn't get to work in brailleblaster. It kept just displaying the \x281C etc. I will have to revisit this again as I'm not 100% sure I tried it with the latest Win 32-bit dll, although I thought I had. Someone suggested including the table 'braille-patterns.cti' but since liblouisudtml It's not so clear to me the structure of the tables. Maybe an 'expert' can try and explain it to me VERY simply. RE maintaining the UK tables - the original writer unfortunately died. I've submitted a couple of changes etc. I haven't check the backward translation! That indeed would be a good test of the tables.
I'll see what I can do next week. Cheers Paul On 16/11/2012 4:04 PM, Keith Creasy wrote:
I have liblouisutdml building using the MSVC command-line tools under Windows 64. What problems are you having? I'd be happy to help get you over this hump. Keith Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx Phone: 502.895.2405 Skype: keith537 -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Joseph Lee Sent: Friday, November 16, 2012 9:22 AM To: liblouis-liblouisxml Subject: [liblouis-liblouisxml] Re: revised UEB table: first part done Hi, I'm still experimenting with UeB on my BrailleNote and am learning the code. Also, I asked a friend of mind to give me some URL's which explains differences between U.S. and UeB codes. At this point, we have a half-baked solution: grade II and UeB works fine, but we need to work on grade 1 table where all symbols reside. Working on grade 1 would be a challenge unless if we have many testers who would be willing to help us and if United Kingdom code's punctuation matches that of UeB. If UK code's punctuation and other symbols match that of UEB, then I'd be happy to tell en-ueb-g1.ctb to include en-gb-g1.ctb, provided that there are no major conflicts. But for now, I'd say let's concentrate on grade 2, as this task is easier - we just need to find differences in text presentation (this task will take up to a week to complete). Thanks. Cheers, Joseph P.S. Who maintains UK codes for LibLouis? On 11/16/12, Paul Wood (Torch) <paulw@xxxxxxxxxxxxxx> wrote:John, First I appreciate that the US tables are undoubtedly the best, but are they the best way forward for UEB? Do we have access to a list of differences from BANA to UEB? Maybe the Australians have one? The reason I ask is the gb or SEB tables might not be 100% but are pretty close, we have work at the moment checking this on a 'normal' book, but experience so far is very good, only picking up foreign words and problems with apostrophes and quotes etc. But we do have a good list of differences between the codes, so with a table expert, which I'm not! it should be quite easy to modify the SEB (gb) tables to UEB. I still haven't got a working latest liblouisudtml in windows, which has been the delay for us. I'm going down the DAISY pipeline2 route and have latest betas to test this week, which I hope to do today or Monday. If you can access a good list of differences for US to UEB, then of course that would be the best approach! more info http://en.wikipedia.org/wiki/English_Braille HTH Paul On 16/11/2012 10:14, John J. Boyer wrote:Hi Joseph, Great work. I think that trying to fix the UEB grade 1 table would be more work than modifying en-us-g1 for UEB. The en-us tables contain a lot of knowledge that the persons who made the UEB tables didn't have. From what I know of UEB largesign opcodes should be replaced with always joinword should be replaced with word or maybe deleted. John On Fri, Nov 16, 2012 at 01:03:01AM -0800, Joseph Lee wrote:Hi folks, Attached is the revised UEB table based on en-us-g2.ctb. For consistency, I named the file as "en-ueb-g2.ctb". In the first part: . Modified the header to add my email address and wrote the fact that this table is for testing purposes only. Also declared that this table is based on en-us-g2.ctb. . Removed "ally" and "ation" contractions, as they are not needed anymore. Just curious: are there any problems with uebc-g1/g2.ctb? If the problems are severe, then starting from scratch would be a good idea, with the basis for these tables coming from en-us-g1/g2.ctb. Thanks. //JL-- Paulw.torchtrust signature Paul Wood, Technical Services Leader *Torch Trust* Torch House, Torch Way, Market Harborough, Leics. LE16 9HL, UK Direct Line: *+44(0)1858 438269* Tel: *+44(0)1858 438260*, Fax: *+44(0)1858 438275* Email: paulw@xxxxxxxxxxxxxx <mailto:paulw@xxxxxxxxxxxxxx> Website: www.torchtrust.org <http://www.torchtrust.org/> ____________________________________________________ Chief Executive: Dr Gordon Temple Charity No. 1095904 Privileged/Confidential Information may be contained in this message. If you are not the intended recipient please destroy this message and kindly notify the sender by reply email. The computer from which this mail originates is equipped with virus screening software. However Torch Trust cannot guarantee that the mail and its attachments are free from virus infection.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
-- Paulw.torchtrust signature Paul Wood, Technical Services Leader *Torch Trust* Torch House, Torch Way, Market Harborough, Leics. LE16 9HL, UK Direct Line: *+44(0)1858 438269* Tel: *+44(0)1858 438260*, Fax: *+44(0)1858 438275* Email: paulw@xxxxxxxxxxxxxx <mailto:paulw@xxxxxxxxxxxxxx> Website: www.torchtrust.org <http://www.torchtrust.org/> ____________________________________________________ Chief Executive: Dr Gordon Temple Charity No. 1095904 Privileged/Confidential Information may be contained in this message. If you are not the intended recipient please destroy this message and kindly notify the sender by reply email. The computer from which this mail originates is equipped with virus screening software. However Torch Trust cannot guarantee that the mail and its attachments are free from virus infection.
