Problems in Standards
This section contains remarks on the text versions of Linux standards. All the issues reported here have been found during requirements formalization in the OLVER and LSB Infrastructure projects. We have defined the following life cycle for each potential issue.
- Initial problem detection during standard formalization.
- Problem formulation and registration in the internal problem tracking system.
- Periodical collective analysis of the validity and importance of registered problems.
- Reporting all approved issues to the appropriate standard bodies.
- Standard bodies decide whether to incorporate any changes in the standards or not.
Click on a problem number for detailed description. Click on a column header to change the sorting order.
No. | Type | Brief | Added on | Accepted | Status |
S0681 | Incompleteness | FcStrDirname is not documented | Fixed in fontconfig 2.6.0 | ||
S0589 | Misprint | Misprint in names of FcConfigSetRescanInverval and FcConfigGetRescanInverval | Fixed in fontconfig 2.4.0 | ||
S0588 | Incompleteness | Lack of information regarding to memory management of FcConfigGetFonts returned value | Fixed in fontconfig 2.4.0 | ||
S0587 | Misprint | Insignificant misprints | Fixed in fontconfig 2.4.0 | ||
S0586 | Misprint | Misprints: char instead of FcChar8 | Fixed in fontconfig 2.4.0 | ||
S0584 | Incompleteness | No information about returned value of many fontconfig functions | Fixed in fontconfig 2.4.0 |
»