Hi Michael,
Thanks for the reply. At the moment, my problem is not so much how to
interpret the rules. The rules are very fluffy at best, so any
implementation will be an approximate.
Rather, I was looking for a table where something of the kind had been
tried. Also, I was wondering how best to map upper to lower case in
Liblouis. Liblouis already knows the case mapping if the characters have
been defined with the uplow statement.. I guess mapping is being done
internally when translating, but there might be a way to do it explicitly in
a table.
Bue
-----Oprindelig meddelelse-----
Fra: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] På vegne af Michael
Whapples
Sendt: 13. maj 2016 11:31
Til: liblouis-liblouisxml@xxxxxxxxxxxxx
Emne: [liblouis-liblouisxml] Re: Avoiding/removing "unnecessary" marking of
capitals
Regarding automating this, i know that attempts have been done, Duxbury
did have a British Braille no capitals option. How well it worked I
cannot remember as the change in the UK came very early in my Braille
reading time and what I did get had probably been proof read and hand
corrected.
I don't know of any automated system where you could look at the code to
see how it works.
I don't know in Denmark how you deem a capital as essential, but my
memory of in the UK was basically if the capital appeared somewhere when
a capital would not normally appear or when it is part of a name or such
like. I think the main one was not using a capital sign for the
beginning of a sentence, except where that capital is something like a name.
Interesting to see that news item said that the reason that always using
capitals was introduced was to do with things like the wider use of
things like email and web addresses where capitals can be important, my
understanding of the old Braille rules would have been these would have
been places where it is deemed essential and a capital sign would have
been used, so not sure really what it solved on that one as it seems
there was no problem to solve.
However I am neither convinced by the argument it would increase cost,
always using a capital sign does simplify automation as the software
would not need to try and work out if the capital is essential and the
chance it might wrongly identify the situation. I don't have the data to
show what actually happen to cost, it would be interesting to see that.
Michael Whapples
On 13/05/2016 04:11, Susan Jolly wrote:
What you want to do is called Case Mapping. Unicode provides a texthttp://www.independent.co.uk/news/braille-change-angers-blind-readers-117408
file you could use as input to a method that handles the conversion.
http://unicode.org/faq/casemap_charprop.html
However, this capability is built into Java and I would assume other
modern languages. That is, there is a library function that turns an
uppercase letter into its lowercase counterpart and vice versa.
UK English braille used to have a rule similar to what you describe,
caps only used when essential. If there was an algorithm to automate
this, perhaps you could find info on that.
FYI, this a funny article about UK braille readers' reaction to the
change.
Best wishes,
SusanJ
For a description of the software, to download it and links to
project pages go to http://liblouis.org
