Giter VIP home page Giter VIP logo

riichibooks's People

Contributors

blankaex avatar dainachiba avatar phoe avatar stephenmk 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

riichibooks's Issues

wait pattern

Got the following suggestion from a reader.
Dashes (hyphens) in wait patterns may be confusing. For example, the winning tiles for "55567m, South, South" are denoted as "5m-8m South", which some people may interpret as "5m, 6m, 7m, 8m South".

I (kind of) explained this on page 56, which reads "Winning tiles of side-wait protoruns are often denoted with a hyphen in the middle, such as 1s-4s or 5p-8p." I guess I could add a footnote there to explain that "1s-4s" is not to be confused with "1s 2s 3s 4s".

Will do this update when I have time.

Add continuous integration

The problems at #5 currently make me think that it is non-trivial to build Riichi Book on one's own - for instance, piemf fonts need to be downloaded and installed manually, I encountered encoding issues that prevented some Japanese text in piemf TeX files from compiling, and the fonts that I had installed (I had texlive-full installed on Ubuntu) did not fully match the ones in the PDF.

My suggestion is to have GitHub's continuous integration, Travis, try and build the PDF automatically on each commit or pull request to the repository. That will make it unnecessary to manually build and upload the book on each text change, make it possible easier for other people to build the book from scratch, and will check that all commits result in valid and buildable TeX code.

I will try to do this on a fork of this repository, as soon as I figure out the steps to build the book myself at #5. Then I will try to reproduce these steps on a clean Linux installation, which will in turn make it possible to tell Travis how to build it.

Resolve build warnings

The LaTeX build process at https://travis-ci.com/riichi/RiichiBooks/ emits a series of warnings, mostly about substituted fonts and unknown references. We will need to figure out which of these warnings need to be fixed and which ones, well, we can ignore.

@dainachiba Could you provide compilation logs from building the book on your own machine? We'll need to figure out if any warnings that you get also need to be fixed.

Polish translation

Hey, I'd be willing to work on translating the Riichi Book into Polish and then maintaining it to keep it up to date. Is there anything I should be aware of before beginning the work?

Building Riichi Book

Hey, I am attempting to build piemf-2.0.2 downloaded from the riichibook repository, but it fails for me on Ubuntu 16.04.6 LTS.

┌─[phoe][~/.texmf/tex/latex/piemf-2.0.2]
└─▪ ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/emiherd/.texmf/tex/latex/piemf-2.0.2/missing: Unknown `--is-lightweight' option
Try `/home/emiherd/.texmf/tex/latex/piemf-2.0.2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking whether make supports nested variables... yes
checking dependency style of gcc... none
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating macros/Makefile
config.status: creating omake/Makefile
config.status: creating src/Makefile
config.status: creating test/Makefile
config.status: creating README
config.status: executing depfiles commands
┌─[phoe][~/.texmf/tex/latex/piemf-2.0.2]
└─▪ make
Making all in macros
make[1]: Entering directory '/home/emiherd/.texmf/tex/latex/piemf-2.0.2/macros'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/emiherd/.texmf/tex/latex/piemf-2.0.2/macros'
Making all in omake
make[1]: Entering directory '/home/emiherd/.texmf/tex/latex/piemf-2.0.2/omake'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/emiherd/.texmf/tex/latex/piemf-2.0.2/omake'
Making all in src
make[1]: Entering directory '/home/emiherd/.texmf/tex/latex/piemf-2.0.2/src'
for i in bjtenex canonex cx ljfzzz vtftzzhi ; \
do \
	makepk.sh $i ; \
done
/bin/bash: line 2: makepk.sh: command not found
/bin/bash: line 2: makepk.sh: command not found
/bin/bash: line 2: makepk.sh: command not found
/bin/bash: line 2: makepk.sh: command not found
/bin/bash: line 2: makepk.sh: command not found
Makefile:404: recipe for target 'default' failed
make[1]: *** [default] Error 127
make[1]: Leaving directory '/home/emiherd/.texmf/tex/latex/piemf-2.0.2/src'
Makefile:344: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Looks like the issue is at

/bin/bash: line 2: makepk.sh: command not found

What is makepk.sh? Should it come from the LaTeX installation?

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.