From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/3] stkutil: display text attributes as html
Date: Thu, 01 Jul 2010 16:15:35 -0500 [thread overview]
Message-ID: <4C2D0577.5070708@gmail.com> (raw)
In-Reply-To: <20100701135459.40411dad@kcaccard-MOBL3>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
On 07/01/2010 03:54 PM, Kristen Carlson Accardi wrote:
> On Thu, 01 Jul 2010 13:54:16 -0500
> Denis Kenzior <denkenz@gmail.com> wrote:
>
>> Hi Kristen,
>>
>> On 07/01/2010 01:29 PM, Kristen Carlson Accardi wrote:
>>> On Thu, 01 Jul 2010 11:30:07 -0500
>>> Denis Kenzior <denkenz@gmail.com> wrote:
>>>
>>>>
>>>>> + start = attrs[i++];
>>>>> + len = attrs[i++];
>>>>> + code = attrs[i++];
>>>>
>>>> You might want to be extra paranoid here that attrs_len is a multiple of 4.
>>>
>>> attrs_len does not have to be a multiple of 4. I will add a sanity
>>> check to attrs_len to make sure it is at least >= i + 3.
>>>
>>
>> Then this code is incorrect, as it handles len 3 attrs only at the end
>> of the array. Also please note that SIM Toolkit Text Attributes are
>> always coded on 4 bytes (see 102.223 Section 8.72 for details). You
>> might want to assume 4 byte alignment or invent a data structure for
>> these attributes.
>
> I should have said that attrs_len does not always have to be a multiple
> of 4 -- it is allowed to only have 3 byte attrs as the last attribute,
> so the code is correct. However, since not all attributes are
> required to be of len 4, we can't just assume attrs_len is a multiple
> of 4.
>
How do you figure this? From 23.040 Section 9.2.3.24.10.1.1 Text Formatting
"Octet 4
This Octet may be omitted by setting the IED length accordingly."
From 102.223 Section 8.72:
"The Text Formatting is a sequence of one or several Text Formatting
items, each coded on 4 bytes.
The Text Formatting scheme used is the same as the Text Formatting
defined in TS 123 040 [27]."
So you either have to support a mixed 3 & 4 byte fields or you assume
all fields are 4 bytes.
Regards,
-Denis
next prev parent reply other threads:[~2010-07-01 21:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 11:22 [PATCH 0/3] html text attribute patches Kristen Carlson Accardi
2010-06-29 11:22 ` [PATCH 1/3] stkutil: display text attributes as html Kristen Carlson Accardi
2010-07-01 16:30 ` Denis Kenzior
2010-07-01 18:29 ` Kristen Carlson Accardi
2010-07-01 18:54 ` Denis Kenzior
2010-07-01 20:54 ` Kristen Carlson Accardi
2010-07-01 21:15 ` Denis Kenzior [this message]
2010-07-01 22:56 ` Kristen Carlson Accardi
2010-07-01 23:08 ` Denis Kenzior
2010-07-01 23:05 ` Kristen Carlson Accardi
2010-07-01 23:47 ` Denis Kenzior
2010-07-01 22:10 ` Andrzej Zaborowski
2010-07-01 22:35 ` Denis Kenzior
2010-07-01 22:47 ` Andrzej Zaborowski
2010-07-01 22:50 ` Denis Kenzior
2010-06-29 11:22 ` [PATCH 2/3] test-stkutil: add unit test for html text attributes Kristen Carlson Accardi
2010-06-29 11:22 ` [PATCH 3/3] test-stkutil: add html attribute test for Display Text tests Kristen Carlson Accardi
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=4C2D0577.5070708@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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