Ruby Markup Converter

By Foriba

0+ active installationsVersion 1.3.0

Converts ruby and emphasis mark notation from Japanese novel-sharing sites for WordPress, without modifying the original text.

Description

Want to Publish Your Manuscripts Written for Japanese Novel-Sharing Sites on WordPress, Too?

Ruby Markup Converter is a plugin that automatically converts ruby (furigana) and emphasis mark (bouten) notation used on Japanese novel-sharing sites and elsewhere into a format that displays correctly in WordPress, without modifying the original text.

Simply copy and paste your manuscript from a text file. There’s no need to add ruby annotations or emphasis marks one by one. Of course, you can also type the same notation directly into the WordPress editor.

Key Features

  • Convert by category or by post: Select a category to convert every post in it, or choose for each post and page whether to convert it. No need to add blocks to each post.
  • Use your original manuscripts as they are: Supported ruby and bouten notation is converted automatically, so there’s no need to rewrite your text.
  • Easy to use: Simply paste your manuscript into a post in a selected category, or into the Ruby Markup Converter block.
  • Choose where to convert: Convert only part of a post with a dedicated block, or convert all posts and pages.
  • Flexible settings: Enable or disable individual markup rules and choose how bouten marks are displayed.

Support for Languages Other Than Japanese

Although Ruby Markup Converter is designed with Japanese typography and novel-writing conventions in mind, it is not limited to Japanese. Text in other languages can also be converted as long as it follows the supported markup rules.

Supported Markup Styles

  • Ruby:

    • |BaseText《RubyAnnotation》
    • BaseText《RubyAnnotation》
    • BaseText(RubyAnnotation)
    • [[rb:BaseText > RubyAnnotation]]
    • #BaseText__RubyAnnotation__#
    • {{ruby|BaseText|RubyAnnotation}}
  • Bouten (Emphasis):

    • 《《Emphasis》》

Usage

Ruby Markup Converter offers several ways to choose where ruby and bouten notation is converted:

By Category

Open Posts > Categories, edit a category, and check the Ruby Markup Converter option. The full text of posts in that category and its child categories is converted.

By Post or Page

In the block editor, open the Ruby Markup Converter panel in the sidebar. You can convert the full text of that post or page, or turn conversion off for it, regardless of other settings.

Ruby Markup Converter Block

Add the Ruby Markup Converter block to a post or page, then paste or type your text inside it. Supported notation within the block is converted when the content is displayed.

Shortcode

Wrap your text in [rubymaco]...[/rubymaco] to convert supported notation within that section. This method is also available in the Classic Editor.

Entire Post Content

Enable Apply to Entire Post Content in the plugin settings to convert supported notation throughout all posts and pages, except those set not to be converted.

Documentation

For detailed instructions, examples, configuration options, and troubleshooting, see the Ruby Markup Converter User Guide.

Installation

  1. Install the plugin using the built-in WordPress plugin installer, or manually upload the extracted files to the wp-content/plugins/ directory.
  2. Activate the plugin through the Plugins menu in WordPress.
  3. Go to Settings > Ruby Markup Converter.
  4. Select the conversion scope and markup rules you want to use.
  5. Save your settings.

FAQ

Can I choose which markup styles to convert?

Yes. You can enable or disable each supported ruby and bouten markup rule individually in the plugin settings. You can also choose the bouten style and rendering method.

Can I exclude a specific post from conversion?

Yes. In the block editor, choose not to convert the post in the Ruby Markup Converter panel in the sidebar. Content inside Ruby Markup Converter blocks and shortcodes in that post is not converted either.

What happens when I uninstall the plugin?

Uninstalling the plugin removes its saved settings, including the category and post conversion settings, but does not delete or modify your posts or pages. Ruby and bouten notation remains in the original text and is no longer converted. Any manually written [rubymaco]...[/rubymaco] shortcode tags also remain visible.

Screenshots

Changelog

1.3.0

  • Added an option to convert the full text of posts in selected categories.
  • Added per-post and per-page conversion settings in the block editor.
  • Fixed some kanji, such as 𠮟 and 﨑, not being recognized as base text in ruby notation without an explicit base text.
  • Fixed shortcodes nested inside [rubymaco]…[/rubymaco] not being processed.
  • Fixed settings failing to save after the settings screen had been left open for a long time.
  • Improved conversion performance, especially for long posts.
  • Fixed typos and improved overall stability.

1.2.0

  • Redesigned the settings screen for easier navigation and configuration.
  • Improved feedback when saving settings or making changes.
  • Moved the custom bouten rendering option to Compatibility Settings.
  • Improved internal reliability while preserving existing settings and conversion behavior.
  • Corrected the documentation to remove an inaccurate statement about built-in ruby support in WordPress.

1.1.0

  • Added the Ruby Markup Converter block for easier use in the block editor.
  • Changed the default bouten rendering method to CSS text-emphasis.
  • Prevented markup conversion inside HTML tags and attributes to avoid potential display issues.
  • Fixed bouten markup immediately following kanji being incorrectly interpreted as ruby markup.
  • Fixed incorrect display of ampersands when using the custom bouten renderer.
  • Fixed an issue where disabling all markup rules caused the settings to revert to their defaults.
  • Updated the minimum required WordPress version to 6.8.

1.0.1

  • Improved internal settings management.

1.0.0

  • Initial public release.