Closed gembree closed 10 years ago
What versione Of rainbow are you using? Release 1.0? This should have been fixed in the development build.
Yes. I confirm that the latest development version can handle this image flawessly. Just download the dev version from the front page https://github.com/marco-calautti/Rainbow. The problem was that Rainbow always quantized the image, even if it was not needed. Now, if the imported image does not exceed the maximum number of colors, no color reduction is applied. However, if it contains too much colors, then it will apply color reduction. In the event that the final color-reduced image is not ok for your needs, then it will be better to reduce the number of colors during the editing phase. Beware that the new version has the XML format radically changed. So, you will need to re-export your tim2 into xml before reimporting it. Let me know if I can set this issue as solved ;).
Thanks for your prompt attention! I don't have a compiler set up right now so I'll wait until the next release, but I'll take your word for it. I can go ahead and move on with my project knowing the font will look better later.
Please mark this as solved; if there's still a problem, it probably qualifies as a separate issue.
The dev build is available as compiled binary already. You can find the linkin the front page. Just read the first lines of the Readme ;).
Dunno how I missed that (I looked three or four times)! Thanks again - great utility.
Great tool!
Rainbow seems to be unnecessarily shrinking the palette of images when I convert them. An example image goes from 16 colors to 10 simply by being exported and imported from TIM2 > XML/PNG > TIM2. Possibly this is optimization that's useful in most cases, or possibly it's because this is an anti-aliased font and the different colors are just different levels of alpha, but whatever the reason it seems undesirable in this case.
I've uploaded an image with the issue. https://dl.dropboxusercontent.com/u/4580484/font_1.tm2