Problem/Motivation
After finishing translation of that file, I'd bet that 2.3. Concept: Content Entities and Fields topic is definitely amongst the most difficult ones to explain clearly. Thus its large comparison table does a vital job in trying to help get through the matter to the Reader. We need the content of all the five columns for sure.
My observation is that the last column (called "Examples") contains a much bigger volume of text than the other four. That causes huge white areas on the left and a narrow, hard-to-read text on the right. That kind of visual frustration could have a bad effect on focusing to the topic holding back the Reader from having a better understanding on such a key important subject.
Proposed resolution
I tinkered around a bit with awesomly flexible AsciiDoc syntax and reached the following results depicted on the right half:
Although the situation is not that bad with English:
Anyway, I provide a patch to let others try out my suggestions on their own.
Comments
Comment #2
Balu ErtlComment #3
jhodgdonI like it! Thanks for the issue and patch.
Any thoughts Joe?
Comment #4
eojthebraveLooks like a good idea to me. +1
Thanks for the suggestion @Balu Ertl
Comment #5
jhodgdonI have a question about the patch. Why are there so many {nbsp} lines in the patch(es)? Are they necessary for the table formatting? They seem a bit odd, especially the one at the end of the table. Can they be removed?
Comment #6
Balu ErtlI put them to make some extra room between rows for easier overview. I admit it's not the most elegant solution, but I had no better idea at the moment. I learned this trick from here: https://github.com/asciidoctor/asciidoctor/wiki/How-to-insert-sequential...
Comment #7
jhodgdonI'm not excited about them either, and I think they will cause confusion and/or errors for future editors and translators. Does it look terrible without them?
Comment #8
Balu ErtlActually not that bad without them neither, so feel free to remove them.
Comment #9
Balu ErtlI'm Glad to hear that both Jennifer & Joe agrees, do you think shall I commit our HU file with this table structure, so we can see how it works for displaying on Docs and generating ePub/PDF output?
Comment #10
jhodgdonPlease feel free to commit to the HU version. :) For the EN version, let's have a new patch without the nbsps in there and go forward.
I have not tested this will build correctly and what it looks like in the e-book versions, but will do that later... I am traveling for the next 2 weeks without a laptop so I cannot do it until I get back. (Having a nice vacation in Costa Rica!!)
Comment #11
Balu ErtlAlright, so I committed in with the extra new lines, let's see, how it will look like:
http://cgit.drupalcode.org/user_guide/plain/source/hu/planning-data-type...
Comment #12
jhodgdonI'm back from my trip... Committed the above patch to the English version, with the following changes:
- Took out the nbsp lines
- Took out the |||| line, which had left a blank line at the top of the table, which looked very odd to me.
Result now builds well and output looks good. Marking Fixed. I will also send out notification to translation groups as per our policy on #2871873: Change process for notifying translation groups about source changes
Comment #14
jhodgdonHere's a link to the notification message I sent, for reference:
https://groups.google.com/forum/#!topic/d8manual/Jrs0F8XInPw
Comment #15
Balu Ertl@Jennifer, does it mean that there's a new deploy to Docs pages or a new ePub/PDF release shining somewhere on the horizon?
Comment #16
jhodgdonGood idea, I will see about a new release and a deploy to docs pages next week.
Comment #17
jhodgdonThe new ebook release is out!
New deploy to drupal.org is in progress... should be there later today I think.
Comment #18
jhodgdonhttps://www.drupal.org/docs/user_guide/en/planning-data-types.html
https://www.drupal.org/hu/docs/user_guide/hu/planning-data-types.html
The build is still in progress, so other languages will be updated in a while...
Comment #19
Balu ErtlAh, snap! Now I realised I was misled by Atom editor's AsciiDoc preview module, which has an even-odd colouring style for table rows, and I did not think through that there's another CSS formatting on D.org Docs. That's the reason of the un-necessary extra row under table head. I will remove from our source file as well.
By the way, with this release HU team has reached the 50% of translation being done :)
Comment #21
jhodgdonCongratulations on the translation milestone!