<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>Novaworks Weblog - Development</title>
    <link>http://www.novaworkssofware.com/blog/</link>
    <description>Novaworks current activity</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 2.4.0 - http://www.s9y.org/</generator>
    <pubDate>Fri, 07 Feb 2025 16:34:14 GMT</pubDate>

    <image>
    <url>http://www.novaworkssofware.com/blog/templates/novaworks/img/s9y_banner_small.png</url>
    <title>RSS: Novaworks Weblog - Development - Novaworks current activity</title>
    <link>http://www.novaworkssofware.com/blog/</link>
    <width>100</width>
    <height>21</height>
</image>

<item>
    <title>SEC Announces Interim Release 25.0.1 for EDGAR System</title>
    <link>http://www.novaworkssofware.com/blog/archives/1522-SEC-Announces-Interim-Release-25.0.1-for-EDGAR-System.html</link>
            <category>Development</category>
            <category>EDGAR News</category>
            <category>SEC</category>
            <category>SEC Filing Help</category>
            <category>XBRL</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/1522-SEC-Announces-Interim-Release-25.0.1-for-EDGAR-System.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=1522</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=1522</wfw:commentRss>
    

    <author>nospam@example.com (LeAnn Dey)</author>
    <content:encoded>
    On February 3rd, the EDGAR system was upgraded with interim release 25.0.1, and it now supports the 2024q3 version of the Fund (FND) taxonomy. The 2024q3 version of the FND taxonomy will now include the requisite update for compatibility with the 2024q3 version of the Open-End Fund (OEF) taxonomy enabling filers to use both taxonomies in one filing, and provide the elements for tagging disclosures related to the SEC&amp;rsquo;s rulemaking regarding enhanced prospectus disclosure requirements for terminology used in fund names. &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/1522-SEC-Announces-Interim-Release-25.0.1-for-EDGAR-System.html#extended&quot;&gt;Continue reading &quot;SEC Announces Interim Release 25.0.1 for EDGAR System&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Tue, 04 Feb 2025 17:49:00 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/1522-guid.html</guid>
    
</item>
<item>
    <title>XBRLworks Scheduled Maintenance</title>
    <link>http://www.novaworkssofware.com/blog/archives/1007-XBRLworks-Scheduled-Maintenance.html</link>
            <category>Development</category>
            <category>FERC Filing Help</category>
            <category>XBRLworks Updates</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/1007-XBRLworks-Scheduled-Maintenance.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=1007</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=1007</wfw:commentRss>
    

    <author>nospam@example.com (The Novaworks Team)</author>
    <content:encoded>
    XBRLworks will be unavailable during scheduled maintenance today, August 26th, from 3:00 p.m. to 6:00 p.m. ET. During this time, the application will be updated to version 1.2a. &lt;font style=&quot;display: none&quot;&gt;{expires: 2022-08-29}&lt;/font&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/1007-XBRLworks-Scheduled-Maintenance.html#extended&quot;&gt;Continue reading &quot;XBRLworks Scheduled Maintenance&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 26 Aug 2022 13:10:18 -0400</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/1007-guid.html</guid>
    
</item>
<item>
    <title>XBRLworks Scheduled Maintenance</title>
    <link>http://www.novaworkssofware.com/blog/archives/964-XBRLworks-Scheduled-Maintenance.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/964-XBRLworks-Scheduled-Maintenance.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=964</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=964</wfw:commentRss>
    

    <author>nospam@example.com (The Novaworks Team)</author>
    <content:encoded>
    XBRLworks will be unavailable during scheduled maintenance today, May 20th, from 4:00 p.m. to 7:00 p.m. ET. During this time, the application will be updated to version 1.1d. &lt;font style=&quot;display: none&quot;&gt;{expires: 2022-05-21}&lt;/font&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/964-XBRLworks-Scheduled-Maintenance.html#extended&quot;&gt;Continue reading &quot;XBRLworks Scheduled Maintenance&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 20 May 2022 14:12:59 -0400</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/964-guid.html</guid>
    
