Hi Christo and others, I may need to revise the beginner documentation to provide some more examples and to point people to the opcodes list. Also, I feel we need a way to provide common examples for more opcodes and to update info on some opcodes such as "class" which may refer to a table that may or may not exist (I'll look into this and will try to come up with some improvements; if not for February release, perhaps by May release). Cheers, Joseph -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Christo de Klerk Sent: Wednesday, January 28, 2015 7:10 AM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: Proposal for capital and emphasis in UEB Hi Bert Many thanks. I am sure it will be very helpful. Kind regards Christo -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Bert Frees Sent: 28 January 2015 5:07 PM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: Proposal for capital and emphasis in UEB I know. Explaining the translation rules to someone without going deeper into how liblouis works internally has proven to be difficult. This is a deeply rooted problem, because the two ARE indeed very tied together. Currently, trying to understand the liblouis internals is still the best road to mastering the translation rules. I have done an attempt to decouple translation rules from liblouis specifics, in a document called "Liblouis Table Specification"[1]. It was successful in the sense that I managed to define precisely what each rule does, without going into implementation details. But on the other hand the definitions are still very technical (and complicated) in some cases. Something I quite like in this documentation though is that it tries to teach by example, and the examples are actually checked by running them through liblouis. Have a look, it might help you understand things better. Note that it's meant as a technical document, not so much as an easy read. Also it's work in progress. [1]: http://snaekobbi.github.io/liblouis-table-spec Keith Creasy writes: > As I said, it's better than a lot of what I've seen but it is not an > easy read. It's helpful to read the sections that talk about how > LibLouis works and then go over the specifics of op codes, arguments, etc. > > Good luck! > > -----Original Message----- > From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx > [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of > Christo de Klerk > Sent: Wednesday, January 28, 2015 9:15 AM > To: liblouis-liblouisxml@xxxxxxxxxxxxx > Subject: [liblouis-liblouisxml] Re: Proposal for capital and emphasis > in UEB > > That is exactly how I felt at the time when I last looked at some > LibLouis documentation. I had a look now at what Christian had pointed > me to and I had certainly never seen it before and as it is now, it > looks clear and helpful. The stuff I had looked at before, was > probably rather dated. > > > -----Original Message----- > From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx > [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Keith > Creasy > Sent: 28 January 2015 4:09 PM > To: liblouis-liblouisxml@xxxxxxxxxxxxx > Subject: [liblouis-liblouisxml] Re: Proposal for capital and emphasis > in UEB > > My comment regarding the LibLouis documentation from when I first > began to work with it is that it seems to be written from the > perspective of someone who is already very familiar with how LibLouis > works and therefor in places it isn't clear what is meant. It also has > a lot of strange typos, unless they've been corrected recently. It is > better documentation than I've seen with other projects but for > someone who is not familiar with the inner workings of LibLouis and > the background behind it the docs are difficult. Try reading it from > the perspective of someone new to LibLouis and understand exactly what > an "op code" is and what it does. The answer is that it depends and > isn't really clear at all. > > > I'm not criticizing, just trying to explain why people new to this > sometimes have a hard time understanding how to write and design tables. > > > -----Original Message----- > From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx > [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Bert > Frees > Sent: Wednesday, January 28, 2015 8:55 AM > To: liblouis-liblouisxml@xxxxxxxxxxxxx > Subject: [liblouis-liblouisxml] Re: Proposal for capital and emphasis > in UEB > > Surely a programmer who has been working with Duxbury tables for 30 > years can not be called a "dunce" :D If we can't teach you then the > documentation must be really bad! > > > Christian Egli writes: > >> On 01/28/2015 01:51 PM, Christo de Klerk wrote: >> >>> I would like to become involved in table development, but have not >>> been able to find documentation to teach a dunce like me in baby >>> steps how to get started. >> >> Have you looked at >> http://www.liblouis.org/documentation/liblouis.html >> in particular the section 2 named "How to Write Translation Tables". >> Does that help? >> 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