Controleer citaten op fouten

Contribute Fout
, ,
1

Just FYI. The proofread breaks quotes. This has that way a while now.

This image depicts a screenshot of a resolution suggestion view in an editing tool, highlighting specific text edits for a post with a quoted section. (Captioned by AI)
This image depicts a screenshot of a resolution suggestion view in an editing tool, highlighting specific text edits for a post with a quoted section. (Captioned by AI)1210×1297 169 KB

2 likes
2

Doesn’t really break the quote, only the preview visualization.

I’d say this, plus the the animated diff we have on the roadmap, means we should move to doing a diff without the cooking part of it.

What do y’all think @awesomerobot @keegan ?

6 likes
3

Just to add to this…

We recently updated Discourse, and from what I recall, the plugin wouldn’t try to proofread quoted text (as it shouldn’t because technically it’s not really quoted anymore if it does).

Below is a screenshot…

The image shows a suggested edit notification for a post in a format where numbers are incorrectly spelled as letters, prompting a correction from "ne-number" to "number." (Captioned by AI)
The image shows a suggested edit notification for a post in a format where numbers are incorrectly spelled as letters, prompting a correction from "ne-number" to "number." (Captioned by AI)1238×1012 78.5 KB

5

@keegan just rolled out a new implementation, the diff is now applied to markdown and streamed :heart_eyes:

It works great for this case and even handles fixing typos in quotes :slight_smile:

The image shows a "Suggested edits" dialog box where a user is commenting on a quote implementation for markdown and streamedstreamed, with options to confirm or discard the change. (Captioned by AI)
The image shows a "Suggested edits" dialog box where a user is commenting on a quote implementation for markdown and streamedstreamed, with options to confirm or discard the change. (Captioned by AI)825×539 63.7 KB

3 likes
6

Ik ben hier omdat ik niet denk dat proeflezen geciteerd materiaal zou moeten corrigeren (het is niet geciteerd als het “gecorrigeerd” is)

Is er een manier om een overstap aan te vragen om geciteerd materiaal niet aan te raken?

Trouwens: Geweldig werk met de recente upgrade en het standaard maken van zoveel plugins, waaronder AI. Ik host zelf en ik moest een paar plugins verwijderen om te upgraden, die standaard waren. (bedankt voor de naadloze ervaring met het behouden van onze emoji’s). Ik ben blij dat iedereen die niet weet hoe plugins toe te voegen nu de volledige ervaring krijgt. Ik heb de AI-ervaring gisteren ingesteld en het is goed.

7

I think we can do something here. It is somewhat tricky cause we need to hoist out content and then re-insert it into the post.

I certainly consider this a bug, will put a pr-welcome on this for now, I may get to it, but it is a bit tricky. The server side needs to partially parse the markdown, remove the quotes, give to proofreader and then add them back in, this may end up resulting in the proofreader getting an incoherent thing to proof read.

Tricky problem.

2 likes
8

We did some prompt engineering, but technically, this is still breaking a quote

image
image771×471 41.7 KB

2 likes
9

Is proofreading quotes actually a real issue :thinking: After all, the error should have been fixed by the quoted user in the first place. Anyway, as long as the AI doesn’t change the context itself — and it does/did make such changes sometimes.

I almost hate to say this out loud, but worrying about changes per se sounds almost like code-based behavior where the most horrible thing that can happen is if x=y changes to x=1 even when the latter one is true too :joy:

But sure. If a quote can stay untouched, just like a code block should be left alone, that would be nice or even great. But is it such a big thing that anybody should use a lot of paid hours to fix it?

Another sure. That is just my opinion and I know there are situations where a quote should be a 1:1 copy.

1 like
10

It can be a problem.. especially if ai makes a mistake with quoted religious texts like pāḡi material and makes a mistake doing it.
Or if the user forgot the special characters (which ai does a nice job of doing), then it really should not fix that, because the quote is the quote . He might lead to a small tangent by misspelling a pāḡč word, but if it is corrected, then it does not justify the rant for his miscommunication due to a spelling mistake.

So, I think it should preserve the quote.. it does not feel right for me to upgrade someone’s quote.

11

This was fixed in

See it here:

image
image716×696 57 KB

If it still doesn’t work for you, try switching to a better model.

1 like
12

Excellent.. I updated earlier today before following up.
I look forward to keeping peoples bad “qotes.” :grinning_face:

13

Testing below for fun:

We use Grok 4 Fast because it is cheap.. but considering we spend 3 Cents per month… We can look at other models if there are problems. We have a slightly custom prompt agent. I’ll test now since we are updated.

14

image
image1132×578 50.6 KB

Any suggestions for ai engines?
We have a custom persona called pali_proofreader

You are a markdown proofreader and a Pāḷi scholar. Fix grammar, Pāḷi diacritic marks, and wrong spellings for a Theravāda discourse discussion website. Correct typos and phrasing issues but keep the user’s original voice. Do not touch quoted blocks (except to remove accidental extra line breaks from copy/paste). Preserve paragraph formatting. If nothing needs fixing, return the text unchanged. Remove unnecessary line breaks, especially from PDF copy/paste. Fix incorrect or missing diacritic marks. Output ONLY the corrected text, with no explanations, no notes, and no commentary.