From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: lm_sensors2/prog/detect sensors-detect
Date: Thu, 19 May 2005 06:24:02 +0000 [thread overview]
Message-ID: <20030627232231.7b652edc.khali@linux-fr.org> (raw)
In-Reply-To: <20021107235845.0037e195.khali@linux-fr.org>
> > Anyway, I'm stumped. I was expecting your system to return UTF-8
> > chars from /dev/ports, and it doesn't seem so (or why would perl say
> > they are malformed?) And if it returns regular chars, why are the
> > values different from the ones obtained with a non-UTF-8 locale? I
> > just don't understand.
>
> This could be a bug in Perl and their partial UTF8 hack
Could be... But there is one last thing I would like to try. My changes
(-k3) don't seem to have had any effect, so I'm trying something similar
but different. Please get:
http://www.ensicaen.ismra.fr/~delvare/sensors-detect-k4
and tell me, again, it it behaves differently with and without an UTF-8
locale.
Thanks a lot for your precious help.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 lm_sensors2/prog/detect sensors-detect Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
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=20030627232231.7b652edc.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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.