Giter VIP home page Giter VIP logo

nrgrammar's Introduction

An introduction to Japanese - Syntax, Grammar & Language

This is the repository for the data that is used to generate the book "An introduction to Japanese", previously found at http://www.amazon.com/dp/9081507117 and other stores.

I've taken this book off the market (because I cancelled my account with my publisher and will be looking at a new way to do publishing) but the book is still available in PDF form.

I've been running it as a dokuwiki for a few years on http://grammar.nihongoresources.com and that has proven to be useful, but progressively harder to maintain as dokuwiki changes its APIs, and my content relies on specific dokuwiki plugins for which I don't have time to actually update them to work with the new versions.

So, I'll be trying to rewrite it to a self-contained website that you can file github issues for, with a php compiler to turn the raw data into .pdf data.

Interesting fact: just because someone's front door is open doesn't mean you have the right to take their stuff, and in the same vein: just because I'm hosting this on a public repository does not give you the right to use the code and raw data for your own purposes.

This book is free for the general public in PDF form, and available as the more traditional (affordable, gasp!) paper textbook version at book retailers, but this is a product, not a project: all code and data is owned by me, Mike "Pomax" Kamermans, and I reserve all rights. You expressly do not have permission to start compiling your own version (except to test the compilation from plain text to .pdf), nor do you have permission to distribute this code or data yourself.

You are, however, welcome to help improve the text, or suggesting compile improvements, by filing issues or submitting pull requests. Contributions deserve acknowledgements in the book's acknowledgement section.

Live site: https://Pomax.github.io/nrGrammar

Development

Compilation of book relies on some older technologies in part because it was initially created back in 2008 when PHP was still the king of "get shit done fast" scripting langauges for people who needed one scripting language to do everything from CLI to web content (was has since been replaced by JavaScript), and LuaTex was still four years away from a version 1, making the only sane TeX choice XeLaTeX (because XeTeX is natively utf8, rather than needing special instructions just to understand utf8 documents).

Localisation

Localised content is housed in ./data/pages, where each locale uses its own locale code as directory name. Inside of those, all files should follow the filename convention as used in the en-GB directory, in order for the compilation scripts to find them.

Translations should follow the spirit of the text, not the letter of text: if an idiom or illustratrive piece of text does not work in the language you're targeting, please do not translate it literally. The worst thing you can do when translating is to take text that works in one language, and force-translating it to a weird, clunky text in a different language. Sometimes that might mean rewriting an entire paragraph, or even more than one, in order for the discourse to flow naturally in your target language: that is fine. It is in fact infinitely preferable over a literal translation that isn't up to whatever is considered university-level langauge in the country/region you're localizing for.

nrgrammar's People

Contributors

aaeegg avatar jcoveney avatar konstantin-glukhov avatar makemek avatar nayuki avatar pomax avatar qsantos avatar ryanbreaker avatar unwitting avatar vvye avatar zooxyt avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

nrgrammar's Issues

License?

I've always been fascinated by "open source" books, not in the sense that I want to steal their contents, but in the sense oh cool their infrastructure is open, (so if you wanted to start making your own book, you would have a template to start) Since most books that are ever published, you have absolutely no idea, how are they made? Which software do they use? Do they use TeX? or propietary technologies?

I know this is not code, but a license would be nice to have even if not open source, source available, what not.

EPUB format?

Hi, I've glanced over your book and it seems very well-structured. Certainly a breath of fresh air from the heavily European-influenced mess that is traditional "Japanese grammar" in the West.

I was hoping to read this on my Kindle Paperwhite, which does technically have PDF support but it is very poor. Similarly, the HTML version is not well-supported by its browser. Do you have any plans to convert this to EPUB?

A bit dissapointed after reaching chapter 2

A lot of my friends were linking me the guide and after I finished chapter 1 I thought wow this is the best overview of Japanese ever. The author truly understands all the differences between the languages and gives a brief history of how kanji evolved etc. However after reaching chapter 2 it became completly unreadable for me... it went from a thing an average person could read and understand in simple terms, to a scientific journal for PHD linguistics students. I appreciate the fact that everything is so in depth but its just impossible for me to read without my brain starting to hurt, I don't know all the fancy words like inflection... I am not a linguistics student, I am just a normal dude trying to understand Japanese.

Another thing that was mind boggling for me is that the guide went from using romaji and then the next chapter completly switching to complex kanji without furigana! Why is it so hard to just keep the romaji and furigana? You have to realise not everyone has the same learning process, not everyone learns kanji first, some people only learn kanji in order of JLPT levels, some learn all 3000 at once, some like me leave that until later. I started with core 10k vocab + grammar + watching tv shows / anime in between. So far I got by reading furigana just fine and plan to start kanji studies several months later.

I don't know why I made this issue because I doubt you would be willing to change the guide, the ideal guide I can picture in my head would have two sections or even two separate guides, an easy to read overview with charts showing all the particles and rules in one place, kinda like a quick reference guide and then the other part being the very in depth version explaining everything.

Anyway this is just a perspective of someone starting out and finding your guide, I just wanted you to see things from a different perspective, please close this issue if you want.

Section 1-2 should more explicitly state that っ represents consonant elonagation

Currently the wording describing the use of っ says this:

In Japanese, because there are no actual 'loose' consonants, the doubling is represented by a special character: a つ (or ツ) written either half height (in horizontal writing) or half width (in vertical writing) to indicate the pause.

This is not clear that っ actually represents consonant gemination, not merely a pause. For words like 雑誌 (ざっし) the difference becomes clear. Rather than a pause followed by a "sh" sound, the "sh" sound is simply twice as long. The wording should be updated to reflect this. It may also be advisable to add example words which show this difference.

Set Phrases

data/pages/en-GB/set_phrases.txt:

