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
TRANG TRANG September 10, 2016, edited September 10, 2016 September 10, 2016 at 2:29:31 PM UTC, edited September 10, 2016 at 2:29:47 PM UTC link Permalink

** Tatoeba update **

In preparation of tomorrow's update, if you have a bit of time, please test the dev website.
https://dev.tatoeba.org

Changes in this update are listed here:
https://github.com/Tatoeba/tatoeba2/milestone/116

Thank you!


P.S. I've also posted an update about the UI migration for anyone who's interested about how it is progressing and what will come next: https://github.com/Tatoeba/tatoeba2/issues/1180

{{vm.hiddenReplies[27200] ? 'expand_more' : 'expand_less'}} hide replies show replies
Wezel Wezel September 10, 2016 September 10, 2016 at 2:46:33 PM UTC link Permalink

In the edit mode (after clicking on "Edit comment") the design of the page is still old, is it supposed to be like that?

{{vm.hiddenReplies[27201] ? 'expand_more' : 'expand_less'}} hide replies show replies
TRANG TRANG September 10, 2016 September 10, 2016 at 5:46:15 PM UTC link Permalink

Yes, it's normal. The form for adding/editing comments has not been redesigned. I only worked on the component that displays the comment.

Guybrush88 Guybrush88 September 10, 2016 September 10, 2016 at 3:06:19 PM UTC link Permalink

I have a question: what does the link option do in the new comment field? I tried to use it but nothing happens, and I'm not really sure of its purpose

{{vm.hiddenReplies[27202] ? 'expand_more' : 'expand_less'}} hide replies show replies
CK CK September 10, 2016, edited October 30, 2019 September 10, 2016 at 3:18:49 PM UTC, edited October 30, 2019 at 11:00:36 AM UTC link Permalink

[not needed anymore- removed by CK]

{{vm.hiddenReplies[27203] ? 'expand_more' : 'expand_less'}} hide replies show replies
Wezel Wezel September 10, 2016, edited September 10, 2016 September 10, 2016 at 3:40:43 PM UTC, edited September 10, 2016 at 3:42:37 PM UTC link Permalink

I'm not sure why it looks like an arrow point in "Latest comments" section, but on a sentence's page it looks like a chain link while having the same function.

{{vm.hiddenReplies[27204] ? 'expand_more' : 'expand_less'}} hide replies show replies
CK CK September 10, 2016, edited October 30, 2019 September 10, 2016 at 3:56:54 PM UTC, edited October 30, 2019 at 11:00:20 AM UTC link Permalink

[not needed anymore- removed by CK]

{{vm.hiddenReplies[27205] ? 'expand_more' : 'expand_less'}} hide replies show replies
Wezel Wezel September 10, 2016 September 10, 2016 at 4:11:40 PM UTC link Permalink

> Perhaps that "arrow" icon would be an even better icon to use for the link to the sentences pages (from the logs and from the comments on the "home" page)

+1, and replace the current arrow (direct link to a comment) with a chain link or a #, as Guybrush suggests below.

Guybrush88 Guybrush88 September 10, 2016 September 10, 2016 at 3:56:57 PM UTC link Permalink

personally I'd prefer to have the arrow point (or, even better, the current #) instead of the chain link in every page where a comment appears

TRANG TRANG September 10, 2016 September 10, 2016 at 6:00:04 PM UTC link Permalink

The arrow is supposed to express "reply". The idea is that if a user wants to reply to a comment, they click on that icon. I felt it would be more intuitive to use the "reply" concept instead of the "permalink" concept.

I kept the same behavior as the current '#' link, so when the user clicks on the reply icon, they are redirected to the comment on the sentence's page. In some cases they may have to scroll down in order to reach the comment form because the comment they chose is not the latest comment. Ideally, the form should appear below the comment, but that's some improvement for later.

Using the reply icon on the sentence's page would make sense if it scrolls down to the comment form.

