| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
.cc, moving its contents into the new stepdown.cc and strings.cc.
(The latter also got many donations from libutil.h.)
Down with stuff! Up the new flesh!
|
| |
|
|
| |
This fixes all the instances caught by unbrace.
|
| | |
|
| |
|
|
| |
I think this is a good addition to the grunt language :)
|
| | |
|
| |
|
|
|
| |
[Committer's note: You squash Grunt's and pubby's patches like
a feature!!!!!]
|
| |
|
|
|
| |
Sometimes, they're there to emphasize a break between two sections of code,
which is good. In a majority of cases, though, they're just inconsistent.
|
| |
|
|
|
| |
Via externs.h -> bitary.h, it was effectively included by everything anyway,
and this way simplifies include chains.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The whole Elder Futhark, in fact. There's a couple runes taken from the
Old English version as well as they are missing from the norse one, and
having no 'y' would making modern text harder to understand.
Unlike Cyrillic, there are no problems with transcription, as instead of
phonetic spelling (nearly impossible to do well programmatically), English
ortography mostly records the actual pronounciation from old times. Well,
these times are quite a bit younger than when it was written in runes, yet
I think it's safe to say no Viking or Anglo-Saxon will come up and say this
is wrong.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is a misdesign in the standard, the committee is debating whether it's
a defect or not, we'll know the result in ten years or so. In the meantime,
gcc-4.8 and clang(version?) added a fix so formerly legal code compiles (but
with a warning...). This fix is not yet in gcc-4.7 nor clang-3.1, and since
failing to build on compilers that happen in the wild is a bad idea, let's
kludge it around with spaces.
More info: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52538
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I had to rename distance() (in coord.h) to distance2() because it conflicts
with the STL function to compare 2 iterators. Not a bad change given how it
returns the square of the distance anyway.
I also had to rename the message global variable (in message.cc) to buffer.
I tried to fix and improve the coding style has much as I could, but I
probably missed a few given how huge and tedious it is.
I also didn't touch crawl-gdb.py, and the stuff in prebuilt, rltiles/tool
and util/levcomp.*, because I have no clue about those.
|
| | |
|
| |
|
|
| |
Ok, perhaps not translation, but I'm sure it's some "transl-" word.
|
| | |
|
| |
|
|
|
| |
Sorry folks who use it, but that was expected. And the fake lang wasn't
supposed to last longer than a day anyway...
|
| | |
|
| |
|
|
|
|
| |
It was good enough for a single day throw away joke.
Also, don't store a copy of the language for every db object.
|
| |
|
|
|
|
| |
Note that it works only on console and webtiles, not local tiles -- which is
a bug that needs to be fixed before any real translations come. Polish letters
are already screwed up there.
|
|
|
I intend to name actual per-language C++ files lang-en.cc, lang-pl.cc
|
