Announcement: Trouble with the custom language.
903 0 9
X
Reading Options
Font Size
A- 15px A+
Width
Reset
X
Table of Contents
Loading... please wait.

So, I made an announcement in the 3 story showcase series, but it doesn't look like as many people follow that one so I will be repeating it here.

First off, I am still working on the series that I will be posting. I have not forgotten about it or you guys even though there are no delivered results yet.

I was actually planning on launching Key to the Void today in fact, but fate seems to have decided to give me a nasty slap in the face over my decision to evolve a dead language as the basis for my Elven language. I had been using a translation dictionary called Glosbe until recently. It had a very nice function on it where if it did not have the exact translation, it would at least offer something close which you could check with back-translations in order to be sure it was close enough to the meaning you wanted.

I had formed the spine of my Elven language as I started this, but there were a few key words that were missing. ("Need" and "too much" being two key terms that are being a pain in the rear right now.) However, when I went on to Glosbe today in order to find a suitable word to then modify in some way, it suddenly stopped giving "close enough" translations and wouldn't translate anything unless it had an exact match. For a dead language like the one I'm using for this project, that's pretty much death to my efforts.

So, for now, my plan is to go back to writing chapters for "A New Hero God" until either Glosbe fixes it's translation functions or someone can recommend me a new Sumerian - English dictionary that can help me serve the same purpose. If I don't have one option or the other realized in a week, I will likely re-write the chapter I was working on to have the Elven language speaking portions hand-waved over as "words that couldn't be understood." I feel it would harm the integrity of the writing, but I also want to get something out there.

9