[liblouis-liblouisxml] Re: output from file2brl

  • From: Greg Kearney <gkearney@xxxxxxxxx>
  • To: liblouis-liblouisxml@xxxxxxxxxxxxx
  • Date: Tue, 20 May 2014 07:15:39 -0700

Thanks recompiling and installing libelous seems to have fixed this. But still 
we need binary installers. I am happy to write the installer parts if I could 
ever get a clear idea just what needs to be installed and where, this includes 
ALL the libraries needed. I keep running into issues where everyone says it’s a 
“simple” compile only to discover that I need this or that version of some 
library.


Commonwealth Braille & Talking Book Cooperative
Greg Kearney, General Manager
605 Robson Street, Suite 850
Vancouver BC V6B 5J3
CANADA
Email: info@xxxxxxxxx

U.S. Address
21908 Almaden Av.
Cupertino, CA 95014
UNITED STATES
Email: gkearney@xxxxxxxxx



On May 20, 2014, at 6:23 AM, Michael Whapples (Redacted sender 
"mwhapples@xxxxxxx" for DMARC) <dmarc-noreply@xxxxxxxxxxxxx> wrote:

> As I said the binaries must be the exact same build. As an example if you did 
> the following (assumption: LibLouis source is in a folder named liblouis and 
> LibLouisUTDML source is in a folder named liblouisutdml next to it).
> 
> cd liblouis
> ./configure
> make
> sudo make install
> cd ../liblouisutdml
> ./configure
> make
> sudo make install
> cd ../liblouis
> ./configure --enable-ucs4
> make
> sudo make install
> 
> As you built liblouis after liblouisutdml and chose a different widechar 
> width then you will get such a problem.
> 
> I fully understand what you are getting at. I find GNU make stuff a bit too 
> complicated and feel we need something simpler. I have raised it before but 
> the view generally seems to be that sticking with GNU make is what people 
> want.
> 
> Providing binary builds for Mac would be useful. I know that may be producing 
> builds for every commit might get a bit complicated but surely binary build 
> for actual release versions would not be unreasonable to expect.
> 
> Michael Whapples
> On 20/05/2014 14:04, Greg Kearney wrote:
>> All that I did was to download the released versions of the programs and 
>> build them. So if I changed anything I did not knowingly do so. 
>> 
>> Once again this is proof of the need for precompiled binary installers. I 
>> can build the installers and I can even build various GUI front ends to the 
>> various liblouis tools but I keep running into issues like this why is it so 
>> hard to simply get prebiotic versions of this?
>> 
>> Sent from my iPhone
>> 
>> Greg Kearney
>> Commonwealth Braille and Talking Book Cooperative
>> 
>> On 20 May 2014, at 2:25 am, "Michael Whapples" <dmarc-noreply@xxxxxxxxxxxxx> 
>> (Redacted sender "mwhapples@xxxxxxx" for DMARC) wrote:
>> 
>>> Sorry about it being after the other stuff, but what about the other 
>>> suggestion, are you sure that liblouis and liblouisutdml (and thus 
>>> file2brl) are compiled with the same definition of widechar?
>>> 
>>> Basically liblouisutdml needs to be compiled against the exact build of 
>>> liblouis you will be using it with. If you have compiled liblouis again 
>>> since compiling liblouisutdml this could have caused the issue.
>>> 
>>> Looking at the output this possibly looks more likely and seems to make 
>>> sense to me with the output you got.
>>> 
>>> LibLouis having its own definition for unicode is something which has 
>>> bugged me and it bugs me even more that one can compile liblouis widechar 
>>> with different widths and this can impact upon programs which use it.
>>> 
>>> Michael Whapples
>>> On 20/05/2014 01:51, Greg Kearney wrote:
>>>> I am using the default configuration file 
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>> Greg Kearney
>>>> Commonwealth Braille and Talking Book Cooperative
>>>> 
>>>> On 19 May 2014, at 4:32 pm, "Michael Whapples" 
>>>> <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "mwhapples@xxxxxxx" for 
>>>> DMARC) wrote:
>>>> 
>>>>> A gut feeling looking at the output is that it could be an encoding issue 
>>>>> in reading the input file.
>>>>> 
>>>>> Could you send the configuration file being used?
>>>>> 
>>>>> On what you have sent me, or may be more accurately what I have recieved, 
>>>>> if you are using the default configuration files there should be no issue.
>>>>> 
>>>>> The HTML file I recieved is UTF-8 encoding, is this correct or might an 
>>>>> email client have changed it somewhere along the line?
>>>>> 
>>>>> Whilst the encoding is what I suspect, it seems unlikely if you are using 
>>>>> defaults and if the email system did not change the HTML encoding.
>>>>> 
>>>>> To explain the output the notation '\zXXXXXXXX' (as in '\z004e004e') 
>>>>> means that liblouis did not recognise a character with ordinal in the 
>>>>> number.
>>>>> 
>>>>> Putting some of the values into UTF16 encoding leads to something which 
>>>>> resembles the actual text of the file content.
>>>>> 
>>>>> Although thinking about this, UTF16 would not lead to such high values by 
>>>>> itself. What I am getting the feeling of is, LibLouis is compile for UCS4 
>>>>> (32-bit unicode) and LibLouisUTDML and thus file2brl are compiled for 
>>>>> UCS2 (16-bit unicode). So when file2brl reads the HTML, it is packing the 
>>>>> characters into 16-bit width characters, but then liblouis is reading 
>>>>> those as 32-bit wide characters, oops, out pops something which is 
>>>>> nonsense because it recognises none of the characters.
>>>>> 
>>>>> Are you sure your file2brl and liblouisutdml were compiled against the 
>>>>> particular version of liblouis you are using?
>>>>> 
>>>>> Michael Whapples
>>>>> On 19/05/2014 23:12, Greg Kearney wrote:
>>>>>> From a python program:
>>>>>> 
>>>>>> os.system("file2brl -t " +  newname + " " + out file )
>>>>>> 
>>>>>> which would be in normal usage:
>>>>>> 
>>>>>> file2brl -t file.html file.brf
>>>>>> 
>>>>>> 
>>>>>> Here is the HTML file: 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> And here is what I get:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Commonwealth Braille & Talking Book Cooperative
>>>>>> Greg Kearney, General Manager
>>>>>> 605 Robson Street, Suite 850
>>>>>> Vancouver BC V6B 5J3
>>>>>> CANADA
>>>>>> Email: 
>>>>>> info@xxxxxxxxx
>>>>>> 
>>>>>> 
>>>>>> U.S. Address
>>>>>> 21908 Almaden Av.
>>>>>> Cupertino, CA 95014
>>>>>> UNITED STATES
>>>>>> Email: 
>>>>>> gkearney@xxxxxxxxx
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On May 19, 2014, at 3:03 PM, John J. Boyer 
>>>>>> <john.boyer@xxxxxxxxxxxxxxxxx>
>>>>>>  wrote:
>>>>>> 
>>>>>> 
>>>>>>> What is your command line? Please give more detail when you have a 
>>>>>>> problem.
>>>>>>> 
>>>>>>> John
>>>>>>> 
>>>>>>> On Mon, May 19, 2014 at 02:56:06PM -0700, Greg Kearney wrote:
>>>>>>> 
>>>>>>>> When I run file2brl I am getting this kind of output, why?
>>>>>>>> 
>>>>>>>> '\z004e004e''\z-
>>>>>>>> 004c
>>>>>>>>  '\z00680054''\z-
>>>>>>>> 00200065''\z006-
>>>>>>>> 1004e''\z0069007-
>>>>>>>> 4''\z006e006f''-
>>>>>>>> \z006c0061''\z00-
>>>>>>>> 4e0020''\z00740-
>>>>>>>> 065''\z006f0077'-
>>>>>>>> '\z006b0072''\z-
>>>>>>>> 006f0020''\z0020-
>>>>>>>> 0066''\z0071004-
>>>>>>>> 5''\z00690075''\-
>>>>>>>> z00610074''\z00-
>>>>>>>> 6c0062''\z002000-
>>>>>>>> 65''\z0069004c'-
>>>>>>>> '\z00720062''\z0-
>>>>>>>> 0720061''\z0020-
>>>>>>>> 0079''\z00650053-
>>>>>>>> ''\z00760072''\-
>>>>>>>> z00630069''\z002-
>>>>>>>> 00065''\z004e00-
>>>>>>>> 28''\z0045004e''-
>>>>>>>> \z0053004c''\z0-
>>>>>>>> 0200029''\z00730-
>>>>>>>> 069''\z00610020-
>>>>>>>> ''\z00200020''\z-
>>>>>>>> 006f0077''\z006-
>>>>>>>> c0072''\z002d006-
>>>>>>>> 4''\z00690066''-
>>>>>>>> \z00730072''\z00-
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Commonwealth Braille & Talking Book Cooperative
>>>>>>>> Greg Kearney, General Manager
>>>>>>>> 605 Robson Street, Suite 850
>>>>>>>> Vancouver BC V6B 5J3
>>>>>>>> CANADA
>>>>>>>> Email: 
>>>>>>>> info@xxxxxxxxx
>>>>>>>> 
>>>>>>>> 
>>>>>>>> U.S. Address
>>>>>>>> 21908 Almaden Av.
>>>>>>>> Cupertino, CA 95014
>>>>>>>> UNITED STATES
>>>>>>>> Email: 
>>>>>>>> gkearney@xxxxxxxxx
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 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

Other related posts: