Home Forums The Japanese Language ために、 に and へ

This topic contains 4 replies, has 3 voices, and was last updated by  ルイ 12 years, 8 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #23448

    ルイ
    Member

    So a while back I read the lesson on purpose and ために.
    Something confused me – and still does! – so I figured I’d ask.

    There are these two, very similar example sentences on how to use ために in the lesson:

    1.
    In order to buy a game, I will go to a video store
    ゲーム を かう ために ビデオや へ いく

    2.
    In order to eat sushi, I will go to a restaurant.
    すし を たべる ために レストラン に いく

    Will somebody please tell me why Koichi used へ in one sentence and に in the other? Not to mention, what is へ even? It isn’t explained in the lesson, nor was it explained in any of the previous lessons (unless I forgot about it somehow..?)

    Thanks!

    #23454

    Hatt0ri
    Member

    に has a bit wider use than へ, which is used only for locations. You can compare it with “to” and “at” in English (but it’s not a literal translation of those particles, just a comparison of usage).

    For example, you can use に in sentences like:
    Go to Tokyo.
    Give book to someone.

    But へ is only used for locations:
    Go at a restaurant.

    Also, へ is read え, not the way it’s supposed to be read.

    #23455

    ルイ
    Member

    Thank you Hattori, that’s a great explanation.

    That means that に and へ would both be valid in any of the two sentences, right?

    #23462

    Joel
    Member

    Yah, either would be valid here.

    That said, I’m going to have to disagree with one thing Hattori said – に does have a wider use than へ, but へ is always used for direction of travel (not location). It’s always translated as “to” or “towards” or (in occasional situations) “into”.

    The particle in “eat at a restaurant” would be で…

    #23472

    ルイ
    Member

    Thanks for clearing that up, Joel!

    And now, off へ bed…

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.