Changeset 1859ee6 for introduction
- Timestamp:
- 12/23/2023 12:40:25 PM (9 months ago)
- Branches:
- 12.1, 12.2, gimp3, ken/TL2024, lazarus, plabs/newcss, python3.11, rahul/power-profiles-daemon, trunk, xry111/for-12.3, xry111/llvm18, xry111/spidermonkey128
- Children:
- 5481e1f1
- Parents:
- a927adc
- git-author:
- Pierre Labastie <pierre.labastie@…> (12/23/2023 12:38:42 PM)
- git-committer:
- Pierre Labastie <pierre.labastie@…> (12/23/2023 12:40:25 PM)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/locale-issues.xml
ra927adc r1859ee6 37 37 38 38 <para>If there is a known workaround for a specific package, it will 39 appear on that package's page. For the most recent information 40 about locale related issues for individual packages, check the 41 <ulink url="&blfs-wiki;/BlfsNotes">Editor Notes</ulink> in the BLFS 42 Wiki.</para> 39 appear on that package's page.</para> 43 40 44 41 <sect2 id="locale-not-valid-option" … … 91 88 invalid for documents where the Microsoft Windows operating system 92 89 has set de facto standards. An example of this problem is ID3v1 tags 93 in MP3 files (see the <ulink url="&blfs-wiki;/ID3v1Coding">BLFS Wiki 94 ID3v1Coding page</ulink> 95 for more details). For these cases, the only solution is to find a 90 in MP3 files. For these cases, the only solution is to find a 96 91 replacement program that doesn't have the issue (e.g., one that 97 92 will allow you to specify the assumed document encoding).</para>
Note:
See TracChangeset
for help on using the changeset viewer.