Skip to content
This repository has been archived by the owner on Nov 5, 2018. It is now read-only.

Add support for newer Braillo embossers #54

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 6 comments
Closed

Add support for newer Braillo embossers #54

GoogleCodeExporter opened this issue Mar 14, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

Add support for newer Braillo embossers (300/600/650)

Original issue reported on code.google.com by [email protected] on 16 Jan 2015 at 10:31

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 16 Jan 2015 at 10:31

  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@dkager
Copy link
Contributor

dkager commented Oct 8, 2015

What needs to be done here? Dedicon uses 650SF. I'd like to add the NL (031.01) table at least, but if these machines need anything else w.r.t. volumes or page size I might as well do that too.
CC @bertfrees

@joeha480
Copy link
Collaborator

There hasn't been any progress in testing in two years. A release has been made with these changes. I'll just have to assume that it works. If this is not the case, open a new issue here https://github.com/brailleapps/braille-utils.impl/issues

@bertfrees
Copy link
Contributor

Not two years. There is some more info here: snaekobbi/pipeline-mod-dedicon#5.

@dkager
Copy link
Contributor

dkager commented Sep 20, 2017

We started doing test runs again in August. One result was that Java apparently converts all non-ASCII (0x0..0x127) characters to question marks. So @PaulRambags had to put in some extra magic.

@PaulRambags
Copy link

It turned out that the IBM00858 encoding (CharSet) worked fine, so in the end no "magic" was needed. If you use encodings IBM850 or windows-1252 for the conversion to ASCII, all characters above 0xFF are translated to a '?'.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants