**From:** Doug Ewell (*doug@ewellic.org*)

**Date:** Tue Mar 08 2011 - 15:25:28 CST

**Previous message:**Ken Whistler: "Re: Assigning a plane for mapping digits for many different bases"**Maybe in reply to:**Tiago Estill de Noronha: "Assigning a plane for mapping digits for many different bases"**Next in thread:**Hans Aberg: "Re: Assigning a plane for mapping digits for many different bases"**Reply:**Hans Aberg: "Re: Assigning a plane for mapping digits for many different bases"**Messages sorted by:**[ date ] [ thread ] [ subject ] [ author ] [ attachment ]**Mail actions:**[ respond to this message ] [ mail a new topic ]

Ken Whistler <kenw at sybase dot com> wrote (converted to plain text):

*> For example, suppose I needed, for some reason, the write the number
*

*> 1927631 (base 10) expressed in base 360. The base 360 digits for that
*

*> are 14, 314, and 191. I could then easily express the number as
*

*> {{14},{314},{191}}_360
*

Or even:

{{14},{314},{191}}₃₆₀

thus further proving that existing Unicode characters, without markup,

are sufficient.

-- Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s

**Next message:**Luke-Jr: "Re: Assigning a plane for mapping digits for many different bases"**Previous message:**Ken Whistler: "Re: Assigning a plane for mapping digits for many different bases"**Maybe in reply to:**Tiago Estill de Noronha: "Assigning a plane for mapping digits for many different bases"**Next in thread:**Hans Aberg: "Re: Assigning a plane for mapping digits for many different bases"**Reply:**Hans Aberg: "Re: Assigning a plane for mapping digits for many different bases"**Messages sorted by:**[ date ] [ thread ] [ subject ] [ author ] [ attachment ]**Mail actions:**[ respond to this message ] [ mail a new topic ]

*
This archive was generated by hypermail 2.1.5
: Tue Mar 08 2011 - 15:28:08 CST
*