New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template #1 (default): Adjusting paddings &/or margins #3

Closed
joeflack4 opened this Issue Jun 19, 2018 · 6 comments

Comments

Projects
2 participants
@joeflack4
Contributor

joeflack4 commented Jun 19, 2018

Description

Make formatting tighter with less spacing between content, again to save space.

Tasks

  • 0. Develop an updated template.
  • 1. You have a separate branch. A branch where the template has been updated to the "all_at_once" version. Or, a branch where it doesn't replace the original ppp template, but exists as a second, template--either as the new default, or non-default.
  • 2. You make a pull request from your branch to the develop branch.
  • 3. I will review, resolve any merge conflicts, merge into develop, and close this issue.
  • 4. Then you can delete your feature branch if you want: git branch -D [FEATURE_BRANCH], git push origin --delete [FEATURE_BRANCH]
  • 5. You will git fetch --all and git pull trunk/develop from inside your develop branch so that your develop branch is in sync with trunk.
  • 6. If you have any other any other currently active feature branches, you can update them to be in sync with this new feature branch by switching to those branches, and doing git rebase develop or git rebase trunk/develop. You may experience some merge conflicts that need resolution. If so, it will be a good learning experience.
@tulvit

This comment has been minimized.

Show comment
Hide comment
@tulvit

tulvit Jun 22, 2018

Member

No good news :'(

I'll assume that "tighter formatting" == "saving space" == "less pages". Because after some changes it may seem that it's become really "tighter". But if the number of pages remains the same - no, it isn't

Original .xlsx (the one I have for tests) -> .html -> .doc == 34 pages. So it's a starting point.

Reducing font size a bit

1em -> 0.9em
Doesn't work. Same 34 pages.

Word breaking on '_' and other chars

In some cases long strings ('${husband_cohabit_start_recent}') produce extra space in a nearby cells, so it was worth to try...
Doesn't work. Same 34 pages.

Changing table proportions

Original columns' ratio was 50%/50%. But question cells contain a way more content then response cell (just forms), so why not to change it to 70%/30%? I really hoped it would work, and yeah, it seems it really become a little bit tighter (and it was quite a tricky task, for example if a colspan attribute is presented, then all tds' width will be ignored) , but...
Doesn't work. Same 34 page.

Misc.

Changing this and that, here and there...
Doesn't work, doesn't work.

Margins/paddings

Let's go wild:

* {
  margin: 0 !important;
  padding: 0 !important;
}

Doesn't work. But, perhaps, Word just ignore this wildcard. Tested each and every tag separately - and it worked. Hooray! So,

td,
p,
h1,
h2,
h3,
ul,
li,
tr,
em,
et cetera {
  padding: 0 !important;
  margin: 0 !important;
}

and... 27 pages! 20% less!

But I'm not sure it's the case. The main problem is an overall layout.

For example, it might make sense to use not this:
question|response
question|response

table layout, but
question
response
question
response

And yet again, there are these long vertical lists,
[ ] male
[ ] female

I really want to make them float, it will save so much space...
But I really don't want to make them in one line, it will reduce readability so much...
I mean this one is easy to use/submit:
[ ] January
[ ] February
[ ] March
[ ] etc.

and this is just a mess:
[ ] January [ ] February [ ] March [ ] etc.

So I guess readability should be always over the space saving...

In other words, what should I do next?

I guess:

  • Playing around with paddings/margins only, anyway reducing page count by 10-15% will be not a bad result after all with options we have...
  • Adding to a todo list "think hard about further layout improvements".
Member

tulvit commented Jun 22, 2018

No good news :'(

I'll assume that "tighter formatting" == "saving space" == "less pages". Because after some changes it may seem that it's become really "tighter". But if the number of pages remains the same - no, it isn't

Original .xlsx (the one I have for tests) -> .html -> .doc == 34 pages. So it's a starting point.

Reducing font size a bit

1em -> 0.9em
Doesn't work. Same 34 pages.

Word breaking on '_' and other chars

In some cases long strings ('${husband_cohabit_start_recent}') produce extra space in a nearby cells, so it was worth to try...
Doesn't work. Same 34 pages.

Changing table proportions

Original columns' ratio was 50%/50%. But question cells contain a way more content then response cell (just forms), so why not to change it to 70%/30%? I really hoped it would work, and yeah, it seems it really become a little bit tighter (and it was quite a tricky task, for example if a colspan attribute is presented, then all tds' width will be ignored) , but...
Doesn't work. Same 34 page.

Misc.

Changing this and that, here and there...
Doesn't work, doesn't work.

Margins/paddings

Let's go wild:

* {
  margin: 0 !important;
  padding: 0 !important;
}

Doesn't work. But, perhaps, Word just ignore this wildcard. Tested each and every tag separately - and it worked. Hooray! So,

td,
p,
h1,
h2,
h3,
ul,
li,
tr,
em,
et cetera {
  padding: 0 !important;
  margin: 0 !important;
}

and... 27 pages! 20% less!

But I'm not sure it's the case. The main problem is an overall layout.

For example, it might make sense to use not this:
question|response
question|response

table layout, but
question
response
question
response

And yet again, there are these long vertical lists,
[ ] male
[ ] female

