Skip to content
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

Poem #198

Open
KariRudjord opened this issue Sep 7, 2018 · 3 comments
Open

Poem #198

KariRudjord opened this issue Sep 7, 2018 · 3 comments

Comments

@KariRudjord
Copy link

Check how poem is rendered in ordinary text (without headline). Do we need an open cell between ordinary text and poem?

@KariRudjord
Copy link
Author

KariRudjord commented Nov 9, 2018

Is it possible to implement a rule in CSS saying that div class="linegroup" shall have one empty row before when coming stright after a /p?
Useful when a poem appears in an ordinary textflow. Now its quite unclear that a poem starts on the 5th line in the excample belowe (there's already a rule saying one empty row after </div>).

skrevet masteroppgave om      
norrøn mytologi1 om jotnene1  
om menneskenes mørke og far-  
lige skygger'                 
,Hvis jeg kunne puste på meg  
  selv                        
der hvor jeg var for tyve år  
  siden                       
ville jeg ha pustet varmt og  
  oppmuntrende                
på min egen nakke             
                              
  ,Jeg hadde blitt doktor-    
gradsstipendiat i språkviten-

@KariRudjord KariRudjord moved this from Issues to check to Waiting for clarification in PIP - further improvements 2021 Nov 9, 2018
@bertfrees
Copy link
Collaborator

There is the next sibling combinator.

@josteinaj
Copy link
Member

I think a top-margin of 1 row for poems and verses would solve this. I'm adding a test for it and modifying the SCSS.

josteinaj added a commit that referenced this issue Nov 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
PIP - further improvements 2021
Waiting for clarification
Development

No branches or pull requests

4 participants