I am migrating from (a very old) version 0.92.0 to 0.111.3 and I am seeing an issue with “highlighting”.
The (.md) code is the following:
* Changed the way the plugin gets registered to the VST3 world (implements the _main_ `GetPluginFactory()` function) with an easier and less error prone syntax:
{{< highlight cpp >}}
EXPORT_FACTORY Steinberg::IPluginFactory* PLUGIN_API GetPluginFactory()
{
return JambaPluginFactory::GetVST3PluginFactory<
pongasoft::test::jamba::RT::JambaTestPluginProcessor, // processor class (Real Time)
pongasoft::test::jamba::GUI::JambaTestPluginController // controller class (GUI)
>("pongasoft", // vendor
"https://www.pongasoft.com", // url
"support@pongasoft.com", // email
stringPluginName, // plugin name
FULL_VERSION_STR, // plugin version
Vst::PlugType::kFx // plugin category (can be changed to other like kInstrument, etc...)
);
}
{{< / highlight >}}
With 0.92.0, I get the proper/expected output (all whitespace is preserved):
Option 1: Indent the code to match the indentation of the shortcode tags
* Changed the way the plugin gets registered to the VST3 world (implements the _main_ `GetPluginFactory()` function) with an easier and less error prone syntax:
{{< highlight cpp >}}
EXPORT_FACTORY Steinberg::IPluginFactory* PLUGIN_API GetPluginFactory()
{
return JambaPluginFactory::GetVST3PluginFactory<
pongasoft::test::jamba::RT::JambaTestPluginProcessor, // processor class (Real Time)
pongasoft::test::jamba::GUI::JambaTestPluginController // controller class (GUI)
>("pongasoft", // vendor
"https://www.pongasoft.com", // url
"support@pongasoft.com", // email
stringPluginName, // plugin name
FULL_VERSION_STR, // plugin version
Vst::PlugType::kFx // plugin category (can be changed to other like kInstrument, etc...)
);
}
{{< / highlight >}}
Option 2: Use fenced code blocks
With fenced code blocks your markdown is portable (e.g., it renders correctly on GitHub, GitLab, etc.). Indent the code to match the indentation of the code fences.
* Changed the way the plugin gets registered to the VST3 world (implements the _main_ `GetPluginFactory()` function) with an easier and less error prone syntax:
```cpp
EXPORT_FACTORY Steinberg::IPluginFactory* PLUGIN_API GetPluginFactory()
{
return JambaPluginFactory::GetVST3PluginFactory<
pongasoft::test::jamba::RT::JambaTestPluginProcessor, // processor class (Real Time)
pongasoft::test::jamba::GUI::JambaTestPluginController // controller class (GUI)
>("pongasoft", // vendor
"https://www.pongasoft.com", // url
"support@pongasoft.com", // email
stringPluginName, // plugin name
FULL_VERSION_STR, // plugin version
Vst::PlugType::kFx // plugin category (can be changed to other like kInstrument, etc...)
);
}
```