{"id":2883,"date":"2026-10-02T06:42:36","date_gmt":"2026-10-02T06:42:36","guid":{"rendered":"https:\/\/blogs.inquirium.net\/inqscribe\/?p=2883"},"modified":"2026-10-02T06:42:36","modified_gmt":"2026-10-02T06:42:36","slug":"styling-text-with-markdown","status":"publish","type":"post","link":"https:\/\/blogs.inquirium.net\/inqscribe\/2026\/10\/02\/styling-text-with-markdown\/","title":{"rendered":"Styling Text with Markdown"},"content":{"rendered":"\n<p>One of our most requested features is text styling.  Transcription services sometimes require formatting. Researchers find it helpful to use styles for coding.  Writers find it useful for expression.<\/p>\n\n\n\n<p>While we have long considered adding support for text styling, we decided to keep InqScribe documents simple for a number of reasons, including performance, simplicity of interface, simplicity and universality of text storage formats across different operating systems, and ensuring that timecode formatting is distinctive and not lost relative to other styles.<\/p>\n\n\n\n<p>At the same time, we recognize that sometimes styles can be very helpful.  While InqScribe does not support styles directly, there is a simple free workaround: use Markdown.<\/p>\n\n\n\n<h2 id=\"markdown-is-a-simple-text-based-solution\">Markdown is a Simple Text-based Solution<\/h2>\n\n\n\n<p>Markdown is a text based format specification for defining text styles. <em> (See the original specification by John Gruber: <a rel=\"noreferrer noopener\" href=\"https:\/\/daringfireball.net\/projects\/markdown\/syntax\" target=\"_blank\">Markdown Syntax<\/a><\/em>.<em>)<\/em><\/p>\n\n\n\n<p>It&#8217;s an ingenious solution because it retains the simple text-based styling common in the early days of text-only email and is very intuitive and legible.  For example, <kbd>**this is bold text**<\/kbd>, this is <kbd>~strikethrough~<\/kbd>.  It also supports a number of standard features like bulleted lists, ordered lists, and URL links.<\/p>\n\n\n\n<p>So, to style your InqScribe transcript, you can just insert markdown codes.  For example, this is an InqScribe transcript with markdown formatting:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img loading=\"lazy\" src=\"https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-12.36.13-PM@2x-810x1024.png\" alt=\"\" class=\"wp-image-2886\" width=\"481\" height=\"608\" srcset=\"https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-12.36.13-PM@2x-810x1024.png 810w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-12.36.13-PM@2x-237x300.png 237w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-12.36.13-PM@2x-768x971.png 768w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-12.36.13-PM@2x.png 1036w\" sizes=\"(max-width: 481px) 100vw, 481px\" \/><\/figure>\n\n\n\n<p>The transcript is quite legible with simple styling.<\/p>\n\n\n\n<p>Of course, what we really want is visible styling.  For that, we can use an application that will render the markdown as visual styles.  While there are many applicaitons that can render markdown, one free widely available solution is Google Docs.<\/p>\n\n\n\n<h2 id=\"rendering-in-google-docs\">Rendering in Google Docs<\/h2>\n\n\n\n<p>Using Google Docs to render the markdown is pretty easy.<\/p>\n\n\n\n<ol><li>Open a new Google Doc<\/li><li>Make sure Markdown is enabled: <ol><li>Go to Tools &gt; Preferences<\/li><li>Check the box next to &#8220;<strong>Enable Markdown<\/strong>&#8220;<\/li><\/ol><\/li><li>In InqScribe, select and Copy the text<\/li><li>In Google Docs, select Edit &gt; <strong>Paste from Markdown<\/strong> (Note this the &#8220;Edit&#8221; menu inside of the Google Docs window, not your browser&#8217;s Edit menu)<\/li><\/ol>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img loading=\"lazy\" src=\"https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.39.00-AM@2x-1016x1024.png\" alt=\"\" class=\"wp-image-2884\" width=\"430\" height=\"433\" srcset=\"https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.39.00-AM@2x-1016x1024.png 1016w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.39.00-AM@2x-298x300.png 298w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.39.00-AM@2x-150x150.png 150w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.39.00-AM@2x-768x774.png 768w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.39.00-AM@2x-80x80.png 80w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.39.00-AM@2x.png 1034w\" sizes=\"(max-width: 430px) 100vw, 430px\" \/><\/figure>\n\n\n\n<p>Et voila: The text is rendered!<\/p>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img loading=\"lazy\" src=\"https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.46.34-AM@2x-685x1024.png\" alt=\"\" class=\"wp-image-2885\" width=\"495\" height=\"740\" srcset=\"https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.46.34-AM@2x-685x1024.png 685w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.46.34-AM@2x-201x300.png 201w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.46.34-AM@2x-768x1149.png 768w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.46.34-AM@2x-1027x1536.png 1027w, https:\/\/blogs.inquirium.net\/inqscribe\/wp-content\/uploads\/sites\/3\/2026\/09\/CleanShot-2026-09-28-at-11.46.34-AM@2x.png 1110w\" sizes=\"(max-width: 495px) 100vw, 495px\" \/><\/figure>\n\n\n\n<p>If you make some edits in Google Docs and then need to use it again in InqScribe&#8230;<\/p>\n\n\n\n<ol><li>In Google Docs select the text<\/li><li>Select Edit &gt; <strong>Copy as Markdown<\/strong> (Note this the &#8220;Edit&#8221; menu inside of the Google Doc browser window, not your browser&#8217;s Edit menu)<\/li><li>In InqScribe paste the text<\/li><\/ol>\n\n\n\n<p>All of your edits and the markdown text should be retained.<\/p>\n\n\n\n<h3 id=\"watch-out-for-delimiters\"><strong>Watch out for Delimiters<\/strong><\/h3>\n\n\n\n<p>If you need to do a round trip back to InqScribe (e.g. copy the markdown text from Google Docs back into InqScribe), you may need to address some delimiter issues that Google Docs introduces: Google Docs will try to use a &#8220;\/&#8221; to delimit time code square brackets &#8220;[&#8221; and &#8220;]&#8221;.<\/p>\n\n\n\n<p><strong>Workaround 1: Remove &#8220;\/&#8221;<\/strong><\/p>\n\n\n\n<p>One workaround is to simply do a search and replace for &#8220;\\&#8221; after pasting back into InqScribe.  e.g. the nice InqScribe transcript&#8230;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;00:01:25.14] You can **bold** text anywhere &#091;00:01:32.10]<\/code><\/pre>\n\n\n\n<p>&#8230;becomes cluttered with &#8220;\/&#8221; when pasted back into Google Docs like this&#8230;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\\&#091;00:01:25.14\\] You can **bold** text anywhere \\&#091;00:01:32.10\\]<\/code><\/pre>\n\n\n\n<p>Just do a search and replace to remove them.<\/p>\n\n\n\n<p><strong>Workaround 2: Use alternative timecode formats: () or {}<\/strong><\/p>\n\n\n\n<p>Another workaround is to use an alternative timecode format, e.g. parentheses () or curly brackets {}.  Google Docs will not introduce delimiters when copying markdown out of Google Docs.<\/p>\n\n\n\n<p>Another workaround would be to use another markdown application.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 id=\"alternatives-to-google-docs\">Alternatives to Google Docs<\/h2>\n\n\n\n<p>There are many many markdown-enabled applications, many of which will give you a live preview of the styled text, many are free.  A quick search will give you plenty of choices.<\/p>\n\n\n\n<p>Unfortunately Word does not seem to provide native Markdown support.<\/p>\n\n\n\n<p>Personally I like <a href=\"https:\/\/typora.io\" target=\"_blank\" rel=\"noreferrer noopener\">Typora<\/a> because of how it handles both an editable preview mode and a raw code view. (There is a free trial).  If you need to edit the markdown and then re-paste into InqScribe, copy and paste the raw markdown and Typora will not insert delimiters.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 id=\"tips-caveats\">Tips\/Caveats<\/h2>\n\n\n\n<p>Some things to watch out for:<\/p>\n\n\n\n<ul><li>Markdown formats are not quite standard.  You&#8217;ll find some variations across different applications, and some (like underline) are not standard and may not be supported at all, so you&#8217;ll need to test them to see how well they work.<\/li><li>For some editors, you may need to explicitly copy the text in markdown format for re-pasting into InqScribe.  This varies from tool to tool.  For instance, if there is a separate Raw Markdown and a Styled Preview, select the text from the Raw Markdown view.  Otherwise what is copied is styled text, which strips out the markdown codes.<\/li><li>If privacy is a major concern for you, the use of Google Docs can be problematic.  A desktop application where data does not leave your computer, (e.g. Typora) is one possible solution.<\/li><li>Since InqScribe documents are essentially text, you can of course introduce other coding styles and just copy and paste them into different viewers.  e.g. HTML, custom codes (&lt;laughs&gt;), etc.<\/li><\/ul>\n\n\n\n<p><\/p>\n\n\n\n<p>If you want to try it yourself, here&#8217;s some text that you can copy and paste into InqScribe and Google Docs:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Simple Markdown in InqScribe\n\n# Heading 1\n## Headling 2\n### Heading 3\n\n**bold**\n\n*italic*\n\n~strikethrough~\n\n&lt;u&gt;underline&lt;\/u&gt;\n\n\n* bulleted list\n1. ordered list\n\n&#091;link to InqScribe](https:\/\/www.inqscribe.com)\n\n\n&#091;00:01:25.14] You can **bold** text anywhere &#091;00:01:32.10]\n\n&#091;00:01:32.10] Even bulleted lists\n* will\n* work\n* anywhere\n&#091;00:01:33.12]\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<p>As always, please <a rel=\"noreferrer noopener\" href=\"https:\/\/www.inqscribe.com\/contact.html\" target=\"_blank\">Contact Us<\/a> with any questions or suggestions!  And tell your friends!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of our most requested features is text styling. Transcription services sometimes require formatting. Researchers find it helpful to use styles for coding. Writers find it useful for expression. While we have long considered adding support for text styling, we decided to keep InqScribe documents simple for a number of reasons, including performance, simplicity of&hellip;<\/p>\n","protected":false},"author":4,"featured_media":2888,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[11,12,13],"tags":[268,269,188,195,219],"_links":{"self":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts\/2883"}],"collection":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/comments?post=2883"}],"version-history":[{"count":3,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts\/2883\/revisions"}],"predecessor-version":[{"id":2895,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts\/2883\/revisions\/2895"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/media\/2888"}],"wp:attachment":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/media?parent=2883"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/categories?post=2883"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/tags?post=2883"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}