</item>
<item>
    <title>SEC Revises Notification for EDGAR Cipher Update</title>
    <link>http://www.novaworkssofware.com/blog/archives/877-SEC-Revises-Notification-for-EDGAR-Cipher-Update.html</link>
            <category>Development</category>
            <category>EDGAR News</category>
            <category>Information Technology</category>
            <category>SEC</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/877-SEC-Revises-Notification-for-EDGAR-Cipher-Update.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=877</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=877</wfw:commentRss>
    

    <author>nospam@example.com (LeAnn Dey)</author>
    <content:encoded>
    &lt;P STYLE=&quot;margin: 0&quot;&gt;As a reminder, the SEC is  updating the ciphers it supports in its Transport Layer Security (TLS) cryptographic protocol on Monday, January 17, 2022. The upcoming upgrade was previously announced on August 25, 2021 and October 27, 2021.&lt;/P&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/877-SEC-Revises-Notification-for-EDGAR-Cipher-Update.html#extended&quot;&gt;Continue reading &quot;SEC Revises Notification for EDGAR Cipher Update&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 14 Jan 2022 09:20:00 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/877-guid.html</guid>
    
</item>
<item>
    <title>LDC #170: Adding Dot Fill Leaders With Embedded Images</title>
    <link>http://www.novaworkssofware.com/blog/archives/545-LDC-170-Adding-Dot-Fill-Leaders-With-Embedded-Images.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/545-LDC-170-Adding-Dot-Fill-Leaders-With-Embedded-Images.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=545</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=545</wfw:commentRss>
    

    <author>nospam@example.com (Steven Horowitz)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;One common request I get from clients is that they want to add dot leaders to some kinds of tables. Dot leaders are pretty common and also look great in documents but are also deceptively difficult to do in HTML. With regular typesetting software, you can fill white space with periods or other characters using a variety of methods that are relatively easy to employ. Typeset documents have set widths and fonts that don&amp;rsquo;t vary depending on external factors. HTML, on the other hand, is highly dependent on a user&amp;rsquo;s viewport settings.&lt;/p&gt;&lt;br /&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/545-LDC-170-Adding-Dot-Fill-Leaders-With-Embedded-Images.html#extended&quot;&gt;Continue reading &quot;LDC #170: Adding Dot Fill Leaders With Embedded Images&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Tue, 16 Jun 2020 18:02:45 -0400</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/545-guid.html</guid>
    
</item>
<item>
    <title>LDC #169: Adding New Functionality To Older Scripts</title>
    <link>http://www.novaworkssofware.com/blog/archives/528-LDC-169-Adding-New-Functionality-To-Older-Scripts.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/528-LDC-169-Adding-New-Functionality-To-Older-Scripts.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=528</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=528</wfw:commentRss>
    

    <author>nospam@example.com (Steven Horowitz)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;Back in 2017, I wrote a post about a script that would&lt;a href=&quot;https://www.novaworkssoftware.com/blog/archives/173-LDC-48-Improved-Align-Outline-Text-Function.html&quot;&gt; align outline text&lt;/a&gt;, which would insert spacers into a formatted outline document to make it consistently spaced. This script has been in use for a few years by a few readers of this blog, and it generally works pretty well, but earlier this week I got a question about it. If a document is otherwise nicely formatted, and you only want to align a section of the document, running the script on an entire document is probably a bad idea, because there is always the possibility of it changing something that already looks pretty good. The question, then, was asking if it was possible to modify this script to run on a portion of the document, instead of the whole document.&lt;/p&gt;&lt;br /&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/528-LDC-169-Adding-New-Functionality-To-Older-Scripts.html#extended&quot;&gt;Continue reading &quot;LDC #169: Adding New Functionality To Older Scripts&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 24 Apr 2020 17:04:00 -0400</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/528-guid.html</guid>
    
