﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Millisecond Forums » Millisecond Forums » Inquisit 6  » Extracting Codebook from Syntax</title><generator>InstantForum 2017-1 Final</generator><description>Millisecond Forums</description><link>https://forums.millisecond.com/</link><webMaster>Millisecond Forums</webMaster><lastBuildDate>Mon, 14 Sep 2026 11:43:49 GMT</lastBuildDate><ttl>20</ttl><item><title>Extracting Codebook from Syntax</title><link>https://forums.millisecond.com/Topic30783.aspx</link><description>We are working with several different Inquisit tasks, and for our lab's sake are looking to extract the codebooks from the syntax (user manual) into a separate document (word or text file). Is there a way to do this, or do I need to manually copy everything into a document?&lt;br/&gt;&lt;br/&gt;For reference, 'codebook' is in reference to the individual variables and their descriptions.&lt;br/&gt;EX:&lt;br/&gt;"blockcode, blocknum:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;the name and number of the current block (built-in Inquisit variable)"&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;Thanks!</description><pubDate>Wed, 10 Feb 2021 22:57:58 GMT</pubDate><dc:creator>SMCM</dc:creator></item><item><title>RE: Extracting Codebook from Syntax</title><link>https://forums.millisecond.com/Topic30784.aspx</link><description>&lt;blockquote data-id="30783" class="if-quote-wrapper" unselectable="on" data-guid="1612997597964" id="if_insertedNode_1612997597830" contenteditable="false"&gt;&lt;a class="quote-para" unselectable="on" style="display: none;" href="#" data-id="30783" title="Move Cursor Below" contenteditable="false"&gt;&lt;span unselectable="on"&gt;+&lt;/span&gt;&lt;/a&gt;&lt;a class="quote-delete" unselectable="on" style="display: none;" href="#" data-id="30783" title="Delete Quote" contenteditable="false"&gt;&lt;span unselectable="on"&gt;x&lt;/span&gt;&lt;/a&gt;&lt;span unselectable="on" class="quote-markup"&gt;[quote]&lt;/span&gt;&lt;div unselectable="on" class="if-quote-header" contenteditable="false"&gt;&lt;div unselectable="on" class="if-quote-toggle-wrapper"&gt;&lt;a class="if-quote-toggle quote-link" href="#" data-id="30783" title=" "&gt;&amp;nbsp;&lt;/a&gt;&lt;/div&gt;&lt;span unselectable="on" class="quote-markup"&gt;[b]&lt;/span&gt;SMCM - 2/10/2021&lt;span unselectable="on" class="quote-markup"&gt;[/b]&lt;/span&gt;&lt;/div&gt;&lt;div class="if-quote-message if-quote-message-30783"&gt;&lt;div class="if-quote-message-margin" contenteditable="true"&gt;We are working with several different Inquisit tasks, and for our lab's sake are looking to extract the codebooks from the syntax (user manual) into a separate document (word or text file). Is there a way to do this, or do I need to manually copy everything into a document?&lt;br/&gt;&lt;br/&gt;For reference, 'codebook' is in reference to the individual variables and their descriptions.&lt;br/&gt;EX:&lt;br/&gt;"blockcode, blocknum:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;the name and number of the current block (built-in Inquisit variable)"&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;Thanks!&lt;a class="if-quote-goto quote-link" href="#" data-id="30783"&gt;&lt;span class="goto"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;span unselectable="on" class="quote-markup"&gt;[/quote]&lt;/span&gt;&lt;/blockquote&gt;&lt;br/&gt;Inquisit script files (.iqx) are simple plain text files (encoding is UTF-8), so if you're fluent in Python or some other programming language, you could certainly write a quick script that automatically extracts the contents between the &amp;lt;usermanual&amp;gt; open and &amp;lt;/usermanual&amp;gt; close tags and copies them into some separate text file.&lt;br/&gt;</description><pubDate>Wed, 10 Feb 2021 22:57:58 GMT</pubDate><dc:creator>Dave</dc:creator></item></channel></rss>