[BROWSER REQUEST] Take line breaks into account when user inputs multiple definitions


Sometimes, I input words that have multiple definitions and I use line breaks so that they are appear one on top of the other as shown below.
Def 1
Def 2
Def 3

The Android app does a very good job of respecting the line breaks in the vocabulary list in sentence mode.

However, the browser version of the glossary doesn’t respect these line breaks at all and definitions are crammed next to each other, which gives something like this:
Def 1 Def 2 Def 3

This not only looks messy, but makes definitions difficult to read for the user.

Can you address this issue so line breaks are taken into account in the browser version of the glossary as well? Thanks.


many times I need to write the meaning in a notepad program and then copy/paste it in lingq if I need to have elements in different lines. Would be better to do it directly in lingq. Is about this you are talking?

And by the way, what is this window at the right side of your screen?

1 Like

What I mean is that when I press Shift + Enter to have elements on different lines, the glossary in sentence mode doesn’t reproduce the hard return (on web only), so all definitions are crammed together on one line only. I don’t think you need to use the notepad to have your definitions on two lines. Shift + Enter will do the trick.

This window on the right side of my screen is the Edge sidebar. You can add any website you want and I always have my favourite dictionary open next to the text on Lingq. I find it easier to copy/paste definitions from it that the pop up window. It’s basically like having your phone next to your computer screen.

1 Like

Thanks for your feedback and suggestion. I’ll forward this to our team and we will see what we can do.

1 Like

Any news on that front Zoran?
This issue is really problematic for Lingqs with more than one definition as every meaning ends up crammed onto one line.

I noticed line breaks were added to sentence notes after users reported the problem, so I hope the same will be done for Lingqs.

I’ll check with our team where do we stand with this.

1 Like

Thanks. Much appreciated.

Zoran, a number of your parsing issues could probably be addressed by integrated generative AI where you simply ask the AI to reformat text to some guidelines within the pipeline of the parsing process. While not the most advanced use of generative AI, cleaning stuff up with some degree of intelligence is quite often within the tech’s sweet spot. I’m not saying to use generative AI to replace anything but instead just to augment what you already have. Consider exploring.

Any news from the team on that front Zoran? Thanks.

In the next update, we should have this improved. Our team is on it.

1 Like

@zoran Any news from the developers Zoran? Nothing has changed at all in the last few updates. Thanks.

No updates here yet, sorry. I’ll post here when I hear back.

@SeoulMate I checked this with our team and we won’t be making any changes there. You will need to just use semi colons or commas to separate. This change would cause other issues in the app and at the moment we are unable to make any changes there.

zoran, in general, consider using generative AI for smarter parsing and formatting.

Even consider it for post-dictionary-based learning of vocabulary. Generative AI is really good at helping with register, appropriate usages, inappropriate usages, contextualized meaning, regional usage differences, idioms, and more about words that has never been present in dictionaries derived from their paper-based ancestors.

Exactly, but I guess they are reluctant to touch anything now given the bugs that occur whenever there is a new update.

We might have to wait until Lingq 6.0 to see more AI integration and better parsing.

1 Like

Here’s our vocab of the day. I note that Wikipedia has this article in 17 languages!


I don’t mind a period without new bugs to be honest. If only was true. This morning all my dictionaries disappeared again!

1 Like