{{vm.hiddenReplies[27211] ? 'expand_more' : 'expand_less'}} hide replies show replies
Wezel Wezel September 10, 2016 September 10, 2016 at 6:06:17 PM UTC link Permalink

Thank you for the response.

Also, that may be a minor thing, but the info icon and the reply arrow in "latest comments" are seemingly not aligned: the arrow is a little to the left from the icon above.

{{vm.hiddenReplies[27212] ? 'expand_more' : 'expand_less'}} hide replies show replies
TRANG TRANG September 10, 2016 September 10, 2016 at 6:20:27 PM UTC link Permalink

I readjusted the alignment.

{{vm.hiddenReplies[27213] ? 'expand_more' : 'expand_less'}} hide replies show replies
Wezel Wezel September 10, 2016 September 10, 2016 at 6:25:14 PM UTC link Permalink

Great, thanks again.

TRANG TRANG September 10, 2016 September 10, 2016 at 5:46:41 PM UTC link Permalink

I added tooltips. Let me know if it's clearer now what this icon does.

{{vm.hiddenReplies[27210] ? 'expand_more' : 'expand_less'}} hide replies show replies
Guybrush88 Guybrush88 September 10, 2016 September 10, 2016 at 6:26:31 PM UTC link Permalink

seems better now. A suggestion: what about adding a tooltip also to the info icon in the latest contributions page? Imho it would improve it

{{vm.hiddenReplies[27215] ? 'expand_more' : 'expand_less'}} hide replies show replies
TRANG TRANG September 10, 2016 September 10, 2016 at 6:45:41 PM UTC link Permalink

Well in the case of the info icon, I think it's an icon that is generally recognizable enough that it doesn't need a tooltip. I'd prefer to avoid the overuse of tooltips.

Even for the comments, I'm afraid that some users start to getting annoyed by the tooltip once they've learned the meaning of the icons. But we'll see...

marafon marafon September 10, 2016, edited September 10, 2016 September 10, 2016 at 8:46:16 PM UTC, edited September 10, 2016 at 8:48:27 PM UTC link Permalink

Wouldn't it be better to move flag and information icon to the left in the "Latest contributions" field? Just like it is here:
https://tatoeba.org/rus/sentences/of_user/marafon

Odexed has mentioned that:
https://tatoeba.org/rus/wall/sh...#message_27100
2) You've changed the position of flags and moved them to the right side. Most people are accustomed to read from left to right.

{{vm.hiddenReplies[27218] ? 'expand_more' : 'expand_less'}} hide replies show replies
TRANG TRANG September 10, 2016 September 10, 2016 at 10:11:38 PM UTC link Permalink

I wrote a poìnt about this in https://github.com/Tatoeba/tatoeba2/pull/1306:

"The language icon for the sentence is displayed on the end side of the sentence (right side on LTR and, left on RTL interface). This copies the layout of the contribution logs. I'm still not completely decided on putting the language icon on the end side, but I'd like to give it a try."

I understand that people will scan the page and use the language icon to quickly detect the sentences they're interested in, and it's faster for them to detect the sentences if the language icon is on the left.

It's however more complicated to design and implement the logs with the language on the left. And since currently the logs have the language on the right-side, I've also put them on the right-side in the comments, to see if that's something users can get used to.

{{vm.hiddenReplies[27219] ? 'expand_more' : 'expand_less'}} hide replies show replies
marafon marafon September 10, 2016 September 10, 2016 at 10:32:44 PM UTC link Permalink

> I understand that people will scan the page and use the language icon to quickly detect the sentences they're interested in, and it's faster for them to detect the sentences if the language icon is on the left.

That's it.

Wezel Wezel September 11, 2016 September 11, 2016 at 7:14:23 PM UTC link Permalink

All the comments appear to say "X minutes ago, edited X minutes ago" even though they were not edited.

{{vm.hiddenReplies[27227] ? 'expand_more' : 'expand_less'}} hide replies show replies
CK CK September 11, 2016, edited October 30, 2019 September 11, 2016 at 10:57:32 PM UTC, edited October 30, 2019 at 11:00:11 AM UTC link Permalink

