LibreOffice Writer

Writer 是 LibreOffice办公套件中的文字处理器应用。(Writer is a word processor app in the LibreOffice Office suite.)

  • Owner: LibreOffice/core
  • Platform: Linux, Mac, Windows
  • License:: GNU General Public License v3.0
  • Category::
  • Topic:
  • Like:
    2
      Compare:

Github stars Tracking Chart

Writer 是 LibreOffice办公套件中的文字处理器应用。

编辑各种文件

Writer拥有您需要的所有功能,包括现代的全功能文字处理和桌面排版工具。这对于快速备忘录来说非常简单,但功能强大,足以创建包含内容,图表,索引等的完整书籍。你可以自由地专注于你的信息,而Writer使它看起来很棒。

只需点击几下即可获得无可挑剔的文档

使用LibreOffice制作时,您的文档看起来比以往更好。您可以选择并应用计算机上的字体,并为文档的几乎每个部分设置和自定义样式。使用自动更正字典,您可以动态捕获拼写错误和拼写错误。自动更正词典会在您键入时检查您的拼写(如果您愿意,可以轻松停用)。如果您需要在文档中使用不同的语言,Writer也可以处理它。

LibreOffice可以帮助您完成整个文档

向导在制作标准文件(如信件,传真,议程和会议记录)方面不遗余力,并且可以完成邮件合并等更复杂任务的简短工作。使用自动完成功能更有效地键入,可以使用内置字典和扫描打开的文档来建议常用的单词和短语来完成您开始输入的内容。文档模板默认发布 -- 不需要创建复杂的文档,因为我们已经为您构建了它们!

Main metrics

Overview
Name With OwnerLibreOffice/core
Primary LanguageC++
Program languageShell, Perl, Makefile, C++, Java, Python, Objective-C, Visual Basic, Assembly, HTML (Language Count: 38)
PlatformLinux, Mac, Windows
License:GNU General Public License v3.0
所有者活动
Created At2013-10-31 15:46:52
Pushed At2025-04-27 14:57:13
Last Commit At2025-04-27 09:35:37
Release Count1652
Last Release Namelibreoffice-25.2.3.2 (Posted on 2025-04-24 20:38:27)
First Release Nametesting_libreoffice-3.3.99.4-hotfixes1 (Posted on 2011-05-06 16:44:21)
用户参与
Stargazers Count3.1k
Watchers Count95
Fork Count679
Commits Count505.8k
Has Issues Enabled
Issues Count0
Issue Open Count0
Pull Requests Count0
Pull Requests Open Count0
Pull Requests Close Count44
项目设置
Has Wiki Enabled
Is Archived
Is Fork
Is Locked
Is Mirror
Is Private

LibreOffice

Coverity Scan Build Status CII Best Practices Translation status

LibreOffice is an integrated office suite based on copyleft licenses
and compatible with most document formats and standards. Libreoffice
is backed by The Document Foundation, which represents a large
independent community of enterprises, developers and other volunteers
moved by the common goal of bringing to the market the best software
for personal productivity. LibreOffice is open source, and free to
download, use and distribute.

A quick overview of the LibreOffice code structure.

Overview

You can develop for LibreOffice in one of two ways, one
recommended and one much less so. First the somewhat less recommended
way: it is possible to use the SDK to develop an extension,
for which you can read the API docs here
and here.
This re-uses the (extremely generic) UNO APIs that are also used by
macro scripting in StarBasic.

The best way to add a generally useful feature to LibreOffice
is to work on the code base however. Overall this way makes it easier
to compile and build your code, it avoids any arbitrary limitations of
our scripting APIs, and in general is far more simple and intuitive -
if you are a reasonably able C++ programmer.

The build chain and runtime baselines

These are the current minimal operating system and compiler versions to
run and compile LibreOffice, also used by the TDF builds:

  • Windows:
    • Runtime: Windows 7
    • Build: Cygwin + Visual Studio 2017 version 15.7
  • macOS:
    • Runtime: 10.10
    • Build: 10.13.2 + Xcode 9.3
  • Linux:
    • Runtime: RHEL 7 or CentOS 7
    • Build: either GCC 7.0.0; or Clang 5.0.2 with libstdc++ 7.3.0
  • iOS (only for LibreOfficeKit):
    • Runtime: 11.4 (only support for newer i devices == 64 bit)
    • Build: Xcode 9.3 and iPhone SDK 11.4
  • Android:
    • Build: NDK r19c and SDK 22.6.2

If you want to use Clang with the LibreOffice compiler plugins, the minimal
version of Clang is 5.0.2. Since Xcode doesn't provide the compiler plugin
headers, you have to compile your own Clang to use them on macOS.

You can find the TDF configure switches in the distro-configs/ directory.

To setup your initial build environment on Windows and macOS, we provide
the LibreOffice Development Environment
(LODE) scripts.

For more information see the build instructions for your platform in the
TDF wiki.

The important bits of code

Each module should have a README file inside it which has some
degree of documentation for that module; patches are most welcome to
improve those. We have those turned into a web page here:

https://docs.libreoffice.org/

However, there are two hundred modules, many of them of only
peripheral interest for a specialist audience. So - where is the
good stuff, the code that is most useful. Here is a quick overview of
the most important ones:

Module, Description
----------, -------------------------------------------------
sal/, this provides a simple System Abstraction Layer
tools/, this provides basic internal types: 'Rectangle', 'Color' etc.
vcl/, this is the widget toolkit library and one rendering abstraction
framework, UNO framework, responsible for building toolbars, menus, status bars, and the chrome around the document using widgets from VCL, and XML descriptions from /uiconfig/ files
sfx2/, legacy core framework used by Writer/Calc/Draw: document model / load/save / signals for actions etc.
svx/, drawing model related helper code, including much of Draw/Impress

Then applications

Module, Description
----------, -------------------------------------------------
desktop/, this is where the 'main' for the application lives, init / bootstrap. the name dates back to an ancient StarOffice that also drew a desktop
sw/, Writer
sc/, Calc
sd/, Draw / Impress

There are several other libraries that are helpful from a graphical perspective:

Module, Description
----------, -------------------------------------------------
basegfx/, algorithms and data-types for graphics as used in the canvas
canvas/, new (UNO) canvas rendering model with various backends
cppcanvas/, C++ helper classes for using the UNO canvas
drawinglayer/, View code to render drawable objects and break them down into primitives we can render more easily.

Rules for #include directives (C/C++)

Use the "..." form if and only if the included file is found next to the
including file. Otherwise, use the <...> form. (For further details, see the
mail Re: C[++]: Normalizing include syntax ("" vs
<>)
.)

The UNO API include files should consistently use double quotes, for the
benefit of external users of this API.

loplugin:includeform (compilerplugins/clang/includeform.cxx) enforces these rules.

Finding out more

Beyond this, you can read the README files, send us patches, ask
on the mailing list libreoffice@lists.freedesktop.org (no subscription
required) or poke people on IRC #libreoffice-dev on irc.freenode.net -
we're a friendly and generally helpful mob. We know the code can be
hard to get into at first, and so there are no silly questions.