This wiki has undergone a migration to Confluence found Here
Difference between revisions of "OO CR085 - Monospaced NTE Font"
Jump to navigation
Jump to search
Hbuitendijk (talk | contribs) |
Hbuitendijk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | {{OO | + | {{OO Approved Change Requests}} |
| − | {{OO | + | {{OO Approved LRI IG Change Requests}} |
Return to [[:Category:OO Change Requests|OO Change Requests]] page. | Return to [[:Category:OO Change Requests|OO Change Requests]] page. | ||
| Line 29: | Line 29: | ||
*24-Jul-2012 - Intent is to pursue this for Errata (then Normative). Requires a vote, so will be queued up for OO conference call. | *24-Jul-2012 - Intent is to pursue this for Errata (then Normative). Requires a vote, so will be queued up for OO conference call. | ||
*3-Aug-2012 - Suggest to review with ACLA next week to get further insight. | *3-Aug-2012 - Suggest to review with ACLA next week to get further insight. | ||
| − | *14-Aug-2012 - Was discussed with ACLA and was considered a good idea. | + | *14-Aug-2012 - Was discussed with ACLA and was considered a good idea. Concern that some systems can only support up to 60 characters. So there are two issues: wrapping and alignment. |
== Resolution == | == Resolution == | ||
| + | *14-Aug-2012 - Suggestion to provide guidance as it is of concern that requiring monospace is not always appropriate. Motion to include guidance language to clarify that when alignment and wrapping are of concern, monospaced font provides a means to resolve this, but requires both parties to agree on how to preserve monospaced font in the final display. Ken McCaslin, David Burgess. | ||
| + | ** Against: 0; Abstain: 0; In Favor: 9 | ||
| + | ** To be included in errata. | ||
Revision as of 19:21, 14 August 2012
Template:OO Approved Change Requests Template:OO Approved LRI IG Change Requests Return to OO Change Requests page.
| Submitted by: Pilots | Revision date: <<Revision Date>> |
| Submitted date: Mar-2012 | Change request ID: OO CR079 |
| Standard/IG: Implementation Guide | Artifact ID, Name: <<Artifact ID, Name>> |
Issue
Note that any text (e.g. NTE) should be produced and interpreted (e.g. displayed) in a monospaced font to preserve alignment of information (e.g. tables).
Recommendation
Rationale
Discussion
Recommended Action Items
- 24-Jul-2012 - Intent is to pursue this for Errata (then Normative). Requires a vote, so will be queued up for OO conference call.
- 3-Aug-2012 - Suggest to review with ACLA next week to get further insight.
- 14-Aug-2012 - Was discussed with ACLA and was considered a good idea. Concern that some systems can only support up to 60 characters. So there are two issues: wrapping and alignment.
Resolution
- 14-Aug-2012 - Suggestion to provide guidance as it is of concern that requiring monospace is not always appropriate. Motion to include guidance language to clarify that when alignment and wrapping are of concern, monospaced font provides a means to resolve this, but requires both parties to agree on how to preserve monospaced font in the final display. Ken McCaslin, David Burgess.
- Against: 0; Abstain: 0; In Favor: 9
- To be included in errata.
