https://bugs.documentfoundation.org/show_bug.cgi?id=170092

--- Comment #7 from BDF <[email protected]> ---
(In reply to Siarhei Kuchuk from comment #0)
> [...]
>
> LibreOffice is free, but it does not offer possibilities to work faster for
> workers.
>
> [...]
>
> Can you please consider add following features (i ordered them from most
> important):
> 
> - Text summarization
> - Content generation/drafting
> - Translation
> - Grammar and spelling correction
> - Writing style improvement
> - Paraphrasing and rewriting
> - Tone adjustment
> - Research assistance
> - Citation and reference formatting
> - Outlining and structuring
> - Data analysis and insights from text
> - Table and chart generation
> - Fact-checking
> - Readability analysis
> - SEO optimization
> - Accessibility suggestions
> - Autocomplete and predictive text
> - Template creation
> - Document comparison
> - Transcription and speech-to-text
> - Text-to-speech narration
> - Formatting assistance
> - Image generation from descriptions
> - Content extraction from images/PDFs
>
> [...]
>
> Expected Results:
> Performance boost of workers and writers. Currently world is not imaginable
> without writing reports in 1 minute instead of hour with great formatting.
> 

  As said on the design talk: IMO we shouldn't outright reject AI or AI tools
just because there is a (large?) counter movement to AI adoption.

  Some features sound like a good fit for a tool or an AI tool for LibreOffice
(eg. Grammar and spelling correction, Template creation (assistant), Research
assistance (regarding managing quoting sources and not to do 'original
research'), Table and chart generation (is this really an AI?)), but I'm not
sure if they are really what we see as "AI" right now (which usually is just an
LLM that also has the capability to create image and video slop - Shrimp Writer
anyone?).
  Some features sound like they are not within the project scope of LibreOffice
after all (Text summarization, Content generation (other than typing yourself),
Tone adjustment, Paraphrasing and rewriting, Fact-checking (very touchy subject
- what is a 'fact' in a world of alternative facts and "fake news"?), Tone
adjustment, Image generation from descriptions (LO is not Photoshop/GIMP or a
camera)).

  The problem I see is that current technology is not nearly as perfect as it
needs to be for the demanding jobs that are listed in the quoted comment
listed. Just recently I gave ChatGPT a document to find certain parts of it and
it just hallucinated stuff that wasn't even in the document after all.
  If LibreOffice includes any AI tool (be it a simple or complex one) it *has*
to work, which is just not possible with the current tools and their error
margin IMO.

  When I take a look at my workplace, AI wouldn't give me a big performance
boost at all. As my output *has* to be accurate, I would have to babysit an LLM
output anyway to make sure it does not start hallucinating and write somewhere
something about Mecha-Hitler or spread CSAM (looking at you, Grok!). Therefore
there would be no performance boost to gain for me with a tool like this.
Though I acknowledge that for other users there might be a performance boost to
gain.

  As AI is heavily criticized around the internet (from stealing the creative
work of others over resource usage and problematic outputs) I do not think TDF
or LibreOffice has to be in a pole position regarding AI adoption. Not to
mention that even the smartest minds and billions of dollars are not getting
rid of hallucinations at the moment.
  Furthermore such a tool should be Opt-In by default or LibreOffice will get
the touch to be yet another app that forces AI down your throat. Therefore the
(already existing) extensions are a good start and a good place as test and
proving ground. 

  IMHO the limited resources and limited development time of (the not billion
dollar company) TDF are better spend on other projects that have a more
tangible output with a lower aversion factor (like fixing existing bugs that
crash the application).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to