</item>
<item>
    <title>LDC #168: Reading JSON with Legato</title>
    <link>http://www.novaworkssofware.com/blog/archives/495-LDC-168-Reading-JSON-with-Legato.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/495-LDC-168-Reading-JSON-with-Legato.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=495</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=495</wfw:commentRss>
    

    <author>nospam@example.com (David Theis)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;With the latest version of the GoFiler family of products, the ability to natively read JSON files has been added to Legato. In this week&amp;rsquo;s blog, we will discuss the new JSON functions and how they can be used. Keep in mind that you must be using version 5.3a or later of GoFiler or version 1.2i of Legato Basic in order to run the examples from this blog. Also this blog explores some very basic Javascript; knowledge of Javascript may be helpful.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/495-LDC-168-Reading-JSON-with-Legato.html#extended&quot;&gt;Continue reading &quot;LDC #168: Reading JSON with Legato&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 16 Mar 2020 10:22:28 -0400</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/495-guid.html</guid>
    
</item>
<item>
    <title>LDC #167: A Quick Web Link Builder Part II</title>
    <link>http://www.novaworkssofware.com/blog/archives/483-LDC-167-A-Quick-Web-Link-Builder-Part-II.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/483-LDC-167-A-Quick-Web-Link-Builder-Part-II.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=483</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=483</wfw:commentRss>
    

    <author>nospam@example.com (The Novaworks Team)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;Last month I described a tool I built to create and insert web news links in my blog, &amp;ldquo;A Quick Web Link Builder&amp;rdquo;. I recently expanded the functionality to load the web page and extract information to load link information into the dialog, thus making linking an even quicker process.&lt;/p&gt;&lt;br /&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/483-LDC-167-A-Quick-Web-Link-Builder-Part-II.html#extended&quot;&gt;Continue reading &quot;LDC #167: A Quick Web Link Builder Part II&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 28 Feb 2020 17:12:00 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/483-guid.html</guid>
    
</item>
<item>
    <title>LDC #166: Forcing a Subject Company Name Lookup For 13D/G Filings</title>
    <link>http://www.novaworkssofware.com/blog/archives/479-LDC-166-Forcing-a-Subject-Company-Name-Lookup-For-13DG-Filings.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/479-LDC-166-Forcing-a-Subject-Company-Name-Lookup-For-13DG-Filings.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=479</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=479</wfw:commentRss>
    

    <author>nospam@example.com (Steven Horowitz)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;This week, we&amp;rsquo;re taking a look at automating the subject company lookup on SC13D/G filings. This is another request from a client, but I think it provides a good opportunity to look at automation of a pretty simple task that otherwise might be forgotten and overlooked by a busy operator. This script will trigger when a user opens a project file (a .GFP file), if and only if the project being opened is of document type SC 13D or SC 13G. These are the best kinds of tasks to automate, because they are specific, and easily forgotten by an operator. If the document opened meets these criteria, the CIK of the subject company will be looked up, and the name of the subject company will be looked up on the EDGAR system and entered into the name field. This is very useful if you have an automated system that is creating .GFP files (not very hard, it&amp;rsquo;s a pretty simple file format), but you cannot guarantee that system has access to the most current names of companies. For example, if the system generating the GFP files has an outdated database of names, you would want to make sure that the subject company is replaced with current information on file open. This is where our script comes in.&lt;/p&gt;&lt;br /&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/479-LDC-166-Forcing-a-Subject-Company-Name-Lookup-For-13DG-Filings.html#extended&quot;&gt;Continue reading &quot;LDC #166: Forcing a Subject Company Name Lookup For 13D/G Filings&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 07 Feb 2020 17:57:00 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/479-guid.html</guid>
    
</item>
<item>
    <title>LDC #165: A Quick Web Link Builder</title>
    <link>http://www.novaworkssofware.com/blog/archives/472-LDC-165-A-Quick-Web-Link-Builder.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/472-LDC-165-A-Quick-Web-Link-Builder.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=472</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=472</wfw:commentRss>
    

    <author>nospam@example.com (The Novaworks Team)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;While the Novaworks tools are principally used for EDGAR, sometimes there are non-EDGAR things to do. One of my activities is maintaining a website for a not-for-profit group supporting amateur radio. As part of my duties, the front page of the site has a section on recent non-club news which requires me to perform a little research and then add the links to the page. This script helps reduce the time to create the links.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/472-LDC-165-A-Quick-Web-Link-Builder.html#extended&quot;&gt;Continue reading &quot;LDC #165: A Quick Web Link Builder&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 24 Jan 2020 17:16:57 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/472-guid.html</guid>
    
</item>
<item>
    <title>LDC #164: Validating Project Files Have XBRL</title>
    <link>http://www.novaworkssofware.com/blog/archives/469-LDC-164-Validating-Project-Files-Have-XBRL.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/469-LDC-164-Validating-Project-Files-Have-XBRL.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=469</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=469</wfw:commentRss>
    

    <author>nospam@example.com (Steven Horowitz)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;This week, we&amp;rsquo;re taking another look at using Legato to enhance GoFiler&amp;rsquo;s validation. Last month, someone asked me if there was a way GoFiler could check a 10-Q project to ensure a completed XBRL file set was attached to it. Well, this isn&amp;rsquo;t something GoFiler normally checks for (since there are times when you might want to omit these files), but we can definitely use Legato to enhance the validation of the project file, so we can warn the user if they might have forgotten something. It also gives us another opportunity to demonstrate some of the project file functions, which are always useful if you&amp;rsquo;re going to be working with GFP files.&lt;/p&gt;&lt;br /&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/469-LDC-164-Validating-Project-Files-Have-XBRL.html#extended&quot;&gt;Continue reading &quot;LDC #164: Validating Project Files Have XBRL&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 10 Jan 2020 17:25:43 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/469-guid.html</guid>
    
</item>
<item>
    <title>LDC #163: Tracking Time in Legato</title>
    <link>http://www.novaworkssofware.com/blog/archives/464-LDC-163-Tracking-Time-in-Legato.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/464-LDC-163-Tracking-Time-in-Legato.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=464</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=464</wfw:commentRss>
    

    <author>nospam@example.com (David Theis)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;For this week&amp;rsquo;s blog post we are going to discuss tracking elapsed time in Legato. Like many things in Legato, there are a number of different ways to accomplish this task, each with their pros and cons. Many of these functions have appeared in other scripts we&amp;rsquo;ve previously posted but this article will be a more in-depth look at these functions.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/464-LDC-163-Tracking-Time-in-Legato.html#extended&quot;&gt;Continue reading &quot;LDC #163: Tracking Time in Legato&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 27 Dec 2019 16:05:59 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/464-guid.html</guid>
    
</item>
<item>
    <title>LDC #162: An Introduction to Quick Keys</title>
    <link>http://www.novaworkssofware.com/blog/archives/458-LDC-162-An-Introduction-to-Quick-Keys.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/458-LDC-162-An-Introduction-to-Quick-Keys.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=458</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=458</wfw:commentRss>
    

    <author>nospam@example.com (The Novaworks Team)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;Everyone has their favorite quick keys. It you have been working in MS Word for a long time, you are probably used to pressing&lt;b&gt;&lt;i&gt; Ctrl&lt;/i&gt;+E&lt;/b&gt; or&lt;b&gt;&lt;i&gt; Ctrl&lt;/i&gt;+R&lt;/b&gt; to center or right align text. In GoFiler, the corresponding keys are&lt;b&gt;&lt;i&gt; F6&lt;/i&gt;&lt;/b&gt; and&lt;b&gt;&lt;i&gt; F8&lt;/i&gt;&lt;/b&gt;, respectively. But what if you want to change the quick keys in GoFiler? In this blog, I will begin to explore quick keys and the foundation of how GoFiler processes them. The next blog will explain how Legato can be used to modify quick keys. In the end, you as a Legato programmer should understand how to use and alter quick keys to best suit your own particular needs.&lt;/p&gt;&lt;br /&gt;
 &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/458-LDC-162-An-Introduction-to-Quick-Keys.html#extended&quot;&gt;Continue reading &quot;LDC #162: An Introduction to Quick Keys&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 16 Dec 2019 14:33:12 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/458-guid.html</guid>
    
