You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for all you work on quanteda. LIWC released a new version of their software in May that uses a new format for their dictionary files with a new extension (.dicx). The format is similar so I hope it won't be too difficult to support it with the dictionary() command. I've copied an example of the code format below [first Github post so apologies if anything is off with this post].
#Original format (.dic)
%
1Correct2Incorrect
%
rope*1candlestick*2candlestick2pistol*2knife2knives2pipe*2#New format (.dicx)Entry,Correct,Incorrectrope*,1,
candlestick*,,1candlestick*,,1knife,,1knives,,1pipe*,,1pistol*,,1
Use case
LIWC 2022 offers a very handy dictionary building tool but it only exports into .dicx.
The text was updated successfully, but these errors were encountered:
Thanks - I will get on this asap. I hadn't realised they just issued a new release. Looks like I will need to purchase a license for the new version.
In the dictionary format, it looks like they went in their format from really bad to slightly bad. Why are we the only ones suggesting something sensible like a YAML format?
Requested feature
Thank you for all you work on quanteda. LIWC released a new version of their software in May that uses a new format for their dictionary files with a new extension (.dicx). The format is similar so I hope it won't be too difficult to support it with the dictionary() command. I've copied an example of the code format below [first Github post so apologies if anything is off with this post].
Use case
LIWC 2022 offers a very handy dictionary building tool but it only exports into .dicx.
The text was updated successfully, but these errors were encountered: