文プロ(Bunpro) : Update 1/15 - N4 Grammar Writeups - Japanese Grammar SRS Study Site

Nice that there is OOPS button. However, the button should disappear after pressing “Show Answer” to prevent cheating.

BTW, what is the keyboard shortcut summary? Particularly for “Show Answer”?

1 Like

Looks like the furigana on 必ず has an extra ず!

I’m also getting a bug where it always shows me at 1 review remaining when I’m finished with all of them. Maybe this has been reported already.


Now that I’m finally getting to use the platform (some N3 stuff is coming up in my N2 revisions), I’m having an interesting time. It’s a real challenge to remember the grammar points, which is kind of the point.

A thought for far into the distant future:

One issue I’ve had when studying grammar points is differences due to particles, or adjoining phrases. In addition to simple typing SRS, maybe it’s possible to build a new question system in which you’re shown a grammar point with a context sentence, and have to choose the right particle/verb form/etc from multiple choices? I can give examples if this isn’t clear.

For “Show Answer”, I think it’s the same as WaniKani: F.

1 Like

Lack of ‘T’ at the beginning of the sentence. Plus, the first one is normal and the second of is polite - a bit inconsistent to me.

It was looking for 降り始めた.

It would be nice to have an override-button, especially in the alpha-stage when there are a lot of sentences that forget to specify if they are looking for the casual or the polite version (for example one of the かもしれない questions mark かもしれません wrong)

Capture

By the way, I would suggest changing the color of that useful little info-box to something else than red. Humans usually associate red with a mistake or error. It makes me feel my answer was wrong, when it was right, just not the one the program is asking.

5 Likes

I seem to be stuck at 1 Review, no matter how often I clear it ;; Tried a non cache refresh, didn’t work.
Account is eefi

I found the wording of this translation a little bit problematic. When I think of “That restaurant” I think そのレストラン

Using そこ instead of その puts the emphasis on where it is, right? Or at least more-so than その

Perhaps the translation should be worded, “That restaurant (over there) is good (delicious).” With the “over there” in gold instead of “that” ?? Unless someone has a better suggestion.

May I ask if you’re going to add N2 and N1 during this year or do we have to wait until 2018? :slight_smile:

@finnra Thank you for your kind words! We hope that we are successful in providing everyone with a grammar study resource that works for them. Cheers!

@Dwarsen This is an excellent point. We like the idea of implementing direct translations alongside what we already have. We will see what we can do. Thank you for your suggestions. Cheers!

@polv We have a feeling that if you click the Oops! button after viewing the answer to the question there is already intent to cheat, but we will play around with the button’s functionality. Thank you for your suggestion. We are currently working on a new Show Answer button that will function similarly to the Show Alternate Answers keyboard shortcut of ‘a’. As @Anaxite pointed out, the ‘f’ can be pressed after submitting an answer to show more information about the grammar point. The arrow keys can be used to navigate between Meaning, Examples, and Readings. The Space Bar toggles English on and off and the delete/backspace key will be used for the Oops! button when move it from beta. Cheers!

@Anaxite It certainly does! Thank you for pointing this out to us. We will get it fixed right away. Thank you, also, for letting us know about the remaining review. Are you using Firefox/Windows 10? We have had a similar issue reported on that platform that we cannot seem to reproduce on our end. We hope to have it sorted out soon!
We are very open to any suggestions on how to expand the site further. We love the idea of eventually adding particles to correctly join phrases and for expanding the site include a variety of different quiz styles. Thank you for your continued support and feedback! Cheers!

@embe Nice find! Thank you for pointing this out to us. Looks like this sentence had been updated to correct the inconsistency in politeness, but we did not push it to the site. We will push the update right away. Sorry for the inconvenience! Cheers!

@Joona Thank you for your feedback. We currently have an Oops! (override) button being beta tested and hope to have it available to everyone very soon. We are also working on redesigning the alerts/announcement info-boxes as well as Show Answer button to make it more intuitive. We agree that the red immediately signals “wrong” when you see it and will choose a new color when we update. Thank you for your suggestions! Cheers!

@eefi Thank you for your feedback. We are currently trying to get to the bottom of this issue. Would you be willing to tell us what web browser and operating system you are using so that we can quickly pinpoint the problem? Sorry that you are experience trouble! Thank you for your patience.