[not needed anymore- removed by CK]

{{vm.hiddenReplies[27228] ? 'expand_more' : 'expand_less'}} hide replies show replies
marafon marafon September 11, 2016 September 11, 2016 at 11:00:13 PM UTC link Permalink

+1

TRANG TRANG September 11, 2016, edited September 11, 2016 September 11, 2016 at 11:04:18 PM UTC, edited September 11, 2016 at 11:05:32 PM UTC link Permalink

Why is it important?

Edit: I wrote about this change on https://github.com/Tatoeba/tatoeba2/pull/1306.

"The username of the sentence owner has been removed because I don't think it is necessary. It was introduced upon a request from a user who wanted to see the username to be able to notice when a comment is posted on his sentences. This use case was actually not too relevant back then, but it is even less relevant today. There's much more activity on the website, which makes it unlikely that a user would notice from the homepage a comment on their sentence unless they are looking at the page 24/7. Also, users have a page that lists all the comments on their sentences. Having the username of the owner doesn't bring much value."

{{vm.hiddenReplies[27231] ? 'expand_more' : 'expand_less'}} hide replies show replies
CK CK September 11, 2016, edited October 30, 2019 September 11, 2016 at 11:07:33 PM UTC, edited October 30, 2019 at 10:59:56 AM UTC link Permalink

[not needed anymore- removed by CK]

{{vm.hiddenReplies[27233] ? 'expand_more' : 'expand_less'}} hide replies show replies
TRANG TRANG September 11, 2016 September 11, 2016 at 11:08:09 PM UTC link Permalink

Yes, but why do you need to see it when you read comments on the homepage?

{{vm.hiddenReplies[27234] ? 'expand_more' : 'expand_less'}} hide replies show replies
Pfirsichbaeumchen Pfirsichbaeumchen September 11, 2016, edited September 12, 2016 September 11, 2016 at 11:55:15 PM UTC, edited September 12, 2016 at 12:01:07 AM UTC link Permalink

I find that information interesting, too. Also, sentences would be properly attributed to who owns them. I don't see why this should be irrelevant.

{{vm.hiddenReplies[27235] ? 'expand_more' : 'expand_less'}} hide replies show replies
mraz mraz September 12, 2016 September 12, 2016 at 4:13:18 AM UTC link Permalink

I find that information interesting, too. Also, sentences would be properly attributed to who owns them. I don't see why this should be irrelevant.

+1

TRANG TRANG September 13, 2016 September 13, 2016 at 10:18:22 PM UTC link Permalink

​To clarify, by irrelevant I meant that it doesn't seem to help achieve any particular goal in the context of the comments.

More concretely: the sentence text and language are relevant because they give context to the comment. If the comment says that the sentence sounds strange, or has a mistake, or is set with the wrong language, you'll want to see what the sentence looks like. For a large amount of comments, if you didn't have the sentence, you would click on the info icon to see what's the sentence exactly, in order to understand fully what the comment is about.

But what about the owner? It's an extra information and of course it can be useful. Just like having the date of creation of the sentence, or date of last modification, could be useful. Or knowing if the sentence was tagged OK or @change could be useful. Or knowing if the sentence has audio or not.​ Or knowing how many comments in total have been posted on the sentence.​..

What makes the sentence owner more important than any of these other pieces of information? What do you achieve with it? What justifies that you get this information right away, rather than with an extra click, like you would have to do for the creation/modification date, the tags, the audio...?

These are questions I cannot answer by myself.

Considering that several users are requesting to have the username back, there has to be something. But I need deeper explanations than "because I want to know it" or "because I find it useful".

Here's my analysis of the various arguments posted in this thread.

1. Having the owner's name would give proper attribution to the sentence.

