From: Till Kamppeter <till.kamppeter@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Contributing braille embosser support
Date: Sat, 12 Dec 2015 09:53:49 -0200 [thread overview]
Message-ID: <566C0ACD.2040305@gmail.com> (raw)
In-Reply-To: <20151212083605.GX2764@var.home>
Thanks, the problems I mentioned are solved by the patches, but the new
fr-braille.po file has some problems (output of cupstestppd):
**FAIL** Bad UTF-8 "fr" translation string for option Edge.
**FAIL** Bad UTF-8 "fr" translation string for option
IndexFirmwareVersio
n.
**FAIL** Bad UTF-8 "fr" translation string for option
IndexFirmwareVersio
n, choice 102000.
**FAIL** Bad UTF-8 "fr" translation string for option
IndexFirmwareVersio
n, choice 103000.
**FAIL** Bad UTF-8 "fr" translation string for option
IndexTable, choice
1.
**FAIL** Bad UTF-8 "fr" translation string for option
IndexTable, choice
2.
**FAIL** Bad UTF-8 "fr" translation string for option
IndexTable, choice
3.
**FAIL** Bad UTF-8 "fr" translation string for option
IndexTable, choice 4.
Can you fix that?
Till
On 12/12/2015 06:36 AM, Samuel Thibault wrote:
> Actually they could even be merged, that'd be better since otherwise
> there would be a lot of duplication. I have attached the resulting
> merge.
>
[...]
>> - The Generic embosser PPD file passes cupstestppd, the files for the Index
>> printers not. The error message is:
>>
>> **FAIL** Multiple occurrences of option IndexTable choice name 24.
>>
>> and indeed the option "IndexTable" has two choices with "24" as short name.
>
> Oops... I must admit I didn't test polish & dutch braille since I speak
> them and don't have an index4 device :) I have attached a patch.
>
next prev parent reply other threads:[~2015-12-12 11:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 10:27 [Printing-architecture] Contributing braille embosser support Samuel Thibault
2015-12-09 16:04 ` Michael Sweet
2015-12-10 20:29 ` Till Kamppeter
2015-12-10 20:45 ` Samuel Thibault
2015-12-10 21:02 ` Till Kamppeter
2015-12-10 21:31 ` Samuel Thibault
2015-12-11 0:19 ` Till Kamppeter
2015-12-11 0:31 ` Samuel Thibault
2015-12-11 1:17 ` Till Kamppeter
2015-12-12 2:28 ` Till Kamppeter
2015-12-12 3:53 ` Till Kamppeter
2015-12-12 8:36 ` Samuel Thibault
2015-12-12 9:50 ` Samuel Thibault
2015-12-12 11:53 ` Till Kamppeter [this message]
2015-12-12 12:04 ` Till Kamppeter
2015-12-13 2:40 ` Samuel Thibault
2015-12-13 11:07 ` Till Kamppeter
2015-12-21 0:11 ` Samuel Thibault
2015-12-21 0:12 ` Samuel Thibault
2015-12-21 13:56 ` Till Kamppeter
2015-12-13 18:59 ` Samuel Thibault
2015-12-13 19:42 ` Till Kamppeter
2015-12-12 15:00 ` Till Kamppeter
2016-11-27 18:54 ` Samuel Thibault
2016-11-27 19:22 ` Till Kamppeter
2016-11-29 19:30 ` Samuel Thibault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566C0ACD.2040305@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=samuel.thibault@ens-lyon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.