Re: Bibletime encoding problem
On Sat, Sep 6, 2014 at 7:17 AM, Johann Spies <johann.spies@gmail.com> wrote:
>
> On 5 September 2014 15:01, Joel Rees <joel.rees@gmail.com> wrote:
>>
>> ouch.
>>
>> > bibletime-data - Documentation and data for bibletime, a bible study
>> > tool
>> > does that not help thou?
>>
>> Doth it help thee not?
>>
>> Mmmm, no, that isn't quite right. Punt:
>>
>> Art thou not holpen thereby?
>>
>> Mayhap, hadst thou shown the incurred error message thou mightest
>> be helped forthwith.
>>
>> :)
>
> Grapjas! :)
Dankie. En jy is welkom. (Courtesy translate.google.com . ;)
> No error messages.
>
> Just output like this:
>
> �� p�� 1 01� 2 x �͒ 3 �d� 4 x �͒ 5 x �͒ 6 ��� 7 x �͒ 8 x �͒ 9 x �͒ 10 x �͒
> 11 x �͒ 12 x �͒ 13 14 x �͒ 15 x �͒ 16 x �͒ 17 x �͒ 18 x �͒ 19 � 20 x �͒ 21 x
> �͒ 22 x �͒ 23 о� 24 x �͒ 25 x �͒ 26 x �͒ 27 x �͒ 28 x �͒ 29 x �͒ 30 x �͒ 31
> x �͒
Have you checked the logs? (I'm always forgetting to do that, myself.)
What I would do is open a shell window, bring up some garbled output
in bibletime, and then do
ls -lart /var/log
to see if it generated any log messages. Then, assuming
"something.log" comes up in the right time frame, use
tail -40 /var/log/something.log
or maybe even tail -400 to go far enough back. If you switch to a
virtual console rather than use a terminal app, you'll need to pipe
through more or less:
tail -400 /var/log/something.log | less
Some of the logs will require you to raise privileges:
sudo tail -400 /var/log/messages
> If you can read that, wonderful!
Well, no, you're going to have to capture the text before the
substitution takes place and send it in a plaintext mail instead of
html/rich text if you want me to try to read it. If you are on a
tablet, don't use google's mail app from the playstore. You'll need a
mail app that can send the text plain. (At least, I haven't found a
way to send plaintext from that.)
The things I'd do to try to read it -- first, I'd try to get it into a
file. Unfortunately, most text editors are too helpful these days, so
you'll end up doing something like
tr \n \n > garbled.text
then paste the garbled text in and hit ctrl-d to end it. If what you
get in garbled.text looks exactly like what you pasted in, the
substitution had already occurred by the time you got it copied. You
can check with hexdump:
hexdump -C garbled.text | less
and if you see a lot of "ef bf bd" sequences, that's the Unicode
substitution character and your copy is definitely too late.
If garbled.text looks like it might actually contain some text you're
trying to look at, you can try opening it with a unicode-aware text
editor like gedit. Usually, you have to get a blank document up, then
use the file-open menu to open the file, but remember to select the
assumed encoding, UTF-8 or one of the legacy encodings, before you hit
the open button. You'll likely need to add encodings to the dialog, as
well, to get your legacy encoding into the list of selectable
encodings.
You may have to delete an octet or two from the front to get started.
(cut command in a shell, redirecting to garbled2.text or something so
you don't lose what you're trying to work with.)
> You apparently did not read my email properly:)
Well, I assume that Chris was wondering whether you had read, for example,
http://www.bibletime.info/en/about/frequently-asked-questions
and, say, the installation and tutorial sections of
https://sites.google.com/site/bibledit/
> Enjoy your day.
Bibletime is not really what I'd call end-user. Very much a work in
progress, a tool for translators who are willing to put up with some
rough edges. It can be used for reading and research, but it's more in
the line of a tool for collaboration. (Which isn't a bad thing,
really, but you have to expect a bit of a learning curve.)
(And if I want a Japanese translation of the Bible available for it,
it looks like I'm going to be the one setting the project up and
leading/doing the translation, and negotiating with the JBS.)
> Regards
> Johann
>
> --
> Because experiencing your loyal love is better than life itself,
> my lips will praise you. (Psalm 63:3)
--
Joel Rees
Be careful where you see conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Reply to: