Hei, John! Thank you for your quick response! You wrote: > e-mail addresses should be handled correctly. The < and > entities > will be converted to their corresponding characters in the process of > parsing. Yes, that's right. > The strings .com .org etc., which are defined by the compbrl > opcode will cause the entire shitespace surrounded string in which they > occur to be converted into computer braille. A different tablle is not > necessary. It is necessary - really, at least to meet the Norwegian standards. Let me explain by an example: Let's assume the following fictive URL: abc4braille.com. Following the Norwegian standards for braille conversion, this should be converted into: abc#d<letter sign>braille.com. Because of this way doing it, I think there should be a combrlChangeTable solution. See? > If something in computer braille is too long to fit on a line, the > literary hyphen will be used. This is hard-coded right now. It needs to > be fixed. You are the first to have an issue with it. I'll put it on my > to-do list. Thank you. Lars > On Tue, Mar 29, 2011 at 08:53:36AM +0200, Lars Bj?rndal wrote: >> Hello >> >> I'm going to convert some HTML files into contracted braille, using >> file2brl. In the document, I enclose email and URL strings into < >> > signs. I have two questions here: >> >> 1. How can I ensure that text inbetween <> are uncontracted? (E.g. use a >> different table) >> >> 2. How can I decide whcih character to use to indicate that the address >> have to be devided into two lines? Here we cannot use the normal >> hyphenation -, since this character can be used in the address/URL. Here >> in Norway, we use dot 5 at the end of line. How should that be handled >> when using liblouisutdml? >> >> Best regards, >> Lars For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com