=> This is is not completely correct. The only place where we can provide complete attribution is on the sentence's details, because this is where you can see who initially added the sentence, who modified it, who commented on it. A sentence can belong to someone who did not initially added it. The final version of a sentence is often the result of collaborative work, with people suggesting corrections or better wording. Reducing attribution to the owner of the sentence is actually a bit unfair, not all the glory goes to the owner.
The username can be misleading as well because the way the it is displayed kinda makes it look like the user is the original author. But when users are extracting quotes from other sources to add them to Tatoeba, even though they will be marked as the "owner" of the sentence, they are not the original author. The original author may be mentioned in the tags or in a comment.
So for me the owner's name doesn't fulfill very well the role of giving attribution.

2. Some users look at the username to figure out if the author of the comment posted on their own sentence.

=> This use case is not elaborate enough for me to see the needs behind it. The question is what happens then? Once a user knows that a user has commented on their own sentence, or hasn't, does it influence any decision? Does it make the user look at the comment any differently? If yes, which decisions, what difference?

3. Having the username serves as a shortcut to discover (and proofread) more sentences from a contributor.

=> This is a much stronger use case, one that I can actually work with. This use case shows that the username facilitates navigation within Tatoeba for an actual purpose: checking out more sentences from a certain contributor. Instead of reaching the contributor's sentences page in 3 clicks, one could get there in 2 clicks.

-------

Now I have to rant a little bit more because there is something important. If I'm spending so much time writing this post, this is not because displaying the sentence owner is a huge deal, but because it's related to a much deeper problem that I'm struggling with, on regular basis: the struggle of getting users to share their user stories.

More and more often, whenever I'm making changes in Tatoeba, I try to ask myself what is the purpose for each part, each button, etc. I came to ask myself why do we display the owner of the sentence in the comments. I couldn't remember why we added it there, and I couldn't picture a good reason either. But I was able to trace down the reason (explained in one of my previous comment), and when I read the Wall thread explaining the reason, I realized that it was not a good reason.

So displaying the sentence owner is actually something I implemented myself back then. I was the one who made the choice to put it there. But in the past, I had the tendency to accept pretty much every request that users asked for. If it was something "small" and not too complicated to implement, I would be okay to implement it, without really taking the time to analyze if the request addresses real needs or if it's just sugar coat. The username is a typical example of something I've added without analysis.

Nowadays, I am a lot more strict with these things because the danger is that the UI gets more and more cluttered, with too many options and too much information, that it becomes too intimidating, or too distracting, or too uncomfortable for the average user. I don't want to overload the UI for the wrong reasons.

Just because a group of users want to see a certain piece of information doesn't mean it is beneficial for everyone, and many parts of Tatoeba's UI are problematic for that matter. Some people like to have the random sentence on the homepage while other people find it unnecessary. Some people find it useful to see transcriptions for Japanese, Chinese, etc, while some people have no use for it. Some people like to see translations in every languages while others only want to see the language they are interested in. There are, and there will always be, many parts of Tatoeba for which users have conflicting needs.

In such situations, it is impossible to make a good decision, nor to find a good solution, without understanding the user stories behind a certain a feature, or feature request. And by "user story" I mean a description of how you are using a feature, with enough details for anyone to put themselves in your shoes and understand why having this feature makes your experience better (or worse) and why not having it makes your experience worse (or better). What problem does it solve for you? The reply from Aiji is an example of good user story: https://tatoeba.org/eng/wall/sh...#message_27243

Without user stories, I have to rely on my telepathic powers, which are not very advanced, to read users minds. Or I have to use my imagination, fight with my own instincts, to try and understand what could be the problems for other people, when it is not necessarily a problem for me. Then I have to spend time writing down a hypothetical user story that the concerned users have to validate.
Without user stories, I could be wasting time implementing a solution that doesn't solve the right problem. Maybe by sharing your user story, you will uncover a problem that I, or anyone, never really thought of, and that can influence a lot, not only the final solution for the feature itself, but as well other features of Tatoeba.