@thespookyfish Thank you for your feedback. You are absolutely right that the use of そこ here and the way that it is translated causes confusion. We will create a more relevant example sentence and make sure to update the Review question so that it becomes more apparent what Bunpro is looking for. Thank you for your suggestions. Cheers!

@Nedeli We are working on getting N2 up as quickly as we can. We just want to make sure that when we release we have an intuitive and polished finished product for you. Stay tuned!

2 Likes

This is really minor, but some of the questions have much larger text that’s way easier to read. Might as well fill up that space, right?

I normally wouldn’t even take the time to mention something like this, but I feel your responsiveness, transparency, and love of the project warrant it. Kudos to you guys, this is shaping up to be an incredible resource!

1 Like

@jbradleyc Thank you for your kind words and feedback! We are looking to redo the reviews with font size/readability as one of our main focuses. Stay tuned!

2 Likes

Rather than doing grammar by JLPT level and by lesson 1-10; I feel like it is better learned by reading/listening --> questioned by your own comprehension --> look up grammar point and associated grammar --> read the theory of individual grammar point and comparative grammar --> SRS.

I also want it searchable by Kanji, for example 気.

So, a better search engine for grammar is a must…

For example, looking up の、こと、もの、ばかり、はず、という、あまり、わけ、ちなみに…

I want to buy Dictionary of Grammar, too; but there are three, I don’t know which one to buy…

2 Likes

Firefox on Linux. I could give Chromium a try later and see what that does.

1 Like

For some reason it resolved itself? I cleared my reviews today and it went down to zero. I was using a different computer though. My desktop yesterday that was having problems was a Linux machine with Firefox.
Thanks for improving the site! Really like it!

1 Like

One more thing is off in the search engine. undefined

Love this website. When do you think N2 will be released? :slight_smile:

1 Like

image

Better to not tell me exactly what its looking for? “Looking for something else” may be better, as I can never remember けれども, and always answer が. Just telling me the answer, instead of making me try and think of it, seems less learny. I end up re-answering with garbage, to force a failure.

6 Likes

I wonder how accurate are Bunpro’s example sentences.

3 Likes

@polv Thank you for your feedback. We are working on making the search engine more responsive and intuitive. If you do not know which grammar dictionary to buy, why don’t you buy them all!? If you find any inaccuracies in the sentences on Bunpro, please do not hesitate to let us know. The sentences are created in house and checked by native speakers, but that does not eliminate human error. Cheers!

@Anaxite and @eefi Thank you for providing your browser and operating system information. We are still having trouble replicating the issue, but will continue working at it. @Anaxite Did you experience any issues on Chrome? Thank you for your patience as we get this sorted out! Cheers!

@keisuke1989 Thank you for your kind words! We are drawing close to the beta release of the first couple of levels of N2, which we will make live to everyone shortly after. We hope to have as much material available to you as possible before the JLPT this winter. Cheers!

@DaisukeJigen Thank you for your feedback. This has popped up before and our reasoning was:

There are many grammar points that can be interchangeable with others and we thought that answering multiple times until you got the answer that Bunpro was looking for that it would be more frustrating. However, we realize that this may not the best method of testing, nor the most “learny”, so we will look to approach this method of study a little differently. If you have any suggestions or if you could give us some insight on what works best for you, we would love to hear it! Cheers!

2 Likes

A little bit more testing:

  • Chromium on Ubuntu works fine
  • Firefox on Android has problems
  • Firefox on Ubuntu has problems

It appears that, on Firefox, something on the site gets stuck: it doesn’t acknowledge having done the very last review of a review session. I think it’s browser specific rather than related to addons - having the same problem on Android is a clue, and I tried disabling all my adblocking.

This is a stab in the dark, but do you have Javascript code that specifically runs after a final review that could be going wonky? I’ve noticed that when I submit the final review of a session, it sometimes_still_ loads one new review after that, then finally reloads the page. This makes me wonder if your site is doing something like this:

  • I submit the final review’s answer
  • Answer is green
  • Hit enter to move on/finish
  • Site loads a new review from somewhere and adds it to the queue
  • Javascript immediately runs to load the summary page
  • now you’re left with a phantom review?

I’m no good at Javascript debugging so I can’t tell if that’s the problem. Maybe there’s a Javascript function being used that isn’t compatible with Firefox (which, although weird, is not the first time I’ve seen it. Thanks, Matecat).

2 Likes