<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Digital Linguistics</title>
    <description>The latest articles on DEV Community by Digital Linguistics (@digitallinguistics).</description>
    <link>https://dev.to/digitallinguistics</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F4675%2F54ef51ea-5a86-45fd-9e87-890733fa049b.png</url>
      <title>DEV Community: Digital Linguistics</title>
      <link>https://dev.to/digitallinguistics</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/digitallinguistics"/>
    <language>en</language>
    <item>
      <title>Installing Finite-State Transducer (FST) tools on Windows</title>
      <dc:creator>Daniel W. Hieber</dc:creator>
      <pubDate>Sat, 04 Sep 2021 04:48:41 +0000</pubDate>
      <link>https://dev.to/digitallinguistics/installing-finite-state-transducer-fst-tools-on-windows-2l4n</link>
      <guid>https://dev.to/digitallinguistics/installing-finite-state-transducer-fst-tools-on-windows-2l4n</guid>
      <description>&lt;p&gt;Finite-state transducers (FSTs) are often used in linguistics to create morphological models of a language, which can both parse words in that language and return a morphological analysis, and accept a morphological analysis and produce a grammatically correct word. While FSTs and computational models sound complex, they're actually fairly straightforward! You don't need to have advanced computational skills. The most difficult part is in fact the grammatical analysis of the language rather than implementing that analysis as an FST. Any linguist can create an FST.&lt;/p&gt;

&lt;p&gt;In this post I'll show you how to install the two most common tools for creating FSTs—&lt;a href="https://fomafst.github.io/" rel="noopener noreferrer"&gt;foma&lt;/a&gt; and &lt;a href="http://hfst.github.io/" rel="noopener noreferrer"&gt;hfst&lt;/a&gt;—on Windows. (If you're on Mac or Linux, those links also have installation instructions for those platforms.)&lt;/p&gt;




&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Download foma by going to the &lt;a href="https://fomafst.github.io/" rel="noopener noreferrer"&gt;foma home page&lt;/a&gt; &amp;gt; &lt;code&gt;Precompiled binaries for Win32, OSX, Linux&lt;/code&gt; &amp;gt; &lt;code&gt;foma-X.X.X_win32.zip&lt;/code&gt; (where the X's are the latest version numbers).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Download hfst by going to the &lt;a href="http://hfst.github.io/" rel="noopener noreferrer"&gt;hfst home page&lt;/a&gt; &amp;gt; &lt;code&gt;download page&lt;/code&gt; &amp;gt; &lt;code&gt;win32 executables&lt;/code&gt; &amp;gt; &lt;code&gt;hfst-latest.zip&lt;/code&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Extract the zip file for both downloads.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Rename the folder in the foma download from &lt;code&gt;win32&lt;/code&gt; to &lt;code&gt;foma&lt;/code&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Move both extracted folders to &lt;code&gt;C:\Program Files (x86)&lt;/code&gt;, like so:&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;C:\Program Files (x86)\foma&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;C:\Program Files (x86)\hfst&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Next you need to make the foma and hfst commands available to run from the terminal / command line. Neither foma nor hfst have a graphical user interface, so you run them by opening a command line (press the Windows key, then type "command", and open the Command Prompt program that is shown) and typing simple text commands that begin with &lt;code&gt;foma&lt;/code&gt; or &lt;code&gt;hfst&lt;/code&gt;. At the moment, however, if you open a command line, no &lt;code&gt;foma&lt;/code&gt; or &lt;code&gt;hfst&lt;/code&gt; commands are available. So let's fix that:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Press the Windows key and type "path". One of the options should be "Edit the system environment variables"—open that. (If that option doesn't appear, search for "path" or "environment variables" in Settings.)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A &lt;code&gt;System Properties&lt;/code&gt; dialog box will open. Click &lt;code&gt;Environment Variables&lt;/code&gt; in the lower right.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;An &lt;code&gt;Environment Variables&lt;/code&gt; dialog box will open. Under &lt;code&gt;User variables for {username}&lt;/code&gt;, click on &lt;code&gt;Path&lt;/code&gt; and then click &lt;code&gt;Edit&lt;/code&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;You will now add the paths to the foma and hfst executables that you placed in Program Files earlier. Do this by clicking &lt;code&gt;New&lt;/code&gt; and adding a line for each. Note that for hfst you also need to add &lt;code&gt;\bin&lt;/code&gt; to the path, like so:&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;C:\Program Files (x86)\foma&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;C:\Program Files (x86)\hfst\bin&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The command line should now know about the existence of the &lt;code&gt;foma&lt;/code&gt; and &lt;code&gt;hfst&lt;/code&gt; commands and be able to run them. Let's check:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open a terminal / command line, type &lt;code&gt;foma -h&lt;/code&gt; and press Enter. You should see the following:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fh2jcdyrwdje0j7a2oead.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fh2jcdyrwdje0j7a2oead.png" alt="Help text returned by the foma command"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;-h&lt;/code&gt; flag stands for "help", and displays information about how to use foma. If you got the help text, it worked! The command line successfully recognized the &lt;code&gt;foma&lt;/code&gt; command.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Check for the &lt;code&gt;hfst&lt;/code&gt; command in a similar way: type &lt;code&gt;hfst-info&lt;/code&gt; and press enter, and you should get see information about the hfst software.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You're all set! You are now ready to begin creating and using finite-state transducers!&lt;/p&gt;

</description>
      <category>fst</category>
      <category>linguistics</category>
      <category>morphology</category>
      <category>computationalinguistics</category>
    </item>
    <item>
      <title>Adding citations to GitHub repositories</title>
      <dc:creator>Daniel W. Hieber</dc:creator>
      <pubDate>Sun, 15 Aug 2021 03:52:21 +0000</pubDate>
      <link>https://dev.to/digitallinguistics/adding-citations-to-github-repositories-1bic</link>
      <guid>https://dev.to/digitallinguistics/adding-citations-to-github-repositories-1bic</guid>
      <description>&lt;p&gt;Tucked away in &lt;a href="https://github.blog/2021-08-12-whats-new-from-github-changelog-july-2021-recap/#general-updates"&gt;GitHub's changelog for July&lt;/a&gt; is a nifty new feature that should thrill academics everywhere: the ability to add citation files to your repository, telling users how to cite your software or data.&lt;/p&gt;

&lt;p&gt;Now, if you add a &lt;code&gt;CITATION.cff&lt;/code&gt; file to the root of your repository in &lt;a href="https://citation-file-format.github.io/"&gt;Citation File Format&lt;/a&gt;, GitHub will automatically parse the information into APA and BibTeX formats and include a "Cite this repository" link in the &lt;strong&gt;About&lt;/strong&gt; sidebar.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/dwhieb/Old-Latin"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--uRbG55Ox--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ynjvrhqnbcjh6v2bnem8.png" alt="image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files"&gt;Check out the complete documentation on using GitHub citation files here.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Happy citing, and may your h-index always be high!&lt;/p&gt;

</description>
      <category>github</category>
      <category>citation</category>
      <category>academia</category>
      <category>research</category>
    </item>
  </channel>
</rss>