So for anyone reading this, when you are confronted to a change that disrupts your activities on Tatoeba, or when you want to suggest a change because the current features don't do the job for you, please, remember *not* to stop at merely stating that "it would be better if...", or "I would prefer if..." or "I would find it useful/interesting/practical/nice if...". Give me the full story, so that I can understand clearly what is your goal and what causes you trouble to reach that goal.
And when you see someone failing to provide a user story to back up a suggestion, please do me a favor and interrogate them until they've provided enough information. Or provide your own story, if the suggestion is something you'd like to see implemented as well. Don't just "+1" it.
This will save me a tremendous amount of time and energy.

{{vm.hiddenReplies[27256] ? 'expand_more' : 'expand_less'}} hide replies show replies
brauchinet brauchinet September 14, 2016 September 14, 2016 at 9:00:30 PM UTC link Permalink

> I was the one who made the choice to put it there.

It was a good choice...

Unfortunately, it's difficult to tell a "user story" in that sense that the username is necessary to perform a certain task more easily or quickly. There is no task to perform; it's just reading the comments.
Why not remove the language flag instead? Whoever might be interested in the comment will at least recognize the language, so the flag doesn't add any information for them.

{{vm.hiddenReplies[27262] ? 'expand_more' : 'expand_less'}} hide replies show replies
Ricardo14 Ricardo14 September 15, 2016 September 15, 2016 at 2:47:16 AM UTC link Permalink

> Why not remove the language flag instead?

It's impossilble since many languages have a lot in common.... Some examples:

[eng] I'm fine.
[por] Estou bem X [spa] Estoy bien

without the language icon, I don't if someone wrote that sentence into Spanish or Portuguese

[eng] I'm from Mexico.
[por] Sou do México X [spa] Soy de Mexico.

[eng] I live in France.
[por] Moro/Vivo na França X [spa] Vivo en Francia

(So if someone posts "Moro na Françia", I won't be able to know if this sentence is in Portuguese or in Spanish)

[eng] I love you!
[por] Te amo! X [spa] ¡Te amo! X [ita] Ti amo!

[eng] Hi!
[dan] Hej! X [fin] Hei!
[ger][nor] Hallo!
[fre][rom] Salut!
[cat] Hola! X [spa] ¡Hola! X [por] Olá!


{{vm.hiddenReplies[27263] ? 'expand_more' : 'expand_less'}} hide replies show replies
brauchinet brauchinet September 15, 2016 September 15, 2016 at 3:41:15 AM UTC link Permalink

You're right.

TRANG TRANG September 15, 2016 September 15, 2016 at 9:43:02 AM UTC link Permalink

> It was a good choice...

It was a "lucky" choice, not a "good" choice. It's a good choice when I can back it up with good reasons :)

> Unfortunately, it's difficult to tell a "user story" in that sense that the username
> is necessary to perform a certain task more easily or quickly.

User stories are not always about productivity. It's not always about performing visible tasks more efficiently. Aiji's story is an easy one, because it has a measurable output (2 clicks vs. 3 clicks). But the question you have to answer is *not* why does it make you "work" better, but why does it give you a better experience. Why does it make you feel better, or less frustrated?

Being more productive is one reason to feel better, but not the only reason. Some stories are more on psychological or emotional level. They require you to analyze yourself on a deeper level and they are for sure more difficult to see and to express.

Aiji Aiji September 12, 2016 September 12, 2016 at 10:01:43 AM UTC link Permalink

We may not "need" it absolutely but I think of one good reason why it would be good to have it and that is proofreading. When I see a comment on a French sentence on the homepage, if I don't know the author of the sentence, I can click his username to directly go to see his profile and sentences and proofread them if necessary. That is not something that I would do spontaneously, but this "unexpected" thing is part of my proofreading habit. Of course, I could do the same by first clicking the sentence, then check, etc. but having a lazy nature, I don't like extra steps and therefore do not think this feature is irrelevant. (the reason you described, on the other hand, is irrelevant, I agree with you)

Also, why remove the possibility to click the username of the person who makes a comment?

{{vm.hiddenReplies[27243] ? 'expand_more' : 'expand_less'}} hide replies show replies
mraz mraz September 12, 2016 September 12, 2016 at 10:41:09 AM UTC link Permalink

+1

TRANG TRANG September 13, 2016 September 13, 2016 at 10:20:21 PM UTC link Permalink

Thanks for your feedback, Aiji. You can refer to my post above for my thoughts on this use case: https://tatoeba.org/eng/wall/sh...#message_27256

As for the impossibility to click the username of the author of the comment, this was not an intended behavior, and was fixed yesterday.

brauchinet brauchinet September 13, 2016 September 13, 2016 at 6:14:00 AM UTC link Permalink

+1
Some users seem to habitually browse through the comments, and they know most of the usernames. To them (me), the username isn't irrelevant at all.
For example, did the owner himself put a comment to their sentence or was it someone else?

{{vm.hiddenReplies[27251] ? 'expand_more' : 'expand_less'}} hide replies show replies
mraz mraz September 13, 2016 September 13, 2016 at 7:07:29 PM UTC link Permalink

+1

Some users seem to habitually browse through the comments, and they know most of the usernames. To them (me), the username isn't irrelevant at all.
For example, did the owner himself put a comment to their sentence or was it someone else?

Egyes felhasználók úgy tűnik, hogy rendszeresen böngészik az észrevételeket, és ismerik a legtöbb felhasználónevet. Nekik (nekem), a felhasználónév nem irreleváns egyáltalán.Például az, hogy maga a tulajdonos írta a megjegyzést a mondathoz vagy valaki más.

mraz mraz September 12, 2016 September 12, 2016 at 4:03:55 AM UTC link Permalink

+1

{{vm.hiddenReplies[27236] ? 'expand_more' : 'expand_less'}} hide replies show replies
odexed odexed September 12, 2016 September 12, 2016 at 4:07:45 AM UTC link Permalink

I agree. I have a bad feeling about the new interface. Tatoeba also looks awful on my Android cellphone.

{{vm.hiddenReplies[27238] ? 'expand_more' : 'expand_less'}} hide replies show replies
CK CK September 12, 2016, edited October 30, 2019 September 12, 2016 at 5:21:41 AM UTC, edited October 30, 2019 at 10:59:47 AM UTC link Permalink

[not needed anymore- removed by CK]

{{vm.hiddenReplies[27240] ? 'expand_more' : 'expand_less'}} hide replies show replies
TRANG TRANG September 13, 2016 September 13, 2016 at 11:12:22 PM UTC link Permalink

Some time ago I asked if anyone was interested in being a tester for Tatoeba but nobody responded to this.
https://tatoeba.org/eng/wall/sh...#message_26623

If you're interested in being a tester, let me know. Without people who want to take responsibility for testing the dev website, I don't feel motivated in establishing heavier release processes.

In any case, quite often, you can already test changes that I make on the dev website a couple of days before I announce it. I don't make the announcement because it takes me time to document the changes in an issue, to write down as precisely as possible what has changed and possible explain why. I'd rather ask people to test after I wrote down what has changed so that they have a clear idea what to test.

You can browse the milestones on GitHub in order to check when are the next updates: https://github.com/Tatoeba/tatoeba2/milestones. So far it's every week, but sometimes I skip some weeks.

You can monitor the commits in order to know whenever someone made changes in the code: https://github.com/Tatoeba/tatoeba2/commits/dev
You can subscribe to the Google group tatoeba-commits as well, if you want to receive email notifications for every commit.
https://groups.google.com/forum...atoeba-commits

In general, whenever there is new code in the "dev" branch, I will perform an update on the dev website shortly after. If I don't, you can always ask me to.

TRANG TRANG September 11, 2016 September 11, 2016 at 11:04:04 PM UTC link Permalink

That's fixed.

{{vm.hiddenReplies[27230] ? 'expand_more' : 'expand_less'}} hide replies show replies
mraz mraz September 12, 2016 September 12, 2016 at 4:06:03 AM UTC link Permalink

Also, we used to have a way to easily send a private message to the person who made the comment, like what we have on the Wall now. I found this very useful.

+1