Allow unsupported languages for api > since llm probably supports them

[christopherpickering]

Instead of giving

{
	"error": "tk is not supported"
}

for unsupported languages, what about just allowing them when using the api? Its easier than expanding the language file for every language, and the llm probably supports them :)

example query for Turkmen:

{
		"q": "good morning sir",
		"source": "en",
		"target": "tk",
		"format": "text",
		"api_key": ""
	}

I did try adding to the languages file, rebuilding, and running, and that works no problem... but it would be cool not to need to modify the source when pulling the latest :)

Its pretty cool, thanks!

[pierotofy]

Mm, yes, I thought about this for a bit, but I wouldn't want a language which is not supported to be listed.

I think it should be easy enough to just add support for a new language by adding it to the source?

[christopherpickering]

Yeah, it depends how you run it I guess - somewhat publicly or for yourself. Maybe a flag to disable the protection? Pretty low priority tho 😀