Muro (5 915 fadenoj)
Antaŭ ol starigi demandon, bonvolu legi la oftajn demandojn.
Ni strebas konservi sanan etoson en civilizitaj diskutoj. Bv. legi niajn regulojn kontraŭ malbona konduto.
antaŭ 4 horoj
antaŭ 5 horoj
antaŭ 2 tagoj
antaŭ 2 tagoj
antaŭ 2 tagoj
antaŭ 3 tagoj
antaŭ 3 tagoj
antaŭ 3 tagoj
antaŭ 3 tagoj
** Stats & Graphs **
Tatoeba Stats, Graphs & Charts have been updated:
Would you like to be the first to translate some English sentences on my proofread list of sentences (List 907)?
This search will find sentences not yet translated, showing the oldest sentences first.
This is the same search, but limited to only the 29,000 sentences with audio.
I wish there was a way to easily flag links to translations as being questionable. That would cover the case where a linked translation is correct as a sentence, but does not mean the same as the original sentence.
Of course one could go and write a comment on each questionable translation, but it is quite tedious, and it is easy to get sidetracked in the process. Or, as an advanced contributor, one could simply unlink the offending translations, but then nobody would probably notice.
I have seen the "unlink" tag, but I don't think a tag is enough.
See sentence #807032 for a current example.
What I normally do is the following.
I take notice who was the one to create the link. for example, #1508983 was linked by marcelostockle - you can see that in the logs. In this case it's a relatively simple case, he added his sentence as a translation. So I comment under his sentence asking him to verify his translation.
Sometimes it's more complicated than that. Sentence A and sentence B were added independently, and then someone linked them. In this case I comment under any of those tagging the person who linked them and asking them to verify the link.
I do something similar, but it is rather difficult to keep track of the sentences I have remarked on in this way. At least there is a page with all my sentence reviews, but no such thing for my translation review.
I wish some of this could be automated somehow, with notifications going out to those involved.
Bulgarian has been added as a User Interface language on dev Tatoeba.
Thanks a lot to the user ls404 who has been working hard and translating the entire website.
The last language enabled on dev website was Serbian, thanks to lazarljubenovic (Lazar on Transifex).
In case you want/wish/can help us to translate the UI into your native language, please let me know :) you can leave me a private message, email me - firstname.lastname@example.org or simply creating an account on Transifex and going through https://www.transifex.com/tatoe...ite/dashboard/
Update: Uyghur has been added as well on dev Tatoeba.
Any chance Neapolitan being implemented?
** What's New on Tatoeba? - Your biweekly recap #20 **
(What's New on Tatoeba will be published biweekly until the end of August.)
It's been now one month since our Kodoeba event started.
※ As far as the internal code goes:
• Our participants have solved five issues, and seven others are on their way. You can find the details on GitHub.
• Alexs has asked for feedback about the tags: https://tatoeba.org/eng/wall/show_message/35555. Be sure to share your thoughts if you'd like to see the tags in Tatoeba become more useful!
※ As for the external projects:
• lbdx has updated Tatominer: https://tatoeba.org/eng/wall/show_message/35527.
• The other projects are starting to take shape, it's still too early to showcase anything. We'll have to wait until mid or end of July.
※ The search has been improved for languages using Arabic scripts, Indonesian and Tagalog. Many thanks to Yorwba.
※ The number of messages in the private messages has been localized, thanks to Ricardo14.
※ There's now a reset icon in the inputs of the advanced search. Thanks to Roverandom789133 for adding this.
※ We no longer unnecessarily store IPs in our contributions logs. Thanks to jpear1 for cleaning this up.
ON THE WALL
※ Trang has been working on making the landing page responsive: https://tatoeba.org/eng/wall/show_message/35464
※ gillux has asked which sentences would be a good candidate to print on a Tatoeba T-shirt or mug: https://tatoeba.org/eng/wall/show_message/35547
※ tommg has announced the release of his language learning app that uses Tatoeba's data: https://tatoeba.org/eng/wall/show_message/35512
※ Rircardo14 posted some updates about the progress of the translation of our UI: https://tatoeba.org/eng/wall/show_message/35518.
※ A new UI language has been enabled on the dev website: Serbian.
※ As usual, thanks to all the members who helped to translate the website!
If you'd like to help to the development of Tatoeba, report issues, or are just curious, have a look at the GitHub repository.
If you want to help us translate the website to your language, you can join us on Transifex: https://www.transifex.com/tatoe...ite/dashboard/ and check this article on the wiki https://en.wiki.tatoeba.org/art...e-translation.
If you're especially happy with one of the updates, don't hesitate to personally thank our developers :) They're working in the shadow but they'll be glad to hear your feedback.
Last recap: https://tatoeba.org/eng/wall/show_message/35504
See this recap on the blog: http://blog.tatoeba.org/2020/06...weekly_30.html
I would like to know why the FAQ is not published in the Kabyle interface although the translation is finished on Transifex.
Translating wiki content through Transifex is a new process. In this case, we simply didn't pay enough attention and we missed the Transifex notifications about how the FAQ was fully translated into Kabyle. So it was simply forgotten (sorry!).
The wiki is a separate application than the tatoeba.org website. The UI languages available on the wiki are actually not in sync with the languages available on tatoeba.org. Currently, the wiki doesn't support Kabyle yet. We first have to add it as a supported language then we have to manually add the Kabyle translations.
But in any case, we will make sure the Kabyle translation of the FAQ is made available soon :) Thanks for reporting it and thanks for translating!
It's online now: https://kab.wiki.tatoeba.org/articles/show/faq
I have a couple of questions:
(1) What would be a translation of "main" (or "main page") in Kabyle?
For instance, the URL of the English main page is like this:
While for French it's "page-principale" instead of "main":
For each language the name in the URL is in the language itself. For now, I have named the Kabyle page "main" but it would be more suitable to have a string in Kabyle.
(2) Same question for the FAQ URL. Is it fine to leave it as "faq" or is there another acronym in Kabyle?
The translation of "main" in Kabyle is "agejdan".
As for the FAQ URL, it would be better to leave it as "faq".
493,678 English Sentences with Audio from the Tatoeba Project
This is something that I put together for my own students. Perhaps some of you may find it interesting.
The first 36,196 sentences have Japanese translations by native Japanese speakers, followed by 457,482 sentences without.
I updated this today.
On my last update three years ago, on July 8, 2017, there were 295,424 audio files.
We have a new Russian voice.
You can listen to his voice here.
Давайте обгоним французский)
Давайте для начала обгоним венгерский, а там как пойдёт)
I think it might be a good idea to eliminate the question mark (?) wildcard for searching.
I think that users should be able to paste in any sentence in the search form and get a result if the sentence is in the database. This doesn't happen now for sentences with question marks.
I think this usefulness far outweighs the usefulness of the one-letter wildcard.
If you're a member of this website and frequently use the ? wildcard, perhaps you could tell us how often and whether you'd be greatly inconvenienced if this were removed.
This is not something easy to implement at all. The question mark is not a searchable character in the first place.
How about just disabling the question mark as a wildcard and ignore it in searches?
We can get both "Mr Smith" and "Mr. Smith" with this search.
Not getting results for sentences with question marks seems strange, since question marks are a part of language, and this is a website dealing with language.
It doesn't bother me that the question mark itself isn't searchable, but it does bother me that if you search for something as simple as the following, it appears that we don't yet have it.
Why are you doing that?
It's not really intuitive for new visitors to avoid using question marks. I've been on this site a long time and even I often have to do searches more than once because I forget to leave off the question marks..
Question marks are allowed when doing Google searches which a lot of people are used to using.
This is probably not something easy to implement. The question mark and the star are one single feature of Manticore. As a result, we can only enable both the question mark and the star or none of them.
Olen tästä samaa mieltä CK:n kanssa. En kylläkään ole hakutoiminnon tehokäyttäjä.
Please don't remove this feature. I always use this feature every time I search Arabic sentences, because Arabic morphology is really inflected. It involves not only suffixes, but prefixes and infixes as well. The search engine used in Tatoeba doesn't seem work 100% to search Arabic words. For example I try to find sentences containing word "علم" but it shows only words with suffixes like علمت, علموا, علمه, and so on. It doesn't show words like يعلم or تعلم. When I tried to search sentences containing "يعلم", it shows words like يعلمون as well. There are no words like تعلم, نعلم, or أعلم. But, when I type "علم?" I will find them.
This feature also helps me to find words in pattern with different root, since Arabic is from Semitic languages.
For example it helps me to search any sentences containing word with pattern like مفعول. I can type in the search box like this:
and it'll show sentences containing words like مبروك مسرور مفتوح مشغول مجنون and so on.
And for your information, I asked this feature years ago here https://tatoeba.org/eng/wall/sh...#message_22849 and it really helps me a lot since then.
I have given some more thoughts about this problem. I think we can make use of another feature of Manticore (blended characters) to make the search engine find the sentence that you want. Question marks used in the search query would both be treated as a wildcard and as a normal character. In other words, searching for "Is she?" would return the sentence "Is she?" as well as sentences containing "is shed". Giving shorter sentences appear first by default, copy pasting an interrogative sentence in the search box should let you find it right away.
I will update dev with that setting tomorrow to let you guys try it out.
On a side note, the percent character (%) is also a wildcard that means "zero or one character". As a result, searching for "100%" currently matches sentences containing 1000.
I updated https://dev.tatoeba.org/ with an experiment setting to solve the problem of not finding sentences when searching for interrogative questions.
orion17, could you also try and let me know if it causes any problem when you search for "علم?" and the like?
I have tried and it still works, except that I just wonder why the results on dev are fewer than those on main tatoeba.
I forgot to mention on my earlier post that when I searched for verb "علم", it did show also sentences containing words with prefixes like العلم, معلم and so on. However, it showed neither the present tense forms (يعلم تعلم نعلم أعلم) nor the imperative form (اعلم)
Therefore, I need to use a question mark to find one. But this prevents me to find this kind of words with suffixes, then I write *?علم* and it shows exactly what I want like يعلمون
> the results on dev are fewer than those on main tatoeba
The corpus of dev is an old copy of the main Tatoeba, so it only contains old sentences.
> it showed neither the present tense forms (يعلم تعلم نعلم أعلم) nor the imperative form (اعلم)
I suspect that’s because only words with 4 characters or more can be found using a different tense or form. "علم" is only 3 characters long.
This limitation is rather arbitrary and is set because the search engine documentation suggests the stemmer may have problems dealing with short words https://docs.manticoresearch.co...n-stemming-len I think we could consider removing the 4 characters limit.
It’s now possible to search for entire questions on tatoeba.org.