I really want to make them float, it will save so much space...
But I really don't want to make them in one line, it will reduce readability so much...
I mean this one is easy to use/submit:
[ ] January
[ ] February
[ ] March
[ ] etc.

and this is just a mess:
[ ] January [ ] February [ ] March [ ] etc.

So I guess readability should be always over the space saving...

In other words, what should I do next?

I guess:

  • Playing around with paddings/margins only, anyway reducing page count by 10-15% will be not a bad result after all with options we have...
  • Adding to a todo list "think hard about further layout improvements".
@joeflack4

This comment has been minimized.

Show comment
Hide comment
@joeflack4

joeflack4 Jun 26, 2018

Contributor

Yeah, I think you're right. I don't think there's too much we can do here. Thinking back to the request that was made of us, I think it will be best if we just mess with the padding and font sizes a little bit, but not a lot.

70/30 may be a good idea though, as an alternative to 50/50. But I don't think we should change much more than that.

I think with the padding of 0, it just looks worse. But before this adjustment, there was barely any padding at all.

Can you do the following:

  • Produce a 70/30 .doc file example, but with the original padding.

After that, I'll share the following with my co-workers and get some feedback: (a) the original (50/50, default padding), (b) 70/30, 0 padding, and (c) 70/30, default padding.

Contributor

joeflack4 commented Jun 26, 2018

Yeah, I think you're right. I don't think there's too much we can do here. Thinking back to the request that was made of us, I think it will be best if we just mess with the padding and font sizes a little bit, but not a lot.

70/30 may be a good idea though, as an alternative to 50/50. But I don't think we should change much more than that.

I think with the padding of 0, it just looks worse. But before this adjustment, there was barely any padding at all.

Can you do the following:

  • Produce a 70/30 .doc file example, but with the original padding.

After that, I'll share the following with my co-workers and get some feedback: (a) the original (50/50, default padding), (b) 70/30, 0 padding, and (c) 70/30, default padding.

@tulvit

This comment has been minimized.

Show comment
Hide comment
@tulvit

tulvit Jun 27, 2018

Member

Files in the zip:

original.doc - original doc with no modifications

original2.doc - actually, original is a little bit "buggy", so columns' ratio is not 50%/50%, but more like 48%/52%, because some content in a response cells is too long and occupy more than 50% of the document (like three inputs in a row), in this version it's fixed

font_reduced.doc - same as original2, but with font size reduced by 10%

padding_reduced.doc - same as original2, but with padding reduced

60_40_ratio.doc - same as original2, but with 60/40 table ratio

70_30_ratio.doc - same as original2, but with 70/30 table ratio

all_at_once.doc - all changes at once

docs.zip

Member

tulvit commented Jun 27, 2018

Files in the zip:

original.doc - original doc with no modifications

original2.doc - actually, original is a little bit "buggy", so columns' ratio is not 50%/50%, but more like 48%/52%, because some content in a response cells is too long and occupy more than 50% of the document (like three inputs in a row), in this version it's fixed

font_reduced.doc - same as original2, but with font size reduced by 10%

padding_reduced.doc - same as original2, but with padding reduced

60_40_ratio.doc - same as original2, but with 60/40 table ratio

70_30_ratio.doc - same as original2, but with 70/30 table ratio

all_at_once.doc - all changes at once

docs.zip

@joeflack4 joeflack4 added this to To do in PPP via automation Jun 28, 2018

@joeflack4 joeflack4 changed the title from Adjusting paddings &/or margins to Adjusting paddings &/or margins for default template Jun 28, 2018

@joeflack4 joeflack4 changed the title from Adjusting paddings &/or margins for default template to Template #1 (default): Adjusting paddings &/or margins Jun 29, 2018

@joeflack4 joeflack4 self-assigned this Jun 29, 2018

@joeflack4

This comment has been minimized.

Show comment
Hide comment
@joeflack4

joeflack4 Jun 29, 2018

Contributor

@tulvit Hey Vitaly~.

IMO, I like the "all_at_once" version, which I think is--60/40, font reduced, without padding reduction.

I've edited the original post with some tasks describing he way I'd like to proceed from here. Please check it out~

Contributor

joeflack4 commented Jun 29, 2018

@tulvit Hey Vitaly~.

IMO, I like the "all_at_once" version, which I think is--60/40, font reduced, without padding reduction.

I've edited the original post with some tasks describing he way I'd like to proceed from here. Please check it out~

@tulvit

This comment has been minimized.

Show comment
Hide comment
@tulvit

tulvit Jul 2, 2018

Member

@joeflack4 Hello!

Please, check out the file attached below (I've zipped it - it seems github doesn't allow doc files).
If everything is ok, then here is a changes.

example.doc.zip

Member

tulvit commented Jul 2, 2018

@joeflack4 Hello!

Please, check out the file attached below (I've zipped it - it seems github doesn't allow doc files).
If everything is ok, then here is a changes.

example.doc.zip

@joeflack4

This comment has been minimized.

Show comment
Hide comment
@joeflack4

joeflack4 Jul 3, 2018

Contributor

@tulvit Closing this issue, as it and the PR are complete. GJ!

Contributor

joeflack4 commented Jul 3, 2018

@tulvit Closing this issue, as it and the PR are complete. GJ!

@joeflack4 joeflack4 closed this Jul 3, 2018

PPP automation moved this from To do to Done Jul 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment