Plugin / Jimmy Codeviewer

Installation

From “Plugins” of your admin page, just search and install “Jimmy Codeviewer”. Make sure to activate “Jimmy Codeviewer” in “Installed Plugins”, a “Plugins” sub menu.

You can download and test the latest version of this plugin from GitHub public repository. https://github.com/JimmyKenMerchant/jimmy-codeviewer/

This Plugin uses several text domains. Names of shortcodes may conflict with shortcodes in other plugins. The name of post type, “jArticle” is considering its unique naming, but even “jArticle”, this name may conflict with other names. LATEX, a renowned digital document preparation system, uses “jarticle” as a Japanese document class. But I think, in WordPress, “jArticle” as one of post types is unique naming. Before activating this plugin, make sure to check naming conflict between this plugin and others. Embedded CSS in this plugin uses several names for HTML ids and classes, such as magazine-content. If you meet any naming conflict in whole HTML ids or classes in your page, change these names to save each unique naming. Changing names of ids and classes in style-codeviewer.css does not affect functions of shortcodes in this plugin.

This plugin wants encoding of the text is UTF-8, otherwise you meet empty return of HTML code. Setting of UTF-8 to mb_detect_encoding and mb_convert_encoding is useful. Plus, you can use UTF-8 as PHP default, e.g., set default_charset = UTF-8 in php.ini . You may need settings of Multibyte String Extension (php-mbstring) and more to fit UTF-8 encoding. Make sure to set UTF-8 in HTML, e.g., write <meta charset="UTF-8"> in head tag. In addition, MySQL’s Table charset needs utf8mb4 , collate needs utf8mb4_unicode_ci . UTF-8 is ultimatelly in-bytes format for Unicode. If you want to search raw Unicode, you may need utf-16 style Unicode such as /\x{2010}/u .