[mitsubishi]

^ the noise issue should now be fixed [edit: er, misunderstood, by volume you mean amount, hehe). I tried the server but nobody's talking but I doubt I can reproduce it that way. Ideally it'd need a debugger (gdb) where it happens.

This post has been edited by mitsubishi: 06 December 2010 - 10:00 AM

[mitsubishi]

The very latest version [just uploaded] has further cleanups/small bug fixes on GoogleTranslate multithreading which may make it more stable, however, I wouldn't expect miracles and I keep suspecting system bugs.

Also dmaHD noise issue is properly fixed by the author of dmaHD, psychorunner. It may not be apparent in hearing since it was also workarounded here clumsily.

--

I'd like to hear more about the google translation issue if it happens. Hardware/software info etc.





--

Hrm. I may be able to make cURL not be multithreaded for Google Translate hence rulling out related issues completely.

This post has been edited by mitsubishi: 06 December 2010 - 05:38 PM

[mitsubishi]

Google Translation support is now COMPLETELY REWRITTEN. Please let me know if the behavior is different now.

--

It avoids using pthreads hence it's not multithreaded.

However, it may be better technologically. It uses a "multi connection" API of cURL which makes it possible to keep alive connections for later use for easing networking and it doesn't lock for fetching either.

--

It's not polished yet, but it appears to be fine at first glance.

--

A much more Polished version is now uploaded. It operates correctly after a dropped connection to the internet and it actually keeps in memory at least 16 messages in case of the translation server being slow for a while (default is changeable in the source).

This was definitely a good architectural decision. It offers much better control, recycling of connections and it's actually faster.

--

I got confimation from one of the guys with the problem that it's fixed.

weeeeeeeeeeee

This post has been edited by mitsubishi: 08 December 2010 - 08:34 PM

[mitsubishi]

Semi-Important on libcurl and translation on linux. To avoid it blocking the client when it first resolves the google domain, libcurl has to be compiled with c-ares support.

Funny is that this issue is identified on Ubuntu for other projects too and it will be included on their next update of libcurl.

One can of course use their own build of cURL to avoid it sooner.

[PyroBor]

I am compiling your exe now. And I have one question. Do we need ftgl have installed on system?
Also it fails to compile for me (ioq3-1803-urt-141210)...

I get compile error without ftgl installed:

