Default font is different for guest on joining collaboration session.

[shaansubbaiah]

Edit (11th Aug 2020) : Reported bug to Abiword

https://bugzilla.abisource.com/show_bug.cgi?id=13934

---

Different font (here -> Nimbus Roman) is set as default when a user joins a public/collaborative Write Activity session.

Found on: Sugar 117-3, Debian 10.4 Buster

Reproduce: Join a collaborative Write activity session. A different font is seen only in the guest user, not in the shared activity's host.

Screenshot:

---

@Saumya-Mishra9129 reported Serif as the default in the guest user; packaged Sugar in Ubuntu 20.04

The font differs in different systems.

[quozl]

A more fundamental problem is that the text differs. It should be the same. Until the text is the same, I wouldn't worry about the font not being the same.

[shaansubbaiah]

@quozl, testing the Write Activity in Sugar 0.117-3, Debian Bullseye I found something similar:

While moving an image, the font switches to one that is not listed in Sugar by default. The font set is one that Abiword picks by default.

This was reproducible on Sugar Live Build as well, Dejavu Serif was selected as default.

Using the minimal Abiword python snippet you had provided earlier, I was able to reproduce this issue. What I did:
Start the minimal Abiword instance -> Change the font to something other than the default -> paste an image -> type -> font is reverted to the default.

That was an Abiword issue. I'm assuming that even this issue, #43, is due to Abiword. I don't know how to confirm this. Perhaps we can call a function to change the font when the user connects to a shared session?

---

Edit: Dragging an image outside the page (extreme left/ right) crashes the Activity. This is also an Abiword issue, tested on the Sugar Live Build and minimal Abiword instance.

With all these issues, might it be better to use a newer version of Abiword?

[quozl]

With any issue that can be reproduced using the minimal AbiWord pyhon snippet, you should use the AbiWord bug tracker. It is fine to keep an issue open in this repository, provided a link is made to the AbiWord bug. 3.0.4 is the latest release of AbiWord. You haven't mentioned here what version you are using.

[shaansubbaiah]

Sorry I didn't see this earlier, I'm running Abiword 3.0.4, Sugar 0.117-3, Debian Bullseye.

This looks somewhat similar https://bugzilla.abisource.com/show_bug.cgi?id=8201, doesn't seem fixed.

[quozl]

https://bugzilla.abisource.com/show_bug.cgi?id=8201 doesn't seem anything to do with the issue. Are you sure you got the right bug number?

[shaansubbaiah]

The earlier link I sent was wrong, I had meant to share https://bugzilla.abisource.com/show_bug.cgi?id=9451
I cannot find the exact bugs we are facing (perhaps my search terms are way off), but there are some similarities with this bug report.

Do I open bugs for the issues we are facing? (Crashing when resizing table cells, moving images to the horizontal edges, etc)

[quozl]

For any issue that can be reproduced using the minimal AbiWord python snippet, you should use the AbiWord bug tracker; either find an existing open bug that accurately and succinctly describes the problem, or if there is no such bug open new one. And, if possible, fix the bug. That's the role of an open source developer; to fix everything everywhere. The alternative is horrible; never using any dependencies.

[shaansubbaiah]

Just to clarify, the opened bug should come under pyAbiword? Selection of v3.0.4 is only available for the AbiWord product and not the pyAbiWord product.

[quozl]

I don't know. You should ask the AbiWord project about that. It is not unusual for bug trackers to not have the most recent version selectable, as adding the new version is a step that must be taken during a complex release process ... but again, that's not an issue that Sugar Labs can help with.

[shaansubbaiah]

Thanks, will do 👍

[shaansubbaiah]

Reported the bug to AbiWord, added link to the top.