</item>
<item>
    <title>LDC #161: Quickly Adding CSS Classes to an Existing HTML Document</title>
    <link>http://www.novaworkssofware.com/blog/archives/451-LDC-161-Quickly-Adding-CSS-Classes-to-an-Existing-HTML-Document.html</link>
            <category>Development</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/451-LDC-161-Quickly-Adding-CSS-Classes-to-an-Existing-HTML-Document.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=451</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=451</wfw:commentRss>
    

    <author>nospam@example.com (Scott Theis)</author>
    <content:encoded>
    &lt;p style=&quot;margin: 0&quot;&gt;In the EDGAR world, inline CSS can be used to style documents. However, CSS style sheets are not allowed. I recently ran into a case where document needed to be published on a system which was just the opposite &amp;mdash; CSS classes are ok, but inline styles are verboten. A quick Legato script saved may hours of work by translating the inline styles to a style sheet.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/451-LDC-161-Quickly-Adding-CSS-Classes-to-an-Existing-HTML-Document.html#extended&quot;&gt;Continue reading &quot;LDC #161: Quickly Adding CSS Classes to an Existing HTML Document&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Mon, 25 Nov 2019 10:23:12 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/451-guid.html</guid>
    
</item>
<item>
    <title>XBRL US Releases Taxonomy Development Handbook for Public Comment</title>
    <link>http://www.novaworkssofware.com/blog/archives/450-XBRL-US-Releases-Taxonomy-Development-Handbook-for-Public-Comment.html</link>
            <category>Development</category>
            <category>Filing Technology</category>
            <category>XBRL</category>
    
    <comments>http://www.novaworkssofware.com/blog/archives/450-XBRL-US-Releases-Taxonomy-Development-Handbook-for-Public-Comment.html#comments</comments>
    <wfw:comment>http://www.novaworkssofware.com/blog/wfwcomment.php?cid=450</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.novaworkssofware.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=450</wfw:commentRss>
    

    <author>nospam@example.com (The Novaworks Team)</author>
    <content:encoded>
    &lt;P STYLE=&quot;margin: 0&quot;&gt;On November 19th, XBRL US released the &lt;I&gt;Taxonomy Development Handbook&lt;/I&gt; for public review. The handbook is a comprehensive guide that directs regulators, industry experts, and businesses through a practical roadmap to building high quality data standards with XBRL. This freely available, foundational document takes readers through the necessary stages of standards development, including: 1) building the appropriate transport data model, 2) assessing project scope, including use cases and requirements, 3) establishing a governance structure, 4) documenting the standards program, and 5) the step-by-step mechanics of building the taxonomy. The handbook also contains an introduction to the XBRL financial data standard, templates to guide developers in documenting the taxonomy, and case studies of XBRL as a method of improving data reporting in various industries.&lt;/P&gt; &lt;a class=&quot;block_level&quot; href=&quot;http://www.novaworkssofware.com/blog/archives/450-XBRL-US-Releases-Taxonomy-Development-Handbook-for-Public-Comment.html#extended&quot;&gt;Continue reading &quot;XBRL US Releases Taxonomy Development Handbook for Public Comment&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 22 Nov 2019 10:49:47 -0500</pubDate>
    <guid isPermaLink="false">http://www.novaworkssofware.com/blog/archives/450-guid.html</guid>
    
</item>

</channel>
</rss>
