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

remove line break after first <li> item #62

Closed
sanette opened this issue Mar 17, 2021 · 11 comments
Closed

remove line break after first <li> item #62

sanette opened this issue Mar 17, 2021 · 11 comments

Comments

@sanette
Copy link

sanette commented Mar 17, 2021

Currently the first item of an itemize environment is not rendered exactly as the other ones: there is a line break after <li...>, as in the following example:

<ul class="itemize"><li class="li-itemize">
item1
</li><li class="li-itemize">item2
</li><li class="li-itemize">item3
</li></ul>

This turns out to be a problem for some CSS list styles, like the "inside" style, where the line break is converted into a space.

Would it be possible to simply remove this line break? so as to obtain:

<ul class="itemize"><li class="li-itemize">item1
</li><li class="li-itemize">item2
</li><li class="li-itemize">item3
</li></ul>
@cspiel
Copy link
Contributor

cspiel commented Mar 17, 2021

I have a patch here that opens a paragraph for \item to avoid
mixed content and to simplify styling lists with CSS. The HTML
output looks like this (after wrapping and indenting with tidy):

  <ul class="itemize">
    <li class="li-itemize">
      <p><span class="monospace">\epsilon</span>: є; <span class=
      "monospace">\varepsilon</span>: ε;</p>
    </li>
    <li class="li-itemize">
      <p><span class="monospace">\kappa</span>: κ; <span class=
      "monospace">\varkappa</span>: ϰ (AMST<sub>E</sub>X);</p>
    </li>

I have run into style-ability problems, too before this patch.

@maranget
Copy link
Owner

maranget commented Mar 17, 2021

You get intended output by writing \begin{itemize}\item..., i.e. no newline before first \item. This is more a workaround than a solution.

@maranget
Copy link
Owner

Should be ok by now, having merged PR #63. Would you please check that the new code fixes your issue?

@sanette
Copy link
Author

sanette commented Mar 22, 2021

aside question, is there an easy way to create a local opam package for the dev version of hevea?

@maranget
Copy link
Owner

aside question, is there an easy way to create a local opam package for the dev version of hevea?

I have nether thought about doing that, considering that compiling hevea from sources is relatively easy (no requirement other than ocamlbuild).

@sanette
Copy link
Author

sanette commented Mar 24, 2021

what I would like is to be able to switch between two versions easily. If there is a simple way to uninstall the dev version, that's maybe enough

@maranget
Copy link
Owner

what I would like is to be able to switch between two versions easily. If there is a simple way to uninstall the dev version, that's maybe enough

I can easily add some uninstall entry in Makefile and will do. Notice that you can use two version of hevea easily by using compete command names. Assuming you have standard hevea installed normally, whatever the method. You can for instance install the dev version of hevea in your home directory with make all install PREFIX=$HOME. Then, you access to the dev version as ~/bin/hevea.

@maranget
Copy link
Owner

Complement, for make all install PREFIX=$HOME to work properly you have to call make clean beforehand.

@maranget
Copy link
Owner

Hi @sanette, I am a bit lost does PR #63 address theissue?

@sanette
Copy link
Author

sanette commented Oct 24, 2021

according to ocaml/ocaml#10672 (comment)
yes it does solve it.

I will try asap myself

@sanette
Copy link
Author

sanette commented Oct 24, 2021

yes! solved, thanks. I'm closing this.

@sanette sanette closed this as completed Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants