Title: PSKOV 2 for JVM Date: 2025-02-11 00:00 Category: News Slug: psk-jvm-item Lang: en ![splash][splash] # Seperate pages' generation In January I implemented half of the functionality of original PSKOV: generation of separate HTML pages from Markdown. Both PSKOV 1 and PSKOV 2 produce HTML files that look the same in web browsers. However, the contents of the generated HTML files differ because PSKOV 1 uses [Showdown][showdown] to convert Markdown to HTML, whereas PSKOV 2 uses [intellij-markdown][intellij-markdown]. Let's see how the generated HTML files compare. Suppose we have the following page in Markdown: ``` Simple page in **Markdown** to convert to **HTML**. | № | Parser | Language | |---|--- |--- | | 1 | [Showdown][showdown] | JavaScript | | 2 | [intellij-markdown][intellij-markdown] | Kotlin | [intellij-markdown]: https://github.com/JetBrains/markdown [showdown]: https://github.com/showdownjs/showdown ``` PSKOV 1 converts the aforementioned Markdown to the following HTML: ```

Simple page in Markdown to convert to HTML.

Parser Language
1 Showdown JavaScript
2 intellij-markdown Kotlin
``` PSKOV 2: ```

Simple page in Markdown to convert to HTML.

ParserLanguage
1ShowdownJavaScript
2intellij-markdownKotlin
``` Here's how both HTML files are rendered in web browsers: ![result][result] Identical rendering of different files. My internal perfectionist is outraged by such a disrepancy. And my internal pragmatist thinks this hardly deserves such an attention. # February In February I'm going to update the cross-language dialect's translator to produce Context. [intellij-markdown]: https://github.com/JetBrains/markdown [result]: ../../images/2025_psk-jvm-item_result.png [showdown]: https://github.com/showdownjs/showdown [splash]: ../../images/2025_psk-jvm-item.png