From: Michael M. <ar...@gm...> - 2010-12-14 09:25:03
|
For some inexplicable reason (by me) Thai output from google translate crashes the client I'm working on on windows (Other languages didn't do it, I'm not Thai but I was trying them all). It does not on linux. It could be internal memory related. I check in case it was my client's memory but it didn't crash on other languages with possibly 4-byte output (and it didn't crash on linux). t It's the same behavior on 64 and 32bit binaries of windows. |
From: Sam H. <sa...@ho...> - 2010-12-14 20:18:13
|
On Tue, Dec 14, 2010, Michael Menegakis wrote: > For some inexplicable reason (by me) Thai output from google translate > crashes the client I'm working on on windows (Other languages didn't > do it, I'm not Thai but I was trying them all). It does not on linux. > It could be internal memory related. I check in case it was my > client's memory but it didn't crash on other languages with possibly > 4-byte output (and it didn't crash on linux). t > > It's the same behavior on 64 and 32bit binaries of windows. Could you maybe paste a Thai string that shows the behaviour? Was it using UTF-8? Thanks, -- Sam. |
From: Michael M. <ar...@gm...> - 2010-12-14 23:26:43
|
On Tue, Dec 14, 2010 at 10:18 PM, Sam Hocevar <sa...@ho...> wrote: > On Tue, Dec 14, 2010, Michael Menegakis wrote: >> For some inexplicable reason (by me) Thai output from google translate >> crashes the client I'm working on on windows (Other languages didn't >> do it, I'm not Thai but I was trying them all). It does not on linux. >> It could be internal memory related. I check in case it was my >> client's memory but it didn't crash on other languages with possibly >> 4-byte output (and it didn't crash on linux). t >> >> It's the same behavior on 64 and 32bit binaries of windows. > > Could you maybe paste a Thai string that shows the behaviour? Was it > using UTF-8? > > Thanks, > -- > Sam. Actually, I did manage to crash it even on Linux. Luckily there is readable outcome: \translate Sweden tonight decided to fight a British judge's decision to grant bail to WikiLeaks founder Julian Assange translated: สวีเดนคืนนี้ตัดสินใจที่จะต่อสู้กับการตัดสินใจของผู้พิพากษาของอังกฤษในการให้ประกันตัวเพื่อ WikiLeaks ผู้ก่อตั้ง Julian Assange Program received signal SIGSEGV, Segmentation fault. 0x00007fffbf402bb6 in FTCharmap::GlyphListIndex(unsigned int) () from /usr/lib/libftgl.so.2 (gdb) bt #0 0x00007fffbf402bb6 in FTCharmap::GlyphListIndex(unsigned int) () from /usr/lib/libftgl.so.2 #1 0x00007fffbf4060fd in FTGlyphContainer::Glyph(unsigned int) const () from /usr/lib/libftgl.so.2 #2 0x00007fffbf40cecf in FTFontImpl::CheckGlyph(unsigned int) () from /usr/lib/libftgl.so.2 #3 0x00007fffbf40e126 in FTFontImpl::Render(char const*, int, FTPoint, FTPoint, int) () from /usr/lib/libftgl.so.2 #4 0x00007fffbf413255 in FTTextureFontImpl::Render(char const*, int, FTPoint, FTPoint, int) () from /usr/lib/libftgl.so.2 #5 0x00007fffbf40cd03 in FTFont::Render(char const*, int, FTPoint, FTPoint, int) () from /usr/lib/libftgl.so.2 #6 0x00007fffbf40ed39 in ftglRenderFont () from /usr/lib/libftgl.so.2 #7 0x000000000040eb3f in Unicode_Render () at code/ioq3-urt/ioq3-urt_Unicode.c:238 The 'translated' output is what is FTGL rendered. There's no problem with other UTF output. e.g. On Greek: \translate Sweden tonight decided to fight a British judge's decision to grant bail to WikiLeaks founder Julian Assange translated: Η Σουηδία αποφάσισε απόψε για την καταπολέμηση της απόφασης της βρετανικής δικαστή να χορηγήσει εγγύηση για να ιδρυτή Wikileaks Julian Assange No crash and normal render. PS. I wonder if Thai is 'more bytes' than Greek and I overflow something though I had they impression they are both 4 bytes on UTF-8? (not sure at all though). The font used is the open source LiberationSerif-Regular.ttf though it's unstable also on arial.ttf. |