Bug 150928 - Review and replace uses of "character set" with "encoding"
Summary: Review and replace uses of "character set" with "encoding"
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Dev-related
  Show dependency treegraph
 
Reported: 2022-09-13 11:11 UTC by Mike Kaganski
Modified: 2024-08-01 09:02 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2022-09-13 11:11:50 UTC
UI and documentation use "character set" term sometimes, e.g. in https://help.libreoffice.org/7.4/en-US/text/shared/00/00000215.html?DbPAR=WRITER (the respective dialog is shown when importing/exporting using Text - Choose Encoding filter, and having "Edit filter settings" checked).

The term "character set" is wrong in that context; the correct term would be "encoding" [1]. E.g., UTF-8 and UTF-16 have *the same character set* (Unicode), but are different encodings.

We need to review the UI strings to make sure that "Encoding" is used where "Character set" is used incorrectly.

[1] https://www.w3.org/International/articles/definitions-characters/
Comment 1 Rafael Lima 2022-09-13 14:20:01 UTC
Hi Mike, indeed this issue appears many times in the UI and in the Help.

A quick search shows that we have 23 occurrences of the term "character set" that need checking.

https://opengrok.libreoffice.org/search?project=help&full=%22character+set%22&defs=&refs=&path=&hist=&type=&xrd=&nn=1

To fix this issue we'll need various patches.