Domino English Translation

Domino is a MIDI editor that is used for creating MIDI songs/musics. Domino is used by various blackers in the Black MIDI ecosystem.

Since Domino is an abandonware, and it's original language is Japanese, many people tried to translate it using resource editing tools. Some of it are outdated, while others are incomplete.

This repository is made to unify the translations made by community, while trying to complete it for easier usage.

Usage

1. Download either the Domino .zip or the .exe.

   • The .zip contains everything you need to run Domino. Download this if you are not sure or this is your first time using this program.
   • You can also download the .exe if you want to use your configured settings. Place it inside your Domino directly, where "Domino.exe" placed.

   

2. Recommended: Download the dominohook .dll file and bind it to the executable. Read how to bind it here. In the future, I will find a way so I could distribute it with the hook.

3. Run the executable.

   • If you downloaded the .zip, just run Domino.exe.
   • If you downloaded the .exe, after placing it on the directory, run Domino_Translated.exe (make sure you rename it so you know which one's the new version!).

Building

Requirements

• Windows operating system. This is a Win32 application.
• Windows Subsystem for Linux (WSL)
• Resource Hacker
• Python 3

Howto

Just run compile.sh, and the binaries (the .exe files) will be compiled and placed inside the _compile folder.

Contributing

You can contribute by translating various files. The .rc files contains the most of the program's strings. There is also .html files for the manuals, .xml for the modules, and some .txt's.

Read Building to get the binary files.

For starters, you can make a pull request from your fork, and the I'll check and merge it. If you don't know how to do it, make sure to read one of this guides.

• How to Contribute to Open Source | Open Source Guides
• How to create a pull request in GitHub | Opensource.com
• Creating a pull request - GitHub Help

TL;DR, here's how.

1. Fork this repository by clicking the "Fork" button above.
2. Make a branch in your fork. (optional)
3. Do your edits there and commit (and push) the changes.
4. Create a pull request by clicking the "New pull request" button.

If you are still confused, you can ask me on the issue board or on Discord (Hans5958#0969).

Completion Checklist

✅ Dialog

Expand to view the checklist.

• 100
• 131
• 132
• 133
• 134
• 135
• 136
• 137
• 138
• 139
• 144
• 145
• 146
• 148
• 149
• 150
• 151
• 152
• 153
• 154
• 155
• 156
• 157
• 158
• 159
• 160
• 161
• 162
• 163
• 164
• 165
• 166
• 167
• 168
• 169
• 170
• 171
• 172
• 173
• 174
• 187
• 188
• 213
• 216
• 217
• 219
• 240
• 266
• 267
• 268
• 269
• 270
• 272
• 273
• 275
• 276
• 277
• 278
• 279
• 280
• 281
• 282
• 283
• 284
• 285
• 286
• 288
• 289
• 290
• 291
• 292
• 293
• 294
• 295
• 296
• 297
• 298
• 299
• 300
• 301
• 302
• 303
• 304
• 305
• 306
• 307
• 308
• 309
• 310
• 311
• 312
• 313
• 314
• 315
• 316
• 317
• 318
• 319
• 320
• 321
• 322
• 323
• 324
• 325
• 326
• 327

✅ Menu

Expand to view the checklist.

• 128
• 130

✅ String Tables

Expand to view the checklist.

• 1
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18
• 19
• 20
• 21
• 22
• 23
• 24
• 25
• 26
• 27
• 28
• 29
• 30
• 31
• 32
• 33
• 34
• 35
• 36
• 37
• 38
• 39
• 40
• 41
• 42
• 43
• 44
• 45
• 46
• 47
• 48
• 49
• 50
• 51
• 52
• 53

⬜️ Manual

Expand to view the checklist.

• index.html
• install.html
• module.html
• other.html
• use.html
• assets...

⬜️ Module

Expand to view the checklist.

• GMLevel1.xml
• ok_GSm.xml
• ok_XG2k.xml
• ok_XGb.xml
• SC-88Pro.xml
• SC-8850.xml

✅ System

Expand to view the checklist.

• CurveCustom.txt
• Exclusive.txt
• Formula.txt
• ParamMap.txt

✅ 240

Expand to view the checklist.

• 134
• 136
• 156
• 165
• 174
• 217
• 275
• 277
• 279
• 280
• 281
• 290
• 293
• 295
• 297
• 299
• 300
• 301
• 306
• 307
• 319
• 322

✅ Other

Expand to view the checklist.

• readme.txt