make[2]: Entering directory `/usr/src/ioq3-1803'
CC code/ioq3-urt/ioq3-urt_FTGL.c
code/ioq3-urt/ioq3-urt_FTGL.c:13:24: warning: FTGL/ftgl.h: No such file or directory
In file included from code/ioq3-urt/ioq3-urt_FTGL.c:15:
code/ioq3-urt/ioq3-urt_FTGL.h:4: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.h:5: error: expected ')' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.h:6: error: expected ')' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.h:7: error: expected ')' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.c:17: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.c:34: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.c:35: error: expected ')' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.c:36: error: expected ')' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.c:37: error: expected ')' before '*' token
code/ioq3-urt/ioq3-urt_FTGL.c: In function 'FTGL_Init':
code/ioq3-urt/ioq3-urt_FTGL.c:83: error: 'qftglCreateTextureFont' undeclared (first use in this function)
code/ioq3-urt/ioq3-urt_FTGL.c:83: error: (Each undeclared identifier is reported only once
code/ioq3-urt/ioq3-urt_FTGL.c:83: error: for each function it appears in.)
code/ioq3-urt/ioq3-urt_FTGL.c:84: error: 'qftglSetFontFaceSize' undeclared (first use in this function)
code/ioq3-urt/ioq3-urt_FTGL.c:85: error: 'qftglRenderFont' undeclared (first use in this function)
code/ioq3-urt/ioq3-urt_FTGL.c:86: error: 'qftglDestroyFont' undeclared (first use in this function)
make[2]: *** [build/release-linux-x86_64/client/ioq3-urt_FTGL.o] Error 1
make[2]: Leaving directory `/usr/src/ioq3-1803'
make[1]: *** [targets] Error 2
make[1]: Leaving directory `/usr/src/ioq3-1803'
make: *** [release] Error 2

And this error after I installed ftgl (2.1.3-rc5):

make[2]: Entering directory `/usr/src/ioq3-1803'
CC code/ioq3-urt/ioq3-urt_FTGL.c
In file included from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/ftgl.h:33:10: error: #include expects "FILENAME" or <FILENAME>
/usr/include/FTGL/ftgl.h:34:10: error: #include expects "FILENAME" or <FILENAME>
/usr/include/FTGL/ftgl.h:35:10: error: #include expects "FILENAME" or <FILENAME>
In file included from /usr/include/FTGL/ftgl.h:114,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTGlyph.h:196: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ftglGetGlyphError'
In file included from /usr/include/FTGL/ftgl.h:115,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTBitmapGlyph.h:77: error: expected ')' before 'glyph'
In file included from /usr/include/FTGL/ftgl.h:117,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTExtrdGlyph.h:97: error: expected ')' before 'glyph'
In file included from /usr/include/FTGL/ftgl.h:118,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTOutlineGlyph.h:88: error: expected ')' before 'glyph'
In file included from /usr/include/FTGL/ftgl.h:119,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTPixmapGlyph.h:77: error: expected ')' before 'glyph'
In file included from /usr/include/FTGL/ftgl.h:120,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTPolyGlyph.h:92: error: expected ')' before 'glyph'
In file included from /usr/include/FTGL/ftgl.h:121,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTTextureGlyph.h:92: error: expected ')' before 'glyph'
In file included from /usr/include/FTGL/ftgl.h:123,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTFont.h:411: error: expected ')' before 'void'
/usr/include/FTGL/FTFont.h:451: error: expected declaration specifiers or '...' before 'FT_Encoding'
/usr/include/FTGL/FTFont.h:467: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
/usr/include/FTGL/FTFont.h:579: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ftglGetFontError'
In file included from /usr/include/FTGL/ftgl.h:132,
                 from code/ioq3-urt/ioq3-urt_FTGL.c:13:
/usr/include/FTGL/FTLayout.h:187: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ftglGetLayoutError'
make[2]: *** [build/release-linux-x86_64/client/ioq3-urt_FTGL.o] Error 1
make[2]: Leaving directory `/usr/src/ioq3-1803'
make[1]: *** [targets] Error 2
make[1]: Leaving directory `/usr/src/ioq3-1803'
make: *** [release] Error 2

This is all after applying patch from ioq3-1803-urt-141210-git.tar.lzma to ioq3 svn source revision 1803.

[mitsubishi]

Ah yes, for the second error make a symlink of /usr/include/freetype2/freetype/ to /usr/local/include (it also needs freetype).

It's a bug of freetype installations according to this page http://ubuntuforums....d.php?t=1396493

This post has been edited by mitsubishi: 15 December 2010 - 10:46 AM

[mitsubishi]

You can also disable the feature completely and not require FTGL by disabling Freetype with the Makefile, but, you'd need the latest source now uploaded which allows it.

--

Updated with fixes.

--

Update involving unicode translation output only printing final translations and dropping translations that the input is same with output language.

also /Unicode_Shadow

This post has been edited by mitsubishi: 15 December 2010 - 07:17 PM

[mitsubishi]

Has any of you had any stability issues again with the latest version? It returned to a threaded version of translation though again re-written but I still worry in case it was a generic issue with threads and the engine there.

[PyroBor]

Well I tried 1803-191210 and it didn't have any stability problems. But I disabled freetype before I compile it. (If that matters)

I think you can completely remove that msg about writing that "in" language is the same as "out".

[mitsubishi]

Nice. The main issue was with translation, unicode is single-threaded.

Yeah, I think it should be posted only once or twice. [edit: done, it's only spammed once]

This post has been edited by mitsubishi: 19 December 2010 - 06:53 PM