Since each person’s custom font is different, you’ll have to structure it accordingly. Naturally, it will depend on how you ordered your font.
#BABYLONIAN NUMERALS CONVERTER CODE#
The exact same code can be written for Babylonian, Mayan, Chinese Rod, and Inuit numbers, and all you have to do is change the Chars variable to the corresponding numbers in order. This subroutine will give us any alphanumeric number at any base from 2 to 36. (For my uses, I only need it to reach 36.)Ġ001D’s suggestion to learn the sequence of various numeral types.
Here’s another subroutine that I borrowed and slightly modified the character set (to aide in clarity for the game user), that allows me to input any whole number and find its counterpart of any base from 2 to 64. Since Roman numerals are an odd set, they somewhat don’t correspond to the base x number sets.īasically, almost all other numbers can be expressed by converting them into their base radix and corresponding characters in the custom font. I figured I wouldn’t be using the lower case ever, so this could be an easy way to keep control over my font. My overlined characters are actually represented by their respective lower case counterpart. Typically, most people are not coding for numbers greater than 4000, the point at which characters change from the typical English alphabet to overlined characters. The only think I changed was the construct matrix and ported to C#. This is based on a common subroutine found on the net everywhere. Ultimately, these puzzles will contains thousands and possibly tens-of-thousands of dots and tags having the smallest text will allow me to push the format to the maximum.įuture version of Mega-Dots that randomizes the puzzle by base number. Fifth, making my own fonts allows me to fine-tune the shapes and poche of each character, to ensure the greatest possible legibility in the smallest possible size. Fourth, making my own fonts allows me to avoid any possible copyright issues. Ideally, I would prefer to batch process this, and due to these font changes, the API’s are very amenable to this. Thirdly, once the user’s catalog and related files are updated on that session of CATIA, these esoteric character options literally appear in the pulldown in 3D, assuming the user would ever want to do this manually. This would make the random number puzzle very easy to program in the drafting API’s. The second advantage would be that I would require only one array of font sizes in the drafting catalog, and not one for each esoteric font types. The advantage of using one font to contain not just all my Babylonian numbers, but all the numbers means that I can drop a tag at the appropriate size and modify the text accordingly, without having to jump font types.
2015 0001D LLCīasically, once you automate the CATIA tag, you must design the font type and size at the point of creation, because modifying these things later is not impossible, but doing it on 6227 tags is effectively impossible. You cannot just insert a tag on a dot, and then retroactively adjust the size and type. First, in CATIA, when you employ text tags, you need to establish a catalog of fonts and sizes that you anticipate your client (in this case, me) to use. The advantages of making my own number font were enormous. Maybe there is a trick to getting them to render in CATIA, Illustrator, and/or Photoshop, (or any web browser), but rather than wasting any more time on that R&D, I figured just designing my own font would be the best course of action. However, whenever I tried to use them in any application other than WordPad or Microsoft Word, the characters appeared as blank. I downloaded the standard Babylonian character types and installed them as they directed.
#BABYLONIAN NUMERALS CONVERTER WINDOWS#
I really tried to use the expanded Windows characters. Maybe I can show you some of my tricks when I programmed the Mega-Dots connect-the-dots puzzles.Īlmost from the start, I ran into annoying problems.
2015 0001D LLCĪncient or uncommon number systems can be a fun, but tricky to work with when coding.
0 kommentar(er)
