Run-time warning about translations

I get this warning: cutelyst.core[warning] Can not load translations from not existing directory: "/usr/share/cutelyst2/translations"

There is nothing installed into /usr/share/cutelyst2 the folder does not exist. I do not see any dependencies I have missed.

I found this in the issues for cutelyst: [https://github.com/cutelyst/cutelyst/pull/103/commits/6ee6b4610d9d81b1c37b5bdadc158ae3b39fd5b1]

set (I18NDIR "${DATADIR}/cutelyst${PROJECT_VERSION_MAJOR}/translations" CACHE PATH "Directory to install translations")

if DATADIR=/usr/share that would explain the call; so how do I fix I see a reference to transifex, but can not figure out the warning; is there a way to get this to work?

That is a mention to Cutelyst translations, which doesn't exists ATM, you can safely ignore.

A feature to come I take it; gotcha; I think I know where you are going with it; you need a Translation Server; and most of them Cost Money, transifex is not cheap; and I also know how to build a System like this; but it requires a third Party App that does the Local Translation on the Server; it basically translates the language files; I wrote mine in Bash; at first it used Google; til that was not free anymore; then I used other services; eventually none of them are free now; there are solutions I have not looked into like Zanata, OpenNMT, and many others; and there is an Option that I found helpful and that is Google Translate; it is easy to add to a Template, I use it at my website; not sure how good it works; since I only look at it in English, but its a cheap option; I have tired to use local translation with Moses; its complex to setup documents; and you have to read in each word one at time and hope it does not get taken out of context; you can translate a string of words at the same time; I just mean one line at a time form the Translation file; because that is all I work with; all my text comes from those files; you can not feed it a translation file; you have to loop through and look up each key pair in that file, and then save it to a language specific file; but it can be done for free; you just have to find a service that stays free; they all start out that way; then you do like I have done and waist your time working on API's that can do this job; but maybe on a limited bases based on how many words a day; another method is one I though of but never wrote; it uses the Google Translate button to translate the site; using a bash call I would call each page using a different language; and I would put id's in every html tag; so I could use it to parse the html and create a bash translation file for each language; not as crazy as it sounds; but you have to have ID tags for all your html tags; and they must be unique; and they must match the Qt Language files, you could do this in C++ a lot faster; you could put a button in the back end to update the files; its called Brute Force Translation; you can also just write a single page that outputs every word in your Qt Language file or files if you cat them; if you do you have to check for unique keys, and using the key as an ID; and creating the language files from the key value; it would be much faster in terms of Translating a site with more then one page; and it give you a page to check out all your translations on; and you can make sure its only seen in the back end; so it uses Google Free Translator like the one at my site; to translate all your Qt Language files that you post to a Page you created for this very reason; so you can loop through all the Languages you will support; and create all the Language files; and keep in mind you may need to restart the app for those setting to be read in; I do not know if Qt Reads those files on the fly or caches them; you would have to know, and only have to test it to find out; hope this helps; I wrote a system for the Government in a Language called ADA, and it used a Proprietary Translation system; it was assume though; it could also update all the comments made in Source Code; it was part of the Versioning System they used to store Source Code; and it required multiple languages to be maintained in the Source Code; because the code was written for use overseas; so each comment had a default id to ensure that is the one translated; if you update a comment; all you had to do was make that Comment default and it would translate the others; it also had a validation service to validate every translation; so it took it to levels you might not even think about doing.