Closed darcywong00 closed 2 years ago
@terrygibbs pointed out that there is an option to export SFM as Rows.
which exports as rows with a space separating the entries.
Can we replace the autogenerated space with an autogenerated comma ( , ). We could then open the output as a csv file and edit as required in excel.
wow, I didn't know about that option, but that would seem to make this task MUCH easier - thanks Scott and Terry!
On Tue, Mar 22, 2022 at 4:02 PM sdysart @.***> wrote:
Terry G. pointed out that there is an option to export SFM as Rows. [image: image] https://user-images.githubusercontent.com/26537840/159444279-bd252b72-10f7-419e-85e2-b4f3f7b63e9d.png which exports as rows with a space separating the entries. Can we replace the autogenerated space with an autogenerated comma ( , ). We could then open the output as a csv file and edit as required in excel.
— Reply to this email directly, view it on GitHub https://github.com/sillsdev/SpeechAnalyzer/issues/74#issuecomment-1074903484, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2I6KMLZF3BHDR5BACUIWDVBGEARANCNFSM5RKALMHQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
@sdysart is supporting some users who are converting wordlists from SA into Cog. Currently, Cog is expecting .csv files in the format: row 1 - glosses separated by commas row 2 - secondary field (IPA?)
Workaround
@sdysart starts with SA exporting to Fieldworks SFM. Then, he's applying a regex in Notepad++ to create CSV (data in column 1 and column 2). Then, he's applying a Google sheet transpose to get the data into 2 rows.