Paul, any thoughts about this? The DITA TC would be glad to help.
We really need actual written specifications in order to
build our stylesheets and NOT incur churn.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
-------- Forwarded Message --------
Thanks! Paul, can you take this one. I suspect
you can make short work of it compared to me.Â
/chet
Rendering only. I think required content
(conformance, introduction, keywords, etc) is a separate
issue.
Here is a list of the information that i need in order
to create (or update) stylesheets for the committee
note. Ken, anything that you'd want to add? Or if I am
being DITA-centric in what I need to know, please let me
know.
- Any differences between PDF and HTML output?
- Example: For single-paged HTML output, the
<title> element should contain document title.
Question: Should this be shortened to be more useful
as viewed in the browser tab?
- Font sizes are better specified in PDF as points
but in CSS as percentages
- Basic settings that apply to entire document
- Page size
- Margin sizes and whether they are mirrored or not
- Specifics for cover page:
- Logo and where it should be placed. Font size,
color, and weight for any static text-based content
- Font size, font color, font weight, padding for
each title, subtitle, and section title:
- Document title and version
- Level of committee note
- Date of committee note
- Specification URIs -- and should this be
something else for committee notes? "Committee
note URIs?"
- This version
- Next version
- Latest version
- Technical Committee
- Chairs
- Editors
- Additional artifacts
- Related work
- Abstract
- Status
- Citation format
- Content for each section
- Font size?
- Any indentation?
- Font weight for any specific components?
- Color and font weight for hyperlinks?
- Fonts
- What fonts are used?
- Serif font =
- San-serif font =
- Monospace font =
- What fallback fonts should be specified?
- Headers
- Footers
- Which pages should footers appear on?
- Font size, font color, font weight
- Content to be included
- How content should be arranged
- Does the arrangement of content differ based on
whether the page is an even or odd number?
- Is there a line about the footer content? If so,
what color and weight?
- Body content
- Basics:
- Header levels:
- Font size, font color, and font weight
- Is there any indentation?
- Any lines above or below headers?
- Lists: Should list items have indentation? If so,
how much?
- Tables:
- Color for header rows
- Font size for table cell content
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
On
2/11/2019 9:01 AM, Chet Ensign wrote:
Kris, we'd be happy to do that. Can you
provide examples or templates of style sheet
documentation that would give you and Ken what you
need? Also, are you talking about rendering specs only
or does that include required sections, headings,
etc/Â
Thanks,Â
/chet
Guys, I want to suggest that OASIS establish
style specifications for specifications and
committee notes. TC administration and TCs then
can work from those style specifications to
build the following:
- Stylesheets for rendering from DITA
- Stylesheets for rendering from Docbook
- Word templates for OASIS TCs that use Word
- Open Office templates for OASIS TC that use
Open Office
This would be much more efficient, not to
mention being a more appropriate process for
OASIS! And I'd be glad to help OASIS with
methodology for documenting document-rendering
specifications, as I am sure others would also.
It's very painful and time-consuming to
reverse-engineer style specifications from a
Word template. And it often seems as if we are
working with moving targets ...
Can we change this process? Please?
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
-------- Forwarded Message --------
Latest template for committee notes.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
-------- Forwarded Message --------
Hi Chet and Kris,
I'm attaching the new templates for
Notes in MS-Word (DOCX) format.
These use Liberation Sans and
Liberation Mono for almost all styles.
I think that the font sizes used here
are the ones we will want to use for the
DITA Notes. I think that the fractional
font sizes Kris found in the PDF from Chet
are an artifact of the PDF generation. I
don't think we've used fractional fonts in
the editable templates (MS-Word and Open
Office).
Best regards,
Paul
Sounds like we're
interested in common goals
here.ÂÂ
We are investigating the use
ofÂLiberation Sans as a
replacement for Arial, Calibri,
Cambria, and similar fonts.
Basic background here:
It appears to be bundled with
Open Office, LibreOffice,
MS-Word. (On my system, anyway).
We're planning to assemble a
Notes template based on
Liberation Sans as the primary
sans-serif font. (Any comments
on this are welcome!)
It would be a good
opportunity for us to clearly
pin down font sizes, and likely
other style elements which have
historically been a bit
neglected.
Best regards,
Paul
Ditto, thanks Kris! I
didn't realize we had fonts showing
up in fractional sizes.Â
/chet
Hi Kris and all,
Thanks for assembling this
so clearly! It's very useful
to consider several of these
items together.
I'll dig into this and see
what the next steps might be.
Best regards,
Paul
Hi, Paul.
I'm comparing the PDF
that Chet sent in November
with what we we have in
our current style sheets.
Here are the changes that
I identify:
Change
|
Notes
|
Comments/Things
we need from OASIS
|
New
header for cover
page. Includes:
- New logo
- The text
"OASIS Committee
Note"
- A line
|
Text
= Arial, 18 pt bold,
#707070
Line = ?
|
- High-quality
version of the
logo
- Specifications
for the line:
Color and
thickness
|
Cover
page titles
|
Text
= Arial (replace
Cambria), bold,
#446CAA (replace #?)
Various font
weights:
Note Title Version =
24 pt
Committee Note Draft
NN = 18pt (replace
16 pt, add bold)
Specification URIs =
12 pt (replace 14
pt, eliminate
padding below)
...
|
OASIS:
I am going to change
the fonts and
colors, but largely
leave the font sizes
as is. Then let's
look at the results
and see what you
think.
It does not look
like the PDF that
you sent us is a
final design; it has
less-than-ideal font
sizes (10.80 pt and
8.88 pt) and padding
for elements.
Can we standardize
font sizes to use
whole numbers?
|
Sidebar
on cover page
|
Remove
|
|
Footer
on cover page
|
Add;
the old design did
not have the footer.
|
|
Footer
|
Render
copyright statement
on a single line;
bottom aligned
|
|
Header
|
Remove
|
|
Body
titles
|
Text
= Arial (replace
Cambria) bold
H1 = 18 pt
H2 = 13.92 pt
(replace 14 pt)
H3 = 12.96 pt
H4 = Not defined
|
Can
we standardize font
sizes to use whole
numbers? |
Body
text
|
Calilbri
10.80 pt
|
|
Footer
text
|
Calibri
8.88 pt
|
|
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA
Technical Committee
Principal consultant,
Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501;
kriseberlein (skype)
On
1/28/2019 10:47 AM,
Kristen James Eberlein
wrote:
FYI. Forwarding to the
list so that I can
reference this in a
GitHub issue.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA
Technical Committee
Principal consultant,
Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501;
kriseberlein (skype)
-------- Forwarded
Message --------
Hi
folks,Â
After reviewing
possible designs for
a new Committee Note
with the TAB and
several interested
members, we have
settled on the
attached. This
eliminates the fat
blue bar that took
up the so much real
estate on the first
page and the header
that reminded you,
page after page,
that THIS ISN'T
STANDARDS TRACK! Oye
vey.Â
Instead, it uses
a label, just under
the OASIS logo, to
identify this as a
Committee Note and
it states in the
Status section that
the patent
provisions of the
OASIS process don't
apply. It is
cleaner, matches our
new color scheme,
and makes Committee
Notes less like ugly
step children.Â
Ken, Kris, Dave,
let us know what
information you want
regarding colors,
etc. Paul, let's go
ahead and update the
cover page template
when you get a
chance.Â
--
/chetÂ
----------------
Chet
Ensign
Chief Technical Community Steward
OASIS:
Advancing open
standards for
the
information
society
http://www.oasis-open.org
Primary: +1
973-996-2298
Mobile: +1
201-341-1393Â
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
OASIS
- Advancing
open standards
for the
information
society
--
/chetÂ
----------------
Chet
Ensign
Chief Technical Community Steward
OASIS: Advancing
open standards for
the information
society
http://www.oasis-open.org
Primary: +1
973-996-2298
Mobile: +1
201-341-1393Â
--
OASIS
- Advancing open
standards for
the information
society
--
OASIS
- Advancing open
standards for the
information society
--
/chetÂ
----------------
Chet Ensign
Chief
Technical Community Steward
OASIS: Advancing open standards for
the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393Â
--
/chetÂ
----------------
Chet Ensign
Chief
Technical Community Steward
OASIS: Advancing open standards for the
information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393Â
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC
that generates this mail. Follow this link to all your TCs in
OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|