menu
Tatoeba
language
Register Log in
language English
menu
Tatoeba

chevron_right Register

chevron_right Log in

Browse

chevron_right Show random sentence

chevron_right Browse by language

chevron_right Browse by list

chevron_right Browse by tag

chevron_right Browse audio

Community

chevron_right Wall

chevron_right List of all members

chevron_right Languages of members

chevron_right Native speakers

search
clear
swap_horiz
search
gillux gillux March 27, 2020 March 27, 2020 at 6:30:37 AM UTC link Permalink

I am publishing a new UX test: https://en.wiki.tatoeba.org/art...show/ux-test-4 This time I’ve performed the test on somebody who is very familiar with Tatoeba already, so I don’t know if I can really call it a UX test. That said, it contains relevant feedback, including about the use of Tatoeba in a teaching environment.

{{vm.hiddenReplies[34618] ? 'expand_more' : 'expand_less'}} hide replies show replies
rumpelstilzchen rumpelstilzchen March 27, 2020 March 27, 2020 at 6:05:08 PM UTC link Permalink

Thanks for another UX test.

Just a quick comment:
> Having the list as a DOC file would be useful to R. because he can freely edit the text. Currently, he has to copy and paste sentences from the CSV file into a Word document to edit them the way he wants.

I don't use Word (or any word processor) so this may be a strange question, but why can't Word open/import the csv file? This is a simple plain text file.

{{vm.hiddenReplies[34623] ? 'expand_more' : 'expand_less'}} hide replies show replies
Guybrush88 Guybrush88 March 27, 2020, edited March 27, 2020 March 27, 2020 at 9:25:19 PM UTC, edited March 27, 2020 at 9:33:03 PM UTC link Permalink

Sometimes I tried to open the csv file with the exported sentences with Libreoffice (the import feature was still working, and I used the exported file to grab the sentences I wanted to mass translate more quickly), and the software always told me that the file was too big and not everything was shown. Using gedit (on Linux) and Notepad++ (on Windows) worked for my purpose, since they showed all the sentences

{{vm.hiddenReplies[34626] ? 'expand_more' : 'expand_less'}} hide replies show replies
Yorwba Yorwba March 27, 2020 March 27, 2020 at 9:58:24 PM UTC link Permalink

Putting all the exported sentences into a single .DOC file would probably make Word choke, but the excerpt from the UX test report is specifically about exporting lists, where file size is less likely to be a problem.

gillux gillux March 28, 2020 March 28, 2020 at 7:29:14 AM UTC link Permalink

I think nothing’s preventing Word from opening the CSV file as plain text, however I assume the file extension CSV is associated with Excel, so opening it with Word is rather counter-intuitive. I imagine users have to right click → "open with", and then find Word from whatever selection box pops up. Compare this with simply double-clicking on the file.

As pointed out in the test, most users are not familiar with the CSV format to begin with, so they don’t know whether they should open it with Word, Excel of whatever.

To put it another way: of course, if you have the knowledge and the skills you can do whatever you want with whatever file format.

{{vm.hiddenReplies[34628] ? 'expand_more' : 'expand_less'}} hide replies show replies
rumpelstilzchen rumpelstilzchen March 28, 2020 March 28, 2020 at 12:30:27 PM UTC link Permalink

> As pointed out in the test, most users are not familiar with the CSV format to begin with, so they don’t know whether they should open it with Word, Excel of whatever.

So should we add some info text about how to open the file in a word processor? Or change the file extension to TXT?