お先に:
The origin of this phrase is お先に失礼します. Also the reply to it, ご苦労様くろさまでした should only be spoken to people of lower rank. Another valid response would be: お先にどうぞ (Go ahead).

はじめまして:
More formal version is 初めてお目にかかります

1.4.2 transitive verbs

You can actually say “swim the ocean” because swim is both a transitive verb and an intransitive verb (and a noun), if you look it up in a dictionary. The same seems to hold for many other traversal verbs. Further, note that a transitive verb not just can be used with a direct object, but it’s mandatory. I just can’t find an example where a word is only transitive verb, but e. g. the verb “give” is almost always used with a direct object (and an indirect object). A lookup of the Japanese verb 「泳ぐ」(to swim) didn’t yield any specification of whether it’s 自動詞 or 他動詞.

Sticky: How to help out, or suggest changes [click this to find out how to contribute]

This data is open to contributions

Typos? Missing, incomplete, or wrong explanations? Suggestions to improve the book on the whole? If you have a github account (which are free to set up) you can actually edit the files on this repository and send those changes my way automatically in a fairly simple, painless way.

Spotted a typo?

Cool! If you spot any typos and you want to fix them, head over to one of the chapters, open them in your browser, and then hit the "edit" button in the upper-ish right (next to 'raw', 'blame', etc).

Simply fix the typo, and then at the bottom of the page in the comment-form-looking-form, add a quick description of the changes. Then hit the big green button and I'll be notified of the change you'd like to see made. All I have to do is press another big green button and the change'll be committed for the rest of the world to see.

Missing something?

If you think the book should have something that it currently doesn't, then file a "new issue", with a short subject descriptor, and an "as long as you feel it needs to be to describe what you think should be added" description, and I'll be automatically notified of your request.

some other idea?

Just file an issue and describe what you'd like to see happening, and we can discuss it as much as we like and/or need to.

Improve 未然形 of adjectives?

In chapter "Verb grammar", section "Inflection bases", the 未然形 of various adjectives is given as 高く, 楽しく, 薄く and 大きく. Similarly, in section "Basic inflections", the 未然形 of ない is said to be なく.

However, the Wiktionary gives 高かろ, 楽しかろ, 薄かろ, 大きかろ and なかろ. This way feels more consistent with section "Pseudo-future: おう/よう" from chapter "More grammar", since the pseudo-future is then made simply by adding "う" to the 未然形 of either verbs or verbal adjectives. Granted, this then implies changing the description of the negations of verbal adjectives.

Is the 未然形 of adjective a strictly-defined thing? If so, which way is the correct way? If not, which one is the more practical?

Thanks for clarifying this part!

〆 symbol meaning

"kanji sentence finaliser" sounds a bit odd!

I'd say "closing mark" is a more convenient, short, description!

add @font-face rules for the CJK radicals and extension B glyphs used.

This would require:

  • inventory which characters are used from which blocks (this should be easily scriptable: just run through the content files and build a list of used codepoints, then dump that to a file)
  • determine which free font(s) can act as basis for creating a dedicated subset font
    • the book itself already uses HAN NOM A and B, so we might be able to just subset out of those.
    • alternatively Hanazono might work?
  • making a subset WOFF file with radical coverage.

2.1.1 Inflection bases example tables

The example tables immediately following the sentence:

Having covered the "what they look like", let's look at what this means for a number of verbs from both classes, and for verbal adjectives:

both have the heading "五段 verbs" - presumably one was supposed to be "一段 verbs"?

2.1.2.1 Particles

Moreover, in the Japanese きれいに 分わ ける, translating to the English "to divide cleanly", the に marks the noun きれい, "clean/neat/tidy", as being used adverbially, "neatly, cleanly".

Is きれい not an adjective rather than a noun as the sentence says?

Logical inconsistency in the paragraph about copula past tense

Section 2.3.22 - Past tense
...
The common explanation for だ is that it came from で, the continuative of です, and the verb ある, to form the copula である. This copula is actually still used in modern Japanese in formal settings. However, the で+あ in this である has contracted over time, to form だる, which explains the 未然形 for だ, which is だろ.

  1. The first highlighted statement is inconsistent with でし (連用形 of です introduced earlier in section 2.3.2)
  2. The second highlighted text presents a statement with implied premises not obvious to the reader. Since 未然形 of ある is あら it is not obvious how だろ sprang from だる. Detailed explanation of だろ etymology will dramatically improve the clarity of the paragraph.

Essential particles→と, 考える example

The section on 'Essential particles'→と gives an example with 考える (to think):

"Another example is the verb 考える, which means "to think" when used with を, but "to think about" when used with と."

However, looking at examples of 考える over at WWWJDIC, it looks like the reverse (i.e. X と 考える meaning 'think that X', and X を 考える meaning 'think about X') fits better.

What I was looking for was some help at baby's first translation attempt, so I'm inclined to go with the WWWJDIC examples, but this seeming contradiction had me curious.

Set up an automated build

Although the challenge here is of course that all the fonts used to build this book are not free and cannot be put on github. They'd have to get pulled in by something like Travis from "somewhere" in a way that others cannot equally simply (illegally) download from.

Small issue about て-form of 軋む

In section 3.2.3.1, the example sentence そのドアがよく軋っています seems to suggest that the て-form of 軋む is 軋って, whereas it is in fact 軋んで. I could be mistaken as I am a beginner.

Kanji is hard to read in mobile view

The text size for kanji with furigana is tiny in mobile browsers like Chrome for android. Hiragana and Katakana do not face this problem. One has to zoom in almost every few seconds for reading the kanji because of the minute scale which is very inconvenient. Here's a screenshot for reference.

screenshot

It would be great if the guide could be optimized for mobile devices.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.