Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 4

Qt-interest Archive, March 2002
Unicode-Row, Cell-help


Message 1 in thread


<<< text/html: EXCLUDED >>>


Message 2 in thread

Thanks for spending time to help me, John.

Reading qt-interest: posting I came across the following.
  You can do:
     QChar ch ...;
     ushort unicode_bigendian = (ch.row << 8 | ch.cell);
Is the first byte cell and the second row?

Searching for structure or enum I found the following in QChar header file.
// Not the non-const ones of these.
 uchar cell() const { return s.constref(p).cell(); }
 uchar row() const { return s.constref(p).row(); }

But, did not really tell me how QChar is made of.

Again, thanks.
Myint
----- Original Message -----
From: "John F. Dumas" <jdumas@locutus.kingwoodcable.com>
To: "Shwe Myint" <PeguNC-01@carolina.rr.com>
Sent: Sunday, March 10, 2002 11:20 AM
Subject: Re: Unicode-Row, Cell-help


> On Sun, 10 Mar 2002, Shwe Myint wrote:
>
> > Hi! All geneous,
> >
> > Will some one direct me to documents that has row and col related to
QChar or
> > get me started on this?
> >
> > Thanks,
> > Myint
>
>    Can't really follow your question but when I'm looking for help with
> respect to unicode it's typically this document:
>
>    http://www.unicode.org/charts/PDF/U4E00.pdf
>
>    that I'm looking for ;-)
>
> //***********************************************************************
> //  John F. Dumas                           Contract Software Developer
> //  5311 Jasper Grove     Unix, Win32, Web - C/C++, Java, CGI Scripting
> //  Kingwood TX, 77345      jdumas[at]locutus[dot]kingwoodcable[dot]com
> //  (281)-360-5290                    http://locutus.kingwoodcable.com/
> //***********************************************************************
>


Message 3 in thread

Thanks John.

I will hunt for that U4E00.pdf and study further.
What ever you explained is great help for me. Appreciated very much.
I repost this for some one like me to benefit from yours.
Take care abd brgds.
Myint
----- Original Message -----
From: "John F. Dumas" <jdumas@locutus.kingwoodcable.com>
To: "Shwe Myint" <PeguNC-01@carolina.rr.com>
Sent: Sunday, March 10, 2002 11:00 PM
Subject: Re: Unicode-Row, Cell-help


> On Sun, 10 Mar 2002, Shwe Myint wrote:
>
> > Thanks for spending time to help me, John.
> >
> > Reading qt-interest: posting I came across the following.
> >   You can do:
> >      QChar ch ...;
> >      ushort unicode_bigendian = (ch.row << 8 | ch.cell);
> > Is the first byte cell and the second row?
> >
> > Searching for structure or enum I found the following in QChar header
file.
> > // Not the non-const ones of these.
> >  uchar cell() const { return s.constref(p).cell(); }
> >  uchar row() const { return s.constref(p).row(); }
> >
> > But, did not really tell me how QChar is made of.
> >
> > Again, thanks.
> > Myint
>
>    Ah, ok - I follow you now.  From what you posted it *looks* like
> 'row' just means 'most significant byte' and 'cell' means 'least
significant
> byte'.  Like for example, a QChar with a value of 1000 would have a
> most significant byte of '3' and a least significant byte of '232',
> in other words:
>
>    1000 = (3 << 8) | (232)
>
>    So (based upon what you show above) the 'row' would be '3' and the
> 'cell' would be '232' but as far as unicode goes I've personally never
> seen it expressed (broken down) this way, it's always just one 16-bit
> number.  I suppose it sort of makes sense, in that document I referred
> to (that U4E00.pdf) things are shown in a sort of row/column way ... like
> it'll have a table like this:
>
>    4E0 4E1 4E2 4E3 ...
> 0   x   x   x   x
> 1   x   x   x   x
> 2   x   x   x   x
> 3   x   x   x   x
> 4   x   x   x   x
> ...
>
> but it really isn't the same, '4E0' represents 12 bits whereas the
vertical
> annotation (0, 1, 2, 3 ...) is just a nibble (4 bits) rather than a whole
> byte like you were showing in your row/cell stuff above.  I'm wondering
> if row/cell is just the names Trolltech has chosen to give for "most
> significant byte" and "least significant byte" and they are just terms
> of the trolls' own devising.  I dunno, does any of this help?
>
> //***********************************************************************
> //  John F. Dumas                           Contract Software Developer
> //  5311 Jasper Grove     Unix, Win32, Web - C/C++, Java, CGI Scripting
> //  Kingwood TX, 77345      jdumas[at]locutus[dot]kingwoodcable[dot]com
> //  (281)-360-5290                    http://locutus.kingwoodcable.com/
> //***********************************************************************
>