Skip to content
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.

Paragraphs and line breaking in HTML posts #41

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rwmpelstilzchen
Copy link

Hi,

Thanks for Exitwp. I've used it for migrating my data from my (old) WordPress blog to Jekyll. ☺

My posts are in HTML, which is the default in WP. The migration ran smoothly, but I've noticed that Exitwp outputs the content of the posts as-is. Now, when manually editing HTML posts in WP one can omit <p>s and <br />s and they are automatically added using the wpautop PHP command; thus, all of the paragraphs and line breaks in Exitwp's output were not processed by the browser as such, since they were whitespaces.

The pull request fixes this. Using this Python implementation of wpautop. It changes the default target format from Markdown to HTML, because the conversion to Markdown loses data (I think you might want to add a warning about this in the comment on target/output formats in the configuration file).

Thanks,
Júda

@thomasf
Copy link
Collaborator

thomasf commented May 13, 2014

Hello, I think that markdown should remain the default output format.

@rwmpelstilzchen
Copy link
Author

OK, but don't you think paragraph separation and line breaking should be properly processed?

@thomasf
Copy link
Collaborator

thomasf commented May 15, 2014

Yes, that is probably desirable for most situations.

@SeanFromIT
Copy link

I like the linebreaks_wp.py additions, I feel like this would address some of the things I had to clean-up manually after migration.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants