From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: how to calculate the size of string in bytes?
Date: Tue, 18 Aug 2015 03:43:44 -0700 (PDT) [thread overview]
Message-ID: <a21841a8-350e-4f7c-8fad-b906daf787d6@googlegroups.com> (raw)
In-Reply-To: <mailman.8504.1439892841.904.help-gnu-emacs@gnu.org>
On Tuesday, 18 August 2015 11:14:04 UTC+1, to...@tuxteam.de wrote:
> On Tue, Aug 18, 2015 at 02:11:54AM -0700, Sam Halliday wrote:
> > We used to have a 6 character hex number at the start of each message that counted the number of multibyte characters, but we'd like to change it to be the number of bytes in the message.
> >
> > We're sending the string to `process-send-string' and `read'ing from the associated network buffer. But when calculating the outgoing length of the string that we want to send, we use `length' --- but we need this to be `length-in-bytes' not the number of multibyte chars. Is there a built in function to do this or am I going to have to iterate the string and count the byte size of each character?
> >
> > A quick test shows that
> >
> > (length (encode-coding-string "EURO" 'raw-text))
> >
> > seems to give the correct result (1 for ASCII, 2 for Pound Sterling, 3 for Euro), but I am not 100% sure if this is correct.
>
> Raw is, afaik, Emacs's internal coding system. You don't want traces of it
> in the network :-)
We're not sending the message using raw, we're using UTF-8. But I need to calculate the length of the UTF-8 string IN BYTES as part of the payload (each messages begins with a 6 character hex encoding of the proceeding string's raw length).
I'm using "raw" to calculate an approximation of the UTF-8 string's byte length, but I am aware that it might not actually be true in the general case :-/
I don't think what you've suggested would actually change the semantics, but it would allow us to use a different encoding on the wire than the encoding of the string. We don't really need to worry about that at this stage, because all our users are using UTF-8. We'll keep it in mind though.
next prev parent reply other threads:[~2015-08-18 10:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 9:11 how to calculate the size of string in bytes? Sam Halliday
2015-08-18 10:13 ` tomas
2015-08-18 14:37 ` Eli Zaretskii
2015-08-18 14:45 ` tomas
2015-08-18 15:00 ` Eli Zaretskii
2015-08-18 16:01 ` tomas
2015-08-18 16:35 ` Eli Zaretskii
2015-08-18 19:30 ` tomas
2015-08-18 19:49 ` Eli Zaretskii
2015-08-18 20:11 ` tomas
2015-08-18 21:47 ` Stefan Monnier
2015-08-19 5:43 ` tomas
[not found] ` <mailman.8577.1439934462.904.help-gnu-emacs@gnu.org>
2015-08-19 8:57 ` Sam Halliday
2015-08-19 9:22 ` Sam Halliday
2015-08-19 19:47 ` Stefan Monnier
[not found] ` <mailman.8504.1439892841.904.help-gnu-emacs@gnu.org>
2015-08-18 10:43 ` Sam Halliday [this message]
2015-08-18 11:47 ` tomas
[not found] ` <mailman.8510.1439898432.904.help-gnu-emacs@gnu.org>
2015-08-18 12:06 ` Sam Halliday
2015-08-18 14:34 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a21841a8-350e-4f7c-8fad-b906daf787d6@googlegroups.com \
--to=sam.halliday@gmail.com \
--cc=help-gnu-emacs@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).