jDiction Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

jDiction 2.2.0 released. http://jdiction.org/downloads

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - cliverethman

Pages: [1]
1
General Questions / Re: Translation per sentence
« on: June 21, 2016, 11:09:10 am »
Hello. We have managed to get the translation working, but are having problems with the modules as they are not translating: http://dev.firstdigital.solutions/de/why-omflow. Please advise

2
General Questions / Only module heading translates
« on: June 08, 2016, 03:15:22 pm »
Hi. Just one question with our website only the headings of the Modules content is being translated?  Please advise. Thanks.   

3
General Questions / Re: Translation per sentence
« on: May 31, 2016, 04:52:39 pm »
OK. I'll discuss with the client and come back to you in the next few days.

4
General Questions / Re: Translation per sentence
« on: May 27, 2016, 05:22:41 pm »
How much would you charge?

5
General Questions / Re: Translation per sentence
« on: May 27, 2016, 04:05:10 pm »
Please advise what the solution is for this.  The reason we used jDiction for this project is because it says in the JED and jDiction documentation that XLIFF is supported. If this is not currently the case, then we need to get it working.

6
General Questions / Re: Translation per sentence
« on: May 27, 2016, 03:49:17 pm »
Sorry, I'm not clear on your response - has the plugin been tested with XLIFF?  The documentation states that it works with XLIFF...

7
General Questions / Re: Translation per sentence
« on: May 27, 2016, 03:10:53 pm »
Hi. Thanks for your reply.  Do you know of any XLIFF translation software packages that do support html tags?   

8
General Questions / Re: Translation per sentence
« on: May 27, 2016, 02:20:35 pm »
Thanks for your response - this is what our client says:

"I have the paid version of MemoQ, so that’s not the issue. The problem is that translators work at sentence level. Each translation unit in the XLIFF file should be a single sentence, but they are packaging an entire web page. As I said in the initial query on this, the file should segment (i.e. start a new translation unit) every time it sees certain punctuation i.e. a full stop or colon usually.
 
They say ““Each content article is saved as its own entity in the XLF file“ which seems to suggest there’s a fundamental problem somewhere.
 
If you look at the screen shot below, you can see that “Capabilities” as a heading has segmented as you’d expect, on it’s own row 103 (displayed here in MemoQ) and on the right you can see that MemoQ has been able to match this to the Chinese translation. Below this is the next segment – as you can see it has many sentences concatenated together, meaning the translation tool cannot match the translation against database (it looks for sentences that match, not for entire pages). There should be a new translation unit everywhere the is a full stop or a <br>.
 
Hope this helps illustrate the issue I’m facing."

9
General Questions / Re: Translation per sentence
« on: May 27, 2016, 12:54:55 pm »
Hi Harald. Thanks for your prompt reply. Our client is using MemoQ XLIFF editor.  What he says is:

" I had no problem importing the XLIFF file, from what I can see it is a problem in how the file is generated. You don’t need an XLIFF editor to see this. If you look at the XML in a text editor, then you can see that entire web pages are being packaged as single translation units."

Please let me know your thoughts - should he be using a different editor?

Thanks.

Pages: [1]