HTML draft fails output naming
This discussion is connected to the gimp-docs-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
| HTML draft fails output naming | liangtai | 02 Feb 17:26 |
| HTML draft fails output naming | Ulf-D. Ehlert | 03 Feb 12:28 |
| HTML draft fails output naming | liangtai | 04 Feb 16:15 |
HTML draft fails output naming
Hello all.
I want a small change of makefiles at the top directory. Please replace `sed'
command into ${SED}, otherwise BSD sed will fail at `t' command within one
line
script separated by semicolons(;), so the HTML draft procedure names always
its
result noname-draft.html. Fortunately the configure script finds the proper
command /usr/local/bin/gsed, and it is assigned to a term `SED' automatically.
=/=/=
It's late that I introduce myself. I want to join in the gimp-doc team as a
Japanese translator. I had begun to work, at November of last year,
on HTML files and XML files of the 2.4.2 release package. Later registering
to the
mailing list, I shifted my work on XML files copied from the subversion trunk.
Now I have 76 HTML and 52 XML files at Japanese version.
I do not understand well the right way to edit, but I suppose you all work on
PO files.
I don't know how to append new paragraphs or images on PO.
Note that the message translators, not me, are already working at gnome-
translation
team, and providing comprehensive PO files for versions from earlier to the
latest.
???? (SimaMoto, RyoTa) http://www.geocities.jp/ss2pxd1c/
-------------------------------------- Yahoo! JAPAN - Internet safety for children and parents. http://pr.mail.yahoo.co.jp/security/
HTML draft fails output naming
liangtai (Montag, 2. Februar 2009, 17:26):
I want a small change of makefiles at the top directory. Please replace `sed' command into ${SED}, otherwise BSD sed will fail at `t' command within one line
script separated by semicolons(;), so the HTML draft procedure names always its
result noname-draft.html. Fortunately the configure script finds the proper command /usr/local/bin/gsed, and it is assigned to a term `SED' automatically.
I have changed the sed command, hope it works for BSD now (and I've also committed two forgotten sed's).
Does BSD provide two different sed programs, "sed" and "gsed"?
=/=/=
It's late that I introduce myself. I want to join in the gimp-doc team as a Japanese translator.
Great! :-)
I had begun to work, at November of last year, on HTML files and XML files of the 2.4.2 release package. Later registering to the
mailing list, I shifted my work on XML files copied from the subversion trunk. Now I have 76 HTML and 52 XML files at Japanese version.
I do not understand well the right way to edit, but I suppose you all work on PO files.
I don't know how to append new paragraphs or images on PO.
With the gettext-based build system, all translations are done by
editing the po files.
I hope you didn't edit/translate the HTML files directly, these
translations were lost (except for paste & copy).
Adding new content or new images is now done by editing the English source files.
You can provide a localized version of any image 'images/C/foo/bar/baz.png' as 'images/jp/foo/bar/baz.png' ("C" replaced with Japanese locale "jp"(?)). Without localized image the English ("C") image will be used.
Note that we are still experimenting and looking for the right way to do everything...
Of course, feel free to ask if you have any problem.
Welcome to the team! :-)
Ulf
HTML draft fails output naming
Thank you for your quick amendment and kindness of receiving my impudent suggestion, although my explanation was not too well illustrated. Now Makefile works fine.
»gsed« is the GNU sed, which allows any one-line style sed scripts with semicolons even they contain advanced commands, but the BSD sed can not accept them. So, I installed the GNU sed through the BSD ports system into my PC, while the BSD sed is bundled with the official releases. Some GNU commands are prefixed a letter »g«, such as gmake and gtar, so that their names can avoid confliction with names of some BSD commands which are already installed.
I do not feel easy to work on PO than XML for translation, because I found gettext system sometimes tend to depend on the English grammar, particulary in sentences including few words or automatic placeholders. I made a plan that I will write all XML files before edit PO files, and my first contribution will be at November this year with »one patch« of PO files. I hope to giving suggestion about addition of paragraphs or images, and resolution around gettext system (if I can) after these days.
???? (SimaMoto, RyôTa)
-------------------------------------- Yahoo! JAPAN - Internet safety for children and parents. http://pr.mail.yahoo.co.jp/security/
