1 |
Gigedit |
2 |
======= |
3 |
|
4 |
Gigedit is an instrument editor for gig files. Gig files are |
5 |
used by software samplers such as LinuxSampler and GigaStudio. |
6 |
|
7 |
With gigedit it is possible to modify existing gig files and also to |
8 |
create completely new instruments from scratch. Gigedit can be run as |
9 |
a stand-alone application, or as a plugin to LinuxSampler. |
10 |
|
11 |
Please note that this is an early version that only includes the most |
12 |
basic features needed to create and edit gig files. There is still a |
13 |
lot to do, fix and improve. |
14 |
|
15 |
Be sure to backup your original gig files before editing them in |
16 |
gigedit. |
17 |
|
18 |
The latest version of gigedit can be found at: |
19 |
|
20 |
https://www.linuxsampler.org |
21 |
|
22 |
Questions, bug reports and suggestions can be sent to LinuxSampler |
23 |
developer's mailing list: |
24 |
|
25 |
linuxsampler-devel@lists.sourceforge.net |
26 |
|
27 |
|
28 |
License |
29 |
======= |
30 |
|
31 |
Gigedit is licensed under the GNU General Public License. See the file |
32 |
COPYING for details. |
33 |
|
34 |
|
35 |
Requirements |
36 |
============ |
37 |
|
38 |
Gigedit requires gtkmm, libgig and libsndfile libraries. There is an |
39 |
optional dependency to LinuxSampler, for being able to play |
40 |
instruments while editing. Also optional is the dependency to gettext |
41 |
for internationalization support. |
42 |
|
43 |
|
44 |
Installation |
45 |
============ |
46 |
|
47 |
On a POSIX system like Linux or OSX you should only have to call the |
48 |
following on the console: |
49 |
|
50 |
./configure |
51 |
make |
52 |
su -c "make install" |
53 |
|
54 |
See the file INSTALL for details about these steps and options. |
55 |
|
56 |
Windows users shall read the respective README file in the "win32" |
57 |
directory for compilation instructions. |
58 |
|
59 |
|
60 |
Building from CVS |
61 |
================= |
62 |
|
63 |
./autogen.sh |
64 |
./configure |
65 |
make |
66 |
su -c "make install" |
67 |
|
68 |
|
69 |
Internationalization: Help on Translations ! |
70 |
============================================ |
71 |
|
72 |
You want to help us translating gigedit into a language you speak? Good! |
73 |
This is how it works: |
74 |
|
75 |
Updating an existing translation (at the moment only Swedish and German): |
76 |
------------------------------------------------------------------------- |
77 |
|
78 |
First collect all text from gigedit's current C++ source code, by typing |
79 |
the following: |
80 |
|
81 |
cd po |
82 |
make update-po |
83 |
|
84 |
The language source files (de.po, sv.po, ...) are now updated and you may |
85 |
open one of it now either with a text editor of your choice or better: by |
86 |
using the graphical translation tool "poedit": |
87 |
|
88 |
poedit de.po |
89 |
|
90 |
|
91 |
Add a new translation (for another language not yet supported): |
92 |
--------------------------------------------------------------- |
93 |
|
94 |
First collect all text from gigedit's current C++ source code, by typing |
95 |
the following: |
96 |
|
97 |
cd po |
98 |
make update-po |
99 |
|
100 |
There should now be a yet untranslated file "gigedit.pot". Rename it to |
101 |
to the language you want to translate, i.e.: |
102 |
|
103 |
mv gigedit.pot ru.po |
104 |
|
105 |
Now either open the file ("ru.po") with a text editor of your choice or |
106 |
better: by using the graphical translation tool "poedit": |
107 |
|
108 |
poedit ru.po |
109 |
|
110 |
After you are done with translating the language file, please send it to us! |