-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ronna- and Quetta- #569
Comments
So far as I know, robi and quebi has not yet been approved by any international standards organization. Conversion from phonewords is supported in the |
Thank you for the reply, Hanna. Perhaps the binary prefixes for those most recently added units will be added with time, as it is logical to do so. I don’t know how long the timespan was between the establishment of the informational units and the adoption of the current binary-prefixed set. I also found that the American Radio Relay League must be a bit “behind the curve.” I found that the abbreviation “KiW [a logical kibiwatt] was pronounced “Q.” I didn’t necessarily expect to hear it pronounced as “kibiwatt.” But, I figured that, since it was only for fun, why not give it a try? After all, it was unexpected to hear binary-prefixed unit abbreviations read properly (at least, up to yobi-). Oh, and, according to Daffy Duck, Bugs Bunny is despicable. <https://www.youtube.com/watch?v=ndriWJJYirs> 🤣 Bugs would also like to point out [when Wile E. Coyote introduces himself as “Mud”] that mud spelled backwards is dum[b] <https://www.youtube.com/watch?v=Vl1uFDiDoQc> . 🤣 Regarding the phone word thing, I was unaware that it was supported. You might have mentioned it to me before; however, if you had, I had forgotten it. I performed a test of Daisy and Hanna and, indeed, 32,479 and 42,662, respectively, were returned. These would be expected unless one’s dial pad is extremely unusual. Although, in my history of looking at those, generally the only characters that I have seen changed are Q, Z, and space. Q and Z are, most commonly, on the 7 key and the 9 key, respectively, with the space character on the 0 key. However, some have the Q and Z on the 0 key and the space on the pound (or, perhaps, star). In rare cases, these characters are removed completely. Although I didn’t “design” phone dial pads, I used to spend some of my spare time using Microsoft Excel (or, at least once, Microsoft Visio) to “design” computer keyboards. A test of the string “This is a test.” showed that spaces and “miscellaneous symbols” (such as punctuation marks or diacritical marks) are currently ignored. Generally, the space character would be on the 0 key. As such, I know that I have generally used the digit 0 for those. “Miscellaneous symbols” are commonly accessed by pressing the 1 key (at least, in text messaging with older phones [such as some of Motorola's early Razr phones]). As such, in the rare case that I am working with a string including punctuation, the digit 1 would be used. As such, the string: “This message is intended for the inbox of Hanna Knutsson only.” would have a long “phone number” of 8,447,063,772,430,470,468,363,330,367,084,304,627,806,304,266,205,688,776,606,659. For diacritical marks, I was initially thinking that the 1 key was used. However, further “thinking it over” suggested that that is probably an incorrect memory (as I haven’t historically used them much on flip phones). Also, it seems only logical that a given diacritic mark would use the same key as the letter to which it is applied, which I think is how it works. As such, the letter é, for example, would be “an extension” of E, and, thus, accessed by pressing the 3 key. As such, those characters would use the same digits as the Latin or English letters that don’t use them. At least you have a starting point. That is the first step of any process. This is where you hope that you fall victim to the jingle for Pringles—“One you ‘pop,’ you ‘can’t’ stop!” Now that you have it started, keep going to completion. Although, as you indirectly mention, what is “completion” for that function exactly? I suppose that, for conversion of raw strings (such as a person’s name) to telephone digits, a dictionary would not be needed. However, going the other way (converting a numeric input to a phone word) would require some sort of referential point. For example: Conversion of the name Daisy is simple—32,479. However, what about if the inputs are reversed? 32,479 could be either daisy or dairy. Unless some sort of “dictionary” was used, conversion from numeric to alphabetic input would probably not work as expected because the calculator would not know the intended characters used or the order in which they are intended to appear—especially if “miscellaneous symbols” (such as a trademark sign or a registered trademark sign), punctuation, or diacritical marks are intended to be part of the text. Have a wonderful day and, in case I didn’t mention it before (because I don’t remember if I did), happy New Year to you, Hanna!
From: Hanna Knutsson ***@***.***>
Sent: Friday, 3 January, 2025 2:07
To: Qalculate/qalculate-gtk ***@***.***>
Cc: WeirdOddWodd ***@***.***>; Author ***@***.***>
Subject: Re: [Qalculate/qalculate-gtk] Ronna- and Quetta- (Issue #569)
So far as I know, robi and quebi has not yet been approved by any international standards organization.
Conversion from phonewords is supported in the base function. Use "phoneword" or 4 as the third argument, e.g. base(TEST, 10, phoneword) = 8378. Conversion to phoneword is more problematic as I assume that a dictionary is required for useful output.
—
Reply to this email directly, view it on GitHub <#569 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMK6JPWTD23OITWO3XKQ5AL2IZAJFAVCNFSM6AAAAABULMG6OWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRYHAZDKMJWG4> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AMK6JPTBMDHEG3XVTV6SI2L2IZAJFA5CNFSM6AAAAABULMG6OWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUZDUUU6.gif> Message ID: < ***@***.***> ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hanna,
I don’t have any issues other than that, it seemed that the e-mail address I was using to contact you previously might be defunct (since the message remained in my outbox for longer than expected). Today, I [very shockingly] discovered that a text-to-speech engine that I use to convert text documents to audio files reads binary-prefixed units (such as the gibibyte). It was also shocking to discover that Qalculate! includes the most recently added prefixes (ronna- and quetta-). Another shocking discovery was that robi- and quebi- (the logical binary equivalents of ronna- and quetta-) aren’t present in the set (even in Wikipedia’s list, from whence your list in Qalculate! might be derived). You have done amazing work on Qalculate! and I look forward to future developments of the project. It would still be nice if it had a phone word (or similar) function that took text strings and converted them to phone dial pad digits or vice versa and if there was a version for Android (and, perhaps, iOS, although I don’t use any iOS devices). But, you might still be working on those and simply haven’t yet released them because you are doing more thorough testing to ensure accuracy and minimal presence (and, preferably, the absence) of bugs. I suppose that, if you did release a version for Android, it probably wouldn’t start out as sophisticated as the version for Windows. Have a wonderful day!
The text was updated successfully, but these errors were encountered: