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 {{ icon }} keyboard_arrow_right

Profile

keyboard_arrow_right

Sentences

keyboard_arrow_right

Vocabulary

keyboard_arrow_right

Reviews

keyboard_arrow_right

Lists

keyboard_arrow_right

Favorites

keyboard_arrow_right

Comments

keyboard_arrow_right

Comments on gillux's sentences

keyboard_arrow_right

Wall messages

keyboard_arrow_right

Logs

keyboard_arrow_right

Audio

keyboard_arrow_right

Transcriptions

translate

Translate gillux's sentences

gillux's messages on the Wall (total 594)

gillux gillux July 5, 2015 July 5, 2015 at 10:09:38 AM UTC link Permalink

You can use other sites like imgur.com for example.

gillux gillux July 5, 2015 July 5, 2015 at 8:53:13 AM UTC link Permalink

I can see it too, but can you provide a screenshot just in case? This problem is likely due to font substitution. We tell browsers to use a certain font to display text on the site (which happens to be Trebuchet MS), whereas this font may not include glyphs used in Azeri (and many other languages), so it fallbacks on a different font only to display "ə". Such font mix can result in height differences especially in small sizes, and style differences. One way to work around this problem is to use webfonts. We talked about that some weeks ago https://github.com/Tatoeba/tatoeba2/issues/684

gillux gillux July 1, 2015 July 1, 2015 at 2:56:41 PM UTC link Permalink

I recorded that issue: https://github.com/Tatoeba/tatoeba2/issues/700.
Thank you for reporting!

gillux gillux July 1, 2015 July 1, 2015 at 7:11:38 AM UTC link Permalink

It should work better now.

gillux gillux July 1, 2015, edited July 1, 2015 July 1, 2015 at 6:36:12 AM UTC, edited July 1, 2015 at 6:36:39 AM UTC link Permalink

> Why doesn't the auto-detect recognise Macedonian?

Because the autodetection algorithm is based on the Tatoeba corpus itself, and we still need to update it manually once in a while so that it takes new sentences into account. Three month ago, there were less than 200 sentences in Macedonian, which was not enough for the algorithm to work. Now you added about 50 000 Macedonian sentences, it will certainly work better once we update it. I’ll let you know when it’s done.

gillux gillux June 30, 2015 June 30, 2015 at 2:42:00 AM UTC link Permalink

> I personally don't think the problem is due to the restriction of the list but due to the fact that the rules and the form are not very clear for new users.

I think it’s both. If you look cindycute’s profile, there is only English while he or she’s a native Chinese. When people are learning a language, and they are asked to add languages they are interested in into their profile, it’s normal they don’t add their native language. Who would know? Even when you’re adding a new language into your profile because the “add sentence” or “add translation” form told you to do so, it’s not clear that we mean your native language rather than the language you want to add sentences in or translate into.

We could solve this problem by having the following process:
• Bring back the full list of languages, with autodetection selected by default.
• Autodetect the language *before* submitting the sentence, so that the user is aware of what language he or she’s about to submit.
• If the selected language isn’t in the user’s profile, display an error message “Sounds like you’re trying to add a sentence in X, but you didn’t add this language to your profile.” And if X was autodetected: “If the sentence was mistakenly detected as X, please select the correct language.”

gillux gillux June 30, 2015 June 30, 2015 at 1:57:02 AM UTC link Permalink

No, it has been implemented everywhere but on the “add sentence” and “add translation” forms.

gillux gillux June 28, 2015 June 28, 2015 at 8:25:13 AM UTC link Permalink

Yes, I don’t think such sentences go against Tatoeba’s goals. The guidelines say “We want sentences that a native speaker would actually use” ¹, so giving an error is common among native speakers, you can put it on Tatoeba. I think we rather use tags like “casual” however.

1. http://en.wiki.tatoeba.org/arti...s,-not-word-fo

> I can easily imagine someone reading a sentence containing a common error, not bothering to open it to read the tags/comments, and inadvertently "learning" something wrong from it.

That’s what you get from learning sentences out of context. And this is true for correct sentences too. If you learn a grammatically correct sentence without knowing it’s exclusively used in, let’s say business context, you’re learning something wrong by thinking it could be used casually.

gillux gillux June 28, 2015, edited June 28, 2015 June 28, 2015 at 1:52:05 AM UTC, edited June 28, 2015 at 1:52:29 AM UTC link Permalink

> 1. Another idea to consider would be to allow the option of an alphabetical sort if it doesn't put too much of a load on the server.
> 2. Also, another idea to consider would be to allow the option to sort the sentences by how they end, if this doesn't put too much load on the server.

I think this would be too resource-hungry as we’d need to index all the sentence texts.

> 3. This one may put too much load on the server, but ...

This won’t put any load and is easy to do.

gillux gillux June 28, 2015 June 28, 2015 at 1:40:12 AM UTC link Permalink

That’s because dev.tatoeba.org’s database is so old that doesn’t contain much natives. There are only people who set themselves as natives on dev.tatoeba.org when Trang introduced this feature. See https://dev.tatoeba.org/stats/native_speakers

gillux gillux June 27, 2015 June 27, 2015 at 6:20:04 AM UTC link Permalink

It’s now possible to randomize the results by selecting the appropriate option of the “Sort” field.

gillux gillux June 27, 2015 June 27, 2015 at 6:02:37 AM UTC link Permalink

I tried to put the search fields to the right, although it feels a bit packed to me, and it requires quite some scrolling to get to the submit button, and it uglify the page when there are no results. Tell me what you think.

gillux gillux June 27, 2015 June 27, 2015 at 6:00:25 AM UTC link Permalink

No, it’s not possible to display more than the first 1000 results. Why would you want that by the way? Also, what if the search criteria are set so that sentences disappear from the search results once translated? This way, the contributor only needs to translate the first results.

gillux gillux June 27, 2015 June 27, 2015 at 5:57:57 AM UTC link Permalink

Since adding a “random page” link on every pagination is rather more difficult to do, I only added a random sort order function to the advanced search.

gillux gillux June 27, 2015 June 27, 2015 at 5:56:18 AM UTC link Permalink

Thank you, this should be fixed now.

gillux gillux June 27, 2015 June 27, 2015 at 12:37:33 AM UTC link Permalink

What do you mean by graying out? Do you mean a reset button for that part only? Or do you mean to gray it out automatically when its fields are all set their default values?

gillux gillux June 27, 2015 June 27, 2015 at 12:30:58 AM UTC link Permalink

Where?

gillux gillux June 26, 2015, edited June 30, 2015 June 26, 2015 at 4:15:54 AM UTC, edited June 30, 2015 at 5:07:35 AM UTC link Permalink

** Advanced Search **

I’ve been working on implementing an advanced search feature. You can test it here: https://dev.tatoeba.org/sentences/search

Now, unapproved and orphan sentences are no longer put at the end of the search results. Instead, they are filtered out by default when performing a search from the top bar. One can later make them appear in the results by changing the appropriate criterion.

Feel free to comment on anything. Note that searches are performed on a copy of tatoeba.org’s database from February 2nd, so you won’t find sentence added past this date. But you can add new sentences just for the sake of searching. They should be visible within ten minutes.

I’d like you to test not only all the criteria, but also searching for newly-added or newly-modified sentences. I changed the way new or modified sentences got indexed, so this part may contains bugs too. In short, every sentence you add or modify should become visible (or disappear) in a search within ten minutes, be it because of a modification of its contents, its tags, ownership, audio, link etc. anything that can be searched.

Previous thread: https://tatoeba.org/wall/show_message/22852

gillux gillux June 23, 2015 June 23, 2015 at 3:40:46 PM UTC link Permalink

That’s a very interesting feature I couldn’t find anywhere in Sphinx’s documentation. I wonder if it’s actually related to wildcard search or it’s just another usage of the star character. Do you know if such searches worked before we add wildcard search?

gillux gillux June 23, 2015 June 23, 2015 at 10:25:44 AM UTC link Permalink

We should probably update the wiki, but in short:
• break → matches break and other words that have the same stem in each language that support stemming, and just break for languages that doesn’t support stemming. For instance, in English sentences it will match break, breaks, breaking, in French it will match break, breaks (it’s a car type), in Esperanto it will only match break because Esperanto doesn’t have a stemmer.
• =break → matches any sentence that have the word break exactly, regardless of stemming
• break* → matches any word starting with break (including break), like breakfast, regardless of stemming