@roosterburton Mmm, strange! I have the latest version 5.3.19 (iOS). It could be that it only applies to translations from Japanese (which is the one causing problems), or it could be because in my case, it only translates to a single language (English), not two like in your case (English and Spanish). The difference in the Japanese to English translation results is significant!
Hi srdurden,
We attempted to reproduce this issue, and donโt see it happening any more. Is it possible that this bug was temporary and that newly imported lessons donโt have this issue?
North
@nsprung I have copied the example text with issues (which I wrote above) into a .txt file, imported it as a lesson and as I suspected, it continues to fail.
Has the team tried it?
Sometimes I feel like providing information about bugs in lingq is pointless; it seems like no one reads or pays attention. Has anyone reviewed what I mentioned about the blue translation button in the edit sentence mode?
The example of text giving problems:
ใใๅบใใใใชใใใใใ ใใ่ใใใ็ฟไธใใใใใชใใจ่จใใใฆใใ
ใใใใใๅบงใฃใฆใชโฆโฆใใใซใใฆใๅงใกใใใ็ธๅคใใใๅฃฐใๅฐใใใชใใ
ใใจใๆตใฎ่จ่ใใใใใใใณใผใใผไปฃใใซใฆใณใฟใผใฎไธใซๆฎใใฆ
ใ ไบ็พๅญใฏๆใใ้ ญใใใใฆๆฐใซ่ใ่ฟใใใใๆฐใฏๅฐใใปใปใใใงใใชใใใใ ใใ ใฃใใ
ใ้ก่ฒใใใใใชใใญใใใใใใใชใใงใใชใใฎใใใ็ญใใฆใใใๆขๅญใฏใตใจใๅฒ้ใใใฃใใใใ่
นใใใใใใใจใๆใๅบใใฆใใกใใฃใจๅฟ้
ใซใชใฃใใ
ใใใใๆไธใซใคใใฆ่กใใใจใใใจใๆไธใฎๆฏใใใใใใๅฃฐใใใใใ
ใ ใใใใใชใใใใใใใใใๅฐใใใฎใ่ฆใใจใไฝใใใใใใฎใใใใใใผใใฎใใใธ่กใใใใๆใผใใใชใใใใ
ใใ ใใฉใใณใใผใฎใซใใใใใใใใใๅๅญใฎใใใ ใใจใใพใๆใใใฎๅฅณใฏใใคใใใๆใใฎใ ใ
ใใใใๆฅใฆใใใชใใฆใใๅผใใงใใใใฐใใคใใฟใใใซๅฎถใพใง้ใณใซ่กใฃใใฎใซใใใใใฎใใใฎใไปๆฅใฏใๅงใกใใใจใใฃใใ่ฉฑใใใใฃใใใโฆใ้ช้ญใใใชใใฃใ๏ผ
@nsprung @zoran How is this issue?
Iโm trying to summarize it in a single post in case it can help with the problem resolution.
Problem: Translations from Japanese to English are experiencing intermittent malfunctions. These errors occur in both the web version and the iOS version. When a user imports a new Japanese lesson and requests the translation of a sentence on the sentence mode screen, one of these errors (or a combination of them) often occurs:
- A loading wheel appears and the translation never loads.
- It translates a text unrelated to the requested translation.
- It adds invented text fragments.
- It translates only a part of the sentence.
These errors happen much more frequently when there are Japanese brackets (ใใ) in the sentence to be translated.
Possible solutions: Lingq already has a solution implemented and it is available in the iOS version, but it is โhiddenโ in another part of the application. This solution resolves all the previously mentioned problems. In iOS, when a user clicks to edit a sentence that had no translation, a blue icon appears. By clicking on the blue icon, a new (and more accurate) translation is generated. Can you incorporate this solution into the sentence view?
How to test: By creating a lesson that collects some of the reported errors, you can replicate the problem. At the end of this message, I will copy some sentences that can be saved in a .txt file and imported into Lingq as if it were an ebook.
Screenshots: Example of poorly translated text in the sentence view. It is text from a private lesson generated after importing an ebook that didnโt have translations previously.
If I click in โShow translationโ (and being a lesson recently imported for which there are no translations) a new translation is requested. The translation generated is incorrect (it has nothing to do with the original text).
However, if you edit the sentence:
โฆdelete the translation and request the translation again (the blue button on the image from the sentence editing):
The generated translation is now correct:
Finally, you can use copy this lines into a .txt file, import as a new lesson and test if the solution is correct.
ใใๅบใใใใชใใใใใ ใใ่ใใใ็ฟไธใใใใใชใใจ่จใใใฆใใ
ใใใใใๅบงใฃใฆใชโฆโฆใใใซใใฆใๅงใกใใใ็ธๅคใใใๅฃฐใๅฐใใใชใใ
ใใจใๆตใฎ่จ่ใใใใใใใณใผใใผไปฃใใซใฆใณใฟใผใฎไธใซๆฎใใฆ
ใ ไบ็พๅญใฏๆใใ้ ญใใใใฆๆฐใซ่ใ่ฟใใใใๆฐใฏๅฐใใปใปใใใงใใชใใใใ ใใ ใฃใใ
ใ้ก่ฒใใใใใชใใญใใใใใใใชใใงใใชใใฎใใใ็ญใใฆใใใๆขๅญใฏใตใจใๅฒ้ใใใฃใใใใ่
นใใใใใใใจใๆใๅบใใฆใใกใใฃใจๅฟ้
ใซใชใฃใใ
ใใใใๆไธใซใคใใฆ่กใใใจใใใจใๆไธใฎๆฏใใใใใใๅฃฐใใใใใ
ใ ใใใใใชใใใใใใใใใๅฐใใใฎใ่ฆใใจใไฝใใใใใใฎใใใใใใผใใฎใใใธ่กใใใใๆใผใใใชใใใใ
ใใ ใใฉใใณใใผใฎใซใใใใใใใใใๅๅญใฎใใใ ใใจใใพใๆใใใฎๅฅณใฏใใคใใใๆใใฎใ ใ
ใใใใๆฅใฆใใใชใใฆใใๅผใใงใใใใฐใใคใใฟใใใซๅฎถใพใง้ใณใซ่กใฃใใฎใซใใใใใฎใใใฎใไปๆฅใฏใๅงใกใใใจใใฃใใ่ฉฑใใใใฃใใใโฆใ้ช้ญใใใชใใฃใ๏ผ
Hi @srdurden,
We donโt have an update for you yet on this matter. I have made a note and will post here when we have more news for you. Please expect a reply from me by the end of the Friday.
I followed the instructions and was able to find at least one sentence that was poorly translated That being said, it seems like the Japanese brackets are used haphhazardly in the example text - the text starts with a ใwhich seems odds, as well as has brackets inside brackets which might easily cause issues. DeepL also has issues translating this text because of this.
Are you able to provide an example text that is a bit more standard? If we can prove Japanesebrackets almost always cause issues, even when used in simple situations (i.e. localized into of a single sentence), then we have something specific we can work on fixing.
@nsprung All the sentences have been cut in this way by the Linq importer, which usually cut brackets incorrectly. All of them are real lingq examples.
However, for me to understand, could you provide me with the reasons why the alternative translation method cannot be used? It works correctly and doesnโt cut or omit part of the sentences. For example, today I came across the sentence:
้ง่ปๅ ดใฎ้ ใๆกๅคงใใ็ฒใ็ปๅใ ใฃใใใฉใๅคงไบบใซ้ใๅใใฆใใใฌใญใฏใ่จใใใฆใฟใใฐใๅใซไผผใฆใใชใๆฏใใใพใๅธใใชใใ
That LinqQ had imported correctly (itโs the last sentence of a dialogue). In the standard translation (and in Deepl website itself), it doesnโt translate the text after the bracket, while the alternative method (the sentence editor view one) has translated it correctly and includes the final sentence:
It was a grainy zoomed-in image of the corner of the parking lot, but if you ask me, the kid pointing the gun at the adult looked a lot like you.โ I couldnโt breathe properly.
Could you explain to me why itโs not possible to apply this solution?
This happens to me in other languages but invariably it says โretrieved fromโ or just has the word I am translating show up.
I can confirm that Lingq creates broken up sentences that start with ใoften. Most of the time it is even just a lone ใall by itself. Of course the text isnโt actually like that, itโs just how Lingq cuts it up. IMO there absolutely is some sort of issue with that and worth investigating.
@nsprung @zoran could you please answer my question? I would like to understand it so I can help if possible.
I have reduced the problem to a file (with a .txt extension) that can be imported and consistently fails. It contains three sentences: one sentence that gets stuck and doesnโt translate, one sentence with parentheses (ใใ) that translates incorrectly, and one sentence with square brackets ใใ that also translates incorrectly. These are real sentences that I found in novels I imported into LingQ and all of them failed when I tried to translate them.
You can copy these 3 lines into a text file and import it to conduct the tests yourselves:
ใใชใผใใใใๅญใกใใใใใฃใใใชใใตใใๅบใใใใชใใใใใ ใใ่ใใใ็ฟไธใใใใใชใใจ่จใใใฆใใใฉใใใใใผใผใ้ฝ่ใใใไธๅฎใใชๅฃฐใๅบใใๅใฏ็ฌ้กใไฝใฃใฆ่จใใ
ใๆๆฐใฎๆ ๅ ฑใ็ขบ่ชใใใใ ใกใซๅฝใๅฎใ่กๅใใจใฃใฆใใ ใใใผใผใใ้ขๆฑ็ฒไฟกๅฐๆนใไธญๅฟใซใๆชๆใ้ใใฆใๆดป็บใช้จ้ฒใใใใ็ถใใฆใใใผใผใใๅญฃ็ฏๅคใใฎใใฎๆฅๆฟใชๆฐๆธฉไฝไธใฏใไฝๅใฎใชใๆนใซใจใฃใฆใฏๅฑ้บใชใฌใใซใงใใใ
ใใใใใๆฅใฆใใใชใใฆใใๅผใใงใใใใฐใใคใใฟใใใซๅฎถใพใง้ใณใซ่กใฃใใฎใซใใใใใฎใใใฎใไปๆฅใฏใๅงใกใใใจใใฃใใ่ฉฑใใใใฃใใใโฆใ้ช้ญใใใชใใฃใ๏ผใใจๆญๅใฎๅฃฐใไธใใใ
Additionally, I have created three lessons for you to review. The lessons are private (I understand that the team can access them); if itโs necessary to make them public, please let me know.
In the first lesson, I used the standard translation button, and youโll see that the translations donโt make sense:
In the following lesson, with the same input text, I used the blue translation button (hidden in the sentence editor). You will see that all the translations are correct:
And finally, I have left one lesson imported without any translations in case you want to run any tests:
You can find the three lessons in this (private) course:
Finally, reiterate my question: The problem is already implemented in LingQ and works correctly (with the blue button in the sentence editor). Could you explain to me why itโs not possible to apply this solution in the sentence view?
1 Like
Read for an hour last night with lots of trouble. Shown here for proof that this is still broken regardless of how the sentence begins.
This is so frustrating. Please help us 
I saw the conversation and understand that they donโt really care about the issue after more than one month and all the job done by srdurden 
Anyway, please do something guys.
Sorry, in english itโs โIโm too lazy to get out of bedโ.
Absolutely not the same as google translate. The idea of the sentence is there, but the translation is wrong.
@nsprung @zoran Please, can you give me an answer or at least confirm that the team is working on it? Thank you
@srdurden We are still working on this, I will update you as soon as I know more. Iโm sorry for the delay.
Are there really very many texts that take this form? The example given seems to involve multiple quotations in a single sentence, some with puncutation (full stops) inside the brackets. This is causing our software some issues, and Iโm not certain it will be simple to fix as we need a solution that can be applied in many different situations without causing further issues. Are there many courses in the Library that exhibit these issues? @srdurden
Are there really very many texts that take this form?
Yes, itโs very common and appears in any Japanese novel.
This is causing our software some issues, and Iโm not certain it will be simple to fix as we need a solution that can be applied in many different situations without causing further issues.
How did you solve it in the hidden blue button? What issues does it have in other languages? It consistently works well for Japanese to English translations in Lingq without issues.
If youโre worried about a change affecting everyone, canโt you make a setting that Japanese learners could optionally enable that would cause it to behave differently? That way the alternative translation effort could be tested over time just with people who want to be involved.
Of course I donโt understand how all the code actually works behind the scene, but as a dev myself, Iโm increasingly surprised and worried that there is so much caution and resistance towards a fix.
I get that with so many languages and features to take care of, itโs complicated. Thereโs got to be a way though, and yes it is absolutely worth it because these bugs are horrible and embarrassing for the product.
Youโve got multiple people just in this one thread pleading for help. Imagine how many people are constantly frustrated by these bugs.
LingQ primarily uses Deepl for the translation of sentences. The Deepl seems to have issues with translating some Japanese sentences, mostly with brackets, so actually, the bugs with the incorrect (or absent) translations are related to the third-party service.
The LingQ team is currently working on a possibility of a more accurate translation which will be based on GPT and will take into account the whole lesson context for the translation.
1 Like