LibreOffice/core
1
0
Fork 0
mirror of https://github.com/LibreOffice/core.git synced 2025-07-23 04:42:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

sw: add something about styles to README

Browse Source 
Change-Id: I2f6e23a69fdb950bfa778252b2f10eaa371f0e1e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/187756
Reviewed-by: Michael Stahl <michael.stahl@collabora.com>
Tested-by: Jenkins
This commit is contained in:
Michael Stahl
2025-07-11 21:12:47 +02:00
parent 47425922fc
commit e9e01ff356
1 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
sw/README.md
View File

@ -197,6 +197,31 @@ There are multiple model classes involved for fields:
Note that there is no UNO service to represent a list. Note that there is no UNO service to represent a list.
### Styles
Styles are either user-defined, or built-in.
User-defined styles simply have a user-defined name.
Built-in styles are identified by `RES_POOL*` constants in `inc/poolfmt.hxx`.
Each built-in style has 2 names:
* programmatic name (ProgName): this is defined in functions
`SwStyleNameMapper::GetTextProgNameArray()` etc, and *never* *ever* changes.
* translatable name (UIName): this is defined as `STR_POOL*` constants
for en-US in `sw/inc/strings.hrc` and is translated like any other
translatable string.
These strings have been changed and may change in future versions.
At the UNO API, and in ODF documents, only ProgNames are relevant.
In the UI, the UINames are used.
Unfortunately the core code also uses UIName, it would be better if it used
ProgName and the conversion would happen in UI code.
### Layout ### Layout
The layout is a tree of `SwFrame` subclasses, the following relationships are The layout is a tree of `SwFrame` subclasses, the following relationships are