{"id":9316,"date":"2021-10-29T10:52:10","date_gmt":"2021-10-29T00:52:10","guid":{"rendered":"https:\/\/www.paradisec.org.au\/blog\/?p=9316"},"modified":"2021-10-29T14:13:14","modified_gmt":"2021-10-29T04:13:14","slug":"converting-docx-to-flex-format-for-dictionaries","status":"publish","type":"post","link":"https:\/\/www.paradisec.org.au\/blog\/2021\/10\/converting-docx-to-flex-format-for-dictionaries\/","title":{"rendered":"Converting docx to FLEx format for dictionaries"},"content":{"rendered":"\n

Following the previous blog post<\/a> I had requests for more detail on how to convert a word-processor dictionary into the format needed to put the text into the software Fieldworks Language Explorer (FLEx)<\/a>. I\u2019ll set out the steps below, but it does require some knowledge of regular expressions that I\u2019ll explain as I go (you can also watch an intro to regular expressions here<\/a>).<\/p>\n\n\n\n

What FLEx needs to import is a text file that has the dictionary parts marked up with codes, like this, where \\lx starts the headword, and \\de starts the definition:<\/p>\n\n\n\n

\\lx alata’a<\/p>\n\n\n\n

\\de speak straight-faced and unsmiling<\/p>\n\n\n\n

Subentries are marked with \\se, and scientific names are marked by \\sc. <\/p>\n\n\n\n

\"\"<\/figure>
\n

First, you have to analyse the dictionary file to see if it is formatted consistently. Make sure you can see the tab, space, and carriage return marks in the document, by clicking on the icon in the header that looks like the one to the left here. <\/p>\n<\/div><\/div>\n\n\n\n

For example, lots of entries look this :<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

The structure here is a word at the line start, followed by a tab, followed by other text (the English definition), followed by a carriage return. So far, so good. But, other lines look like this:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Here we have indented lines, with two spaces before the text. This is used to indicate subentries to the main entry.<\/p>\n\n\n\n

Another type of entry is as follows, where the definition extends beyond the end of the line and is wrapped, but with a tab to space it across to the right column:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

In some entries this wrapping can go for several lines:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Scientific names are given in italics and in brackets:<\/p>\n\n\n\n

‘ala’ala                croton (Codiaeum<\/em>)<\/p>\n\n\n\n

‘alabusi               type of tree (Acalypha<\/em>)<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>
\n

Because there is italic formatting here, we can find text with that formatting using MS Word\u2019s Advanced Find and Replace function to then insert codes. Leave the search box empty, but select the font style italic. This will search for all italic text. You have to replace the text with \\sc ^&. ^& means ‘put the thing I found here’, so it will put whatever text was in italics after \\sc.<\/p>\n<\/div><\/div>\n\n\n\n

\"\"<\/figure>
\n

This is what it looks like after doing that change, with \\sc inserted before an italic word. You need to take out the brackets around this, by finding “( \\ ” and replacing with \\, and finding “) ^p” and replacing with ^p.<\/p>\n<\/div><\/div>\n\n\n\n

Now, we need to find all carriage returns followed just by a tab, to find where the definition has gone longer than the end of the line. We will then replace that with a space.<\/p>\n\n\n\n

\"\"<\/figure>
\n


Again, using Advanced Find and Replace, you need to choose a paragraph mark from the special list at the bottom of the window. This will insert ^p into the search box. Similarly, now choose the tab character from the menu and it will put ^t into the search box. Put a single space into the replace box, and it will now replace all carriage returns followed by tabs to a single space. Do this as many times as it returns a result.<\/p>\n<\/div><\/div>\n\n\n\n

\"\"<\/figure>
\n

Now that we know all tabs only precede a definition, we can replace them with \\de , and we do this the same way, by finding ^t and replacing with \\de (with a space following it).<\/p>\n<\/div><\/div>\n\n\n\n

\"\"<\/figure>
\n

Next, we can identify subentries as having two spaces at the beginning of a line, so we can look for “^p ” (that is, ^p followed by two spaces), and replace it with “\\se “<\/p>\n<\/div><\/div>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>
\n

Now all remaining carriage returns occur before a headword, so can all be replaced by themselves with “\\lx ” which is the marker for the headword.<\/p>\n<\/div><\/div>\n\n\n\n

\"\"<\/figure>
\n

Last, you can put a carriage return before each backslash to create the format needed by FLEx. The last thing is to save this file as plain text.<\/p>\n<\/div><\/div>\n\n\n\n

You can now import that file into FLEx.<\/p>\n","protected":false},"excerpt":{"rendered":"

Following the previous blog post I had requests for more detail on how to convert a word-processor dictionary into the format needed to put the text into the software Fieldworks Language Explorer (FLEx). I\u2019ll set out the steps below, but it does require some knowledge of regular expressions that I\u2019ll explain as I go (you … Read more<\/a><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[79,3],"tags":[55,97],"class_list":["post-9316","post","type-post","status-publish","format-standard","hentry","category-dictionaries","category-technology","tag-dictionary","tag-regular-expressions"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts\/9316","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/comments?post=9316"}],"version-history":[{"count":12,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts\/9316\/revisions"}],"predecessor-version":[{"id":9346,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts\/9316\/revisions\/9346"}],"wp:attachment":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/media?parent=9316"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/categories?post=9316"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/tags?post=9316"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}