Unnecessary spacing after referencing glossary terms. How to fix?

Questions
, ,
1

When referencing something from the glossary using either #citation or @XXX, there is automatically a space after the reference even when there isn’t one in the editor. This is fine typically as there is meant to be a space before the next word of course but when I am wanting to finish the sentence or add a comma it adds a space after the reference which I don’t want.

I am using glossarium for the glossary.

This paper explores the use of regressive machine learning models to perform prognostics in @bev:pl.

I.e it should be Battery Electric Vehicles (BEV).

But it appears as

… Battery Electric Vehicles (BEV) .

image
image784×160 26.6 KB

(First post so not sure if the formatting is correct)

2

Hello,
This is a bug in glossarium 0.5.4. This will be fixed in the next release. It is fixed by this commit.

1 Like
3

Thank you for the response @quachpas

Is there an easy way I can fix this myself now or switch to that branch / commit?

It’s for my dissertation due next Monday so would like to sort it by then.

Another question I had that you might know the answer to.

I’m using a .bib file for my bibliography in Harvard format which results in (Name, date) i.e (Chen et Al., 2018) however I believe the proper format when using it at the start of the sentence would be Chen et Al. (2018) states…

Is there a way I can manually override it for this use case or is it easier to just do the reference manually?

4

You can download the files directly and import from that. Or replace your local files if you are not using the webapp.

For your 2nd question, I think you should try different citation styles.

5

Ah that’s great.

I’ll take a look!

6

FYI for all

Form is what I was looking for turns out. form: “prose” fixes the issue.

2 Likes
7

I’ve tried importing the files into the project folder (web app) and then importing from there however it’s still causing the issue for me

8

If you still have problems with the fixed version of the package, please open a new Questions topic.

Also, please read how to write inline and block code correctly from

You were not using backticks for inline code, and for code block it was single quotes instead of backticks. A moderator fixed your message, because new users only can edit posts within 24 hours time period after posting.

1 Like