Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
What should `translate (join (apple) (banana)) to (<language other than english>)` do?
See original GitHub issueExpected Behavior
Plugging in blocks into translate block with a language other than the viewer’s language selected should translate that phrase into the selected language.
Actual Behavior
This is really a question about what the translate block should do if it fails to translate a phrase.
The following combination of blocks (composed of unchanged blocks found in the toolbox) results in ‘applebanana’ in English.
This feels a little broken, especially since it still translates to a string in English. Maybe this should result in the empty string, indicating that a translation for that phrase in the desired language could not be found.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Just a note on the technical side: “applebanana” is what the translate api returns for that query and many other made up words just return the original as well. If we did want to return the empty string instead, I don’t see any score in the response that we could use to help make that decision.
This is my new favorite example of this 😄
That’s a valid translation of broken in Japanese. A lot of Japanese words are basically English :p