Use SDL_ttf to display texts

[petitlapin]

Linked to:

• [Idea] Handle utf-8 in keyboard for highscore input #16 (having utf-8 scores)
• better translation workflow #36 (i18n handling)

This is the first step to have an i18n sustainable project.
If we want to keep the initial fonts (we would need to find them...), I would suggest to have a map of fonts in screen.cc (key being the locale, value being the TTF_Font) and have a unique entrypoint to display texts in this class (so no more display text directly from sprites.cc).

We can cache most of the generated texts (all that are static and won't change during the game) and delete them whenever we change locale.

A first step could be to display the copyright at the bottom of the main screen () and move on with the other texts. Note that we would "temporary" lose the translations for all the other languages so ideally, we should not release a version until we have a clean way to handle all the existing translations...

[zabidenhtf]

Also, im have idea. Main game font will be comic sans (Because when im played first time in Ri-Li game, im selected russian translation, and in russian version all is in comic sans font, and also its look nice)

[zabidenhtf]

Started work, now im replace all on string (because text in ri-li's engine is just a simple image)

[zabidenhtf]

This looks more better

[zabidenhtf]

Yep, im rewrite DrawString, and now it WORK YAY

[petitlapin]

Just to be sure, I'm seeing in the first screenshot you are using DrawString? This is not the way to go because it won't handle correctly utf-8 languages.
I've started a first version in https://github.com/petitlapin/Li-Ri/tree/work/sdl_ttf to go the correct direction.
The new method Ec.PrintText taking a std::string as parameter should replace all the other calls. Note that I didn't handle correctly the placing of the text and removed the previous ones.

Can I let you continue this way starting on this branch?

[zabidenhtf]

Yes, sure, im can continue this branch :D

[petitlapin]

great, I would suggest for you to open a PR once you have managed to display cleanly one text or two so I can review (and to ensure it's going on the right direction and you don't lose time on a solution that will not work), would it be fine with you?
Because I guess you put some effort on the current version you have but I don't want to waste your time on something that will not get merged.

Also, a bit aside, I'm not sure on how much you use an AI assistant, but I would personally recommend you to only use it for the minimal task because if you rely too much on it, you will not learn yourself and you will not be able to think by yourself. I prefer to have it done by a human, even if it takes more time because at least you will learn something :).

[zabidenhtf]

zabidenhtf@abb3e9c

[zabidenhtf]

Here is fully working TTF fonts support

[zabidenhtf]

In this commit now more stuff uses ttf (BUT IT CAN BE LAGGY IM FIX IT) zabidenhtf@9cc0e40

[petitlapin]

zabidenhtf@abb3e9c

Sorry, I noticed I forgot to push screen.h. It is laggy because you don't destroy the structure you create, this was this part of code you removed: f882355#diff-22ae5e91ac372a6cf9330ed9db87890dfbb6cfd5e6effe1fad53c4c3ed4bb20fR66-R86

[petitlapin]

Also please don't use TTF_RenderText_Solid, it does not render the utf-8 characters (just try text with Cyrillic letters for example, that's why I add a é in the initial commit, to check if it was well displayed)

[zabidenhtf]

Ok, sure, I'm fix my errors

[zabidenhtf]

Fixed, now it dont lag, and it can render UTF-8 symbols