Help building help.
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.
| Help building help. | john Culleton | 11 Jun 18:41 |
| Help building help. | Ulf-D. Ehlert | 12 Jun 20:17 |
| Help building help. | Marco Ciampa | 13 Jun 08:00 |
| Help building help. | Roman Joost | 26 Jun 06:14 |
| Help building help. | Marco Ciampa | 26 Jun 12:58 |
| Help building help. | Alexandre Prokoudine | 26 Jun 13:04 |
| Help building help. | Roman Joost | 01 Jul 07:36 |
| Help building help. | Marco Ciampa | 21 Jul 00:57 |
| Help building help. | Marco Ciampa | 21 Jul 01:13 |
| Help building help. | Jihui Choi | 18 Aug 12:19 |
| Help building help. | Marco Ciampa | 18 Aug 14:02 |
| Help building help. | Marco Ciampa | 18 Aug 14:32 |
| Help building help. | Jihui Choi | 18 Aug 15:43 |
| Help building help. | Marco Ciampa | 19 Aug 09:04 |
| Help building help. | Jihui Choi | 19 Aug 10:01 |
| GIMP doc on Cygwin | Kolbjørn Stuestøl | 07 Sep 12:15 |
| GIMP doc on Cygwin | Marco Ciampa | 07 Sep 17:04 |
| GIMP doc on Cygwin | Kolbjørn Stuestøl | 08 Sep 08:49 |
| GIMP doc on Cygwin | Julien Hardelin | 10 Sep 19:30 |
| GIMP doc on Cygwin | Kolbjørn Stuestøl | 10 Sep 21:25 |
| Updating quickreference | Kolbjørn Stuestøl | 10 Sep 22:13 |
| Updating quickreference | Alexandre Prokoudine | 11 Sep 04:11 |
| Updating quickreference | Kolbjørn Stuestøl | 11 Sep 17:04 |
Help building help.
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed. What I got instead was a package with the guts of the manual in xml. I tried autogen, then ./configure, and then make. Consistently I get these error messages:
Making all in quickreference
make[1]: Entering directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No
rule to make target `svg/gimp-keys-ca.svg', needed by `svg'. Stop.
make[1]: Leaving directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make: ***
[all-recursive] Error 1
Before I start hacking around eliminating references to the quickreference is there a standard solution to my problem?
I don't want to spend days learning about docbook, wonderful though it may be. I have a project under way and I need to look some things in the manual.
Anyone have a copy they are willing to share? Slackware 14 if anyone cares.
John Culleton Wexford Press Free list of books for self-publishers: http://wexfordpress.net/shortlist.html PDF e-book: "Create Book Covers with Scribus" available at http://www.booklocker.com/books/4055.html
Help building help.
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed.
Making pdf always was problematic for some languages, the html manual is IMO a better choice. BTW, do you really want to print some hundred pages?
What I got instead was a package with the guts of the manual in xml.
A "package" means you didn't pull the current version from the git repository?
I tried autogen, then
./configure, and then make.
You must try
make pdf-en # "en" for the English version
since pdf is not built by default. (And making pdf does not require the quickreference.)
Consistently I get these error messages:
Making all in quickreference make[1]: Entering directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No rule to make target `svg/gimp-keys-ca.svg', needed by `svg'. Stop. make[1]: Leaving directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make: *** [all-recursive] Error 1
If I remember correctly, this was a bug which has been fixed in the current version from the git repo.
I have a project under way and I need to look some things in the manual.
What's wrong with the online manual? ;)
Ulf
Ob selbst das schnste Buch den Wald aufwiegt, der dafr stirbt? -- Karlheinz Deschner
Help building help.
On Wed, Jun 12, 2013 at 10:17:50PM +0200, Ulf-D. Ehlert wrote:
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed.
Making pdf always was problematic for some languages, the html manual is IMO a better choice. BTW, do you really want to print some hundred pages?
PDF pages are no longer just for print but a mean to read with computer / tablet / ebook reader. I myself use a kindle to read GIMP books in PDF in the spare time.
I would not underestimate the importance of the pdf format for a manual.
What I got instead was a package with the guts of the manual in xml.
A "package" means you didn't pull the current version from the git repository?
Yes I know of may Mac users of GIMP that use updated tar packages of the manual that I feed them sporadically...
I tried autogen, then
./configure, and then make.You must try
make pdf-en # "en" for the English version
since pdf is not built by default. (And making pdf does not require the quickreference.)
Consistently I get these error messages:
Making all in quickreference make[1]: Entering directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No rule to make target `svg/gimp-keys-ca.svg', needed by `svg'. Stop. make[1]: Leaving directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make: *** [all-recursive] Error 1If I remember correctly, this was a bug which has been fixed in the current version from the git repo.
I have a project under way and I need to look some things in the manual.
What's wrong with the online manual? ;)
That you have to be on line...
Ulf
--
Ob selbst das schnste Buch den
Wald aufwiegt, der dafr stirbt?
-- Karlheinz Deschner
_______________________________________________ gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
Help building help.
On Thu, Jun 13, 2013 at 10:00:12AM +0200, Marco Ciampa wrote:
On Wed, Jun 12, 2013 at 10:17:50PM +0200, Ulf-D. Ehlert wrote:
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed.
Making pdf always was problematic for some languages, the html manual is IMO a better choice. BTW, do you really want to print some hundred pages?
PDF pages are no longer just for print but a mean to read with computer / tablet / ebook reader. I myself use a kindle to read GIMP books in PDF in the spare time.
I would not underestimate the importance of the pdf format for a manual.
Perhaps it would make better sense, to remove the PDF functionality (based on dblatex), since it never left a stable stage.
The reason to choose dblatex was that FOP at the time was not mature enough to produce good quality output. I think that has changed. DbLatex worked well for latin content, but always seemed to give us headaches with totally different character sets. Perhaps it's not dblatex fault, just the lack investigating a good LaTeX -> PDF solution.
Anyhow, perhaps it makes more sense to move to a epub/Kindle solution. I can relate to Marco here, since I'm also using my Kindle to read most of my books now. The Kindle format is even simiar to HTML. Not sure if there are already packages out there who go from DocBook to Kindle/epub.
Cheers
Roman Joost www: http://www.romanofski.de email: romanofski@gimp.org
Help building help.
On Wed, Jun 26, 2013 at 04:14:42PM +1000, Roman Joost wrote:
On Thu, Jun 13, 2013 at 10:00:12AM +0200, Marco Ciampa wrote:
On Wed, Jun 12, 2013 at 10:17:50PM +0200, Ulf-D. Ehlert wrote:
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed.
Making pdf always was problematic for some languages, the html manual is IMO a better choice. BTW, do you really want to print some hundred pages?
PDF pages are no longer just for print but a mean to read with computer / tablet / ebook reader. I myself use a kindle to read GIMP books in PDF in the spare time.
I would not underestimate the importance of the pdf format for a manual.
Perhaps it would make better sense, to remove the PDF functionality (based on dblatex), since it never left a stable stage.
The reason to choose dblatex was that FOP at the time was not mature enough to produce good quality output. I think that has changed. DbLatex worked well for latin content, but always seemed to give us headaches with totally different character sets. Perhaps it's not dblatex fault, just the lack investigating a good LaTeX -> PDF solution.
Anyhow, perhaps it makes more sense to move to a epub/Kindle solution. I can relate to Marco here, since I'm also using my Kindle to read most of my books now. The Kindle format is even simiar to HTML. Not sure if there are already packages out there who go from DocBook to Kindle/epub.
There are powerful converters out there. See for example the Git book that is written in markdown and the pandoc suite or Calibre.
References:
http://git-scm.herokuapp.com/book http://git-scm.herokuapp.com/blog/2009/07/28/the-gory-details.html http://www.slideshare.net/larrycai/write-book-in-markdown http://johnmacfarlane.net/pandoc/epub.html http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html https://github.com/LaPingvino/markdown-example-book http://calibre-ebook.com/
bye
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
Help building help.
On Wed, Jun 26, 2013 at 10:14 AM, Roman Joost wrote:
On Thu, Jun 13, 2013 at 10:00:12AM +0200, Marco Ciampa wrote:
Anyhow, perhaps it makes more sense to move to a epub/Kindle solution. I can relate to Marco here, since I'm also using my Kindle to read most of my books now. The Kindle format is even simiar to HTML. Not sure if there are already packages out there who go from DocBook to Kindle/epub.
http://sourceforge.net/projects/docbook/files/epub3/
However, note that eInk readers are, in my experience, quite inferior for technical reading. Anything that involves tables and color images is likely to make your head hurt :) OTOH, EPU is more than just for eInk readers. Tablets are OK :)
Alexandre Prokoudine http://libregraphicsworld.org
Help building help.
On Wed, Jun 26, 2013 at 05:04:10PM +0400, Alexandre Prokoudine wrote:
On Wed, Jun 26, 2013 at 10:14 AM, Roman Joost wrote:
On Thu, Jun 13, 2013 at 10:00:12AM +0200, Marco Ciampa wrote:
Anyhow, perhaps it makes more sense to move to a epub/Kindle solution. I can relate to Marco here, since I'm also using my Kindle to read most of my books now. The Kindle format is even simiar to HTML. Not sure if there are already packages out there who go from DocBook to Kindle/epub.
http://sourceforge.net/projects/docbook/files/epub3/
However, note that eInk readers are, in my experience, quite inferior for technical reading. Anything that involves tables and color images is likely to make your head hurt :) OTOH, EPU is more than just for eInk readers. Tablets are OK :)
Hm... sounds like we need a plan. Perhaps I'll create a bug in Bugzilla and we move the discussion there ...
Kind Regards,
Roman Joost www: http://www.romanofski.de email: romanofski@gimp.org
Help building help.
On Mon, Jul 01, 2013 at 05:36:50PM +1000, Roman Joost wrote:
On Wed, Jun 26, 2013 at 05:04:10PM +0400, Alexandre Prokoudine wrote:
On Wed, Jun 26, 2013 at 10:14 AM, Roman Joost wrote:
On Thu, Jun 13, 2013 at 10:00:12AM +0200, Marco Ciampa wrote:
Anyhow, perhaps it makes more sense to move to a epub/Kindle solution. I can relate to Marco here, since I'm also using my Kindle to read most of my books now. The Kindle format is even simiar to HTML. Not sure if there are already packages out there who go from DocBook to Kindle/epub.
http://sourceforge.net/projects/docbook/files/epub3/
However, note that eInk readers are, in my experience, quite inferior for technical reading. Anything that involves tables and color images is likely to make your head hurt :) OTOH, EPU is more than just for eInk readers. Tablets are OK :)
Hm... sounds like we need a plan. Perhaps I'll create a bug in Bugzilla and we move the discussion there ...
Would you please post here the bug id when you have done?
Thanks!
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
Help building help.
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed. What I got instead was a package with the guts of the manual in xml. I tried autogen, then ./configure, and then make. Consistently I get these error messages:
Making all in quickreference make[1]: Entering directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No rule to make target `svg/gimp-keys-ca.svg', needed by `svg'. Stop. make[1]: Leaving directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make: *** [all-recursive] Error 1Before I start hacking around eliminating references to the quickreference is there a standard solution to my problem?
I don't want to spend days learning about docbook, wonderful though it may be. I have a project under way and I need to look some things in the manual.
Anyone have a copy they are willing to share? Slackware 14 if anyone cares.
I have another error:
$make pdf-it
*** Making PDF (it) ...
Build the book set list...
xsltproc -o /tmp/tmpxAwlqk/doclist.txt --xinclude --xincludestyle doclist.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
Build the listings...
xsltproc -o /tmp/tmpxAwlqk/listings.xml --xinclude --xincludestyle --param current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' /usr/share/dblatex/xsl/common/mklistings.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
xsltproc -o gimp.rtex --xinclude --xincludestyle --param current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' --param listings.xml '/tmp/tmpxAwlqk/listings.xml' /tmp/tmpxAwlqk/custom.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml
XSLT stylesheets DocBook - LaTeX 2e (0.3.4-3)
===================================================
literal: default template used in programlisting or screen
literal: default template used in programlisting or screen
Don't know what gentext to create for xref to: "para" (linkend=text-to-path)
Don't know what gentext to create for xref to: "para" (linkend=text-along-path)
Image 'images/toolbox/paths-transform-1.png' not found
Image 'images/toolbox/paths-transform-2.png' not found
Image '../images/tool-options/stock-gravity-east-24.png' not found
Build gimp.pdf
built-in module xetex registered
no support found for ifthen
no support found for ifxetex
no support found for fontspec
no support found for xltxtra
no support found for fontenc
no support found for ucs
no support found for inputenc
no support found for fancybox
built-in module makeidx registered
no support found for babel
no support found for cmap
no support found for db2latex
built-in module bibtopic registered
building additional files...
checking if compiling is necessary...
the output file doesn't exist
xelatex -interaction=batchmode gimp.tex
A possible reason for transformation failure is invalid DocBook (as reported by xmllint)
Error: [Errno 2] No such file or directory make: *** [pdf/it/gimp.pdf] Errore 1
....
but
log/it-xmllint.log
contains
it: no errors.
Any hint?
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
Help building help.
Hi, Marco.
Is any advance?
Recently I tried to make pdf file, for test, pdf-en.
I met above same errors.
If you have any, please let me know.
P.S Some people-especially old people- prefer hard copies, like a book. For that pdf version is very good solution. Of course pdf is great for e-book reader for tablet or smartphone. Unfortunately we've had lots of problems with CJK languages. Thus I almost give it up but if it's possible to make gimp-help-2 to a pdf file, it would be wonderful.
--
Regards,
Jihui Choi
On Sun, Jul 21, 2013 at 10:13 AM, Marco Ciampa wrote:
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed. What I got instead was a package with the guts of the manual in xml. I tried autogen, then ./configure, and then make. Consistently I get these error messages:
Making all in quickreference make[1]: Entering directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No rule to make target `svg/gimp-keys-ca.svg', needed by `svg'. Stop. make[1]: Leaving directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make: *** [all-recursive] Error 1Before I start hacking around eliminating references to the quickreference is there a standard solution to my problem?
I don't want to spend days learning about docbook, wonderful though it may be. I have a project under way and I need to look some things in the manual.
Anyone have a copy they are willing to share? Slackware 14 if anyone cares.
I have another error:
$make pdf-it *** Making PDF (it) ...
Build the book set list...
xsltproc -o /tmp/tmpxAwlqk/doclist.txt --xinclude --xincludestyle doclist.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml Build the listings...
xsltproc -o /tmp/tmpxAwlqk/listings.xml --xinclude --xincludestyle --param current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' /usr/share/dblatex/xsl/common/mklistings.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml xsltproc -o gimp.rtex --xinclude --xincludestyle --param current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' --param listings.xml '/tmp/tmpxAwlqk/listings.xml' /tmp/tmpxAwlqk/custom.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml XSLT stylesheets DocBook - LaTeX 2e (0.3.4-3) =================================================== literal: default template used in programlisting or screen literal: default template used in programlisting or screen Don't know what gentext to create for xref to: "para" (linkend=text-to-path)
Don't know what gentext to create for xref to: "para" (linkend=text-along-path)
Image 'images/toolbox/paths-transform-1.png' not found Image 'images/toolbox/paths-transform-2.png' not found Image '../images/tool-options/stock-gravity-east-24.png' not found Build gimp.pdf
built-in module xetex registered
no support found for ifthen
no support found for ifxetex
no support found for fontspec
no support found for xltxtra
no support found for fontenc
no support found for ucs
no support found for inputenc
no support found for fancybox
built-in module makeidx registered
no support found for babel
no support found for cmap
no support found for db2latex
built-in module bibtopic registered
building additional files...
checking if compiling is necessary... the output file doesn't exist
xelatex -interaction=batchmode gimp.texA possible reason for transformation failure is invalid DocBook (as reported by xmllint)
Error: [Errno 2] No such file or directory make: *** [pdf/it/gimp.pdf] Errore 1
....
but log/it-xmllint.log
contains
it: no errors.Any hint?
--
Marco Ciampa
+--------------------+ | Linux User #78271 |
| FSFE fellow #364 |
+--------------------+
_______________________________________________ gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list
Help building help.
On Sun, Jul 21, 2013 at 03:13:30AM +0200, Marco Ciampa wrote:
On Tue, Jun 11, 2013 at 02:41:02PM -0400, john Culleton wrote:
Elaborate things break more often then simple things. All I want is a Gimp Manual in pdf form for version 2.8. I can print this out, put it in a ring binder and use it as needed. What I got instead was a package with the guts of the manual in xml. I tried autogen, then ./configure, and then make. Consistently I get these error messages:
Making all in quickreference make[1]: Entering directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make[1]: *** No rule to make target `svg/gimp-keys-ca.svg', needed by `svg'. Stop. make[1]: Leaving directory
`/home/safe/Documents/gimp-help-2.8.0/quickreference' make: *** [all-recursive] Error 1Before I start hacking around eliminating references to the quickreference is there a standard solution to my problem?
I don't want to spend days learning about docbook, wonderful though it may be. I have a project under way and I need to look some things in the manual.
Anyone have a copy they are willing to share? Slackware 14 if anyone cares.
I have another error:
$make pdf-it *** Making PDF (it) ...
Build the book set list...
xsltproc -o /tmp/tmpxAwlqk/doclist.txt --xinclude --xincludestyle doclist.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml Build the listings...
xsltproc -o /tmp/tmpxAwlqk/listings.xml --xinclude --xincludestyle --param current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' /usr/share/dblatex/xsl/common/mklistings.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml xsltproc -o gimp.rtex --xinclude --xincludestyle --param current.dir '/home/marco/git-gnome/gimp-help-2/xml/it' --param listings.xml '/tmp/tmpxAwlqk/listings.xml' /tmp/tmpxAwlqk/custom.xsl /home/marco/git-gnome/gimp-help-2/xml/it/gimp.xml XSLT stylesheets DocBook - LaTeX 2e (0.3.4-3) =================================================== literal: default template used in programlisting or screen literal: default template used in programlisting or screen Don't know what gentext to create for xref to: "para" (linkend=text-to-path) Don't know what gentext to create for xref to: "para" (linkend=text-along-path) Image 'images/toolbox/paths-transform-1.png' not found Image 'images/toolbox/paths-transform-2.png' not found Image '../images/tool-options/stock-gravity-east-24.png' not found Build gimp.pdf
built-in module xetex registered
no support found for ifthen
no support found for ifxetex
no support found for fontspec
no support found for xltxtra
no support found for fontenc
no support found for ucs
no support found for inputenc
no support found for fancybox
built-in module makeidx registered
no support found for babel
no support found for cmap
no support found for db2latex
built-in module bibtopic registered
building additional files...
checking if compiling is necessary... the output file doesn't exist
xelatex -interaction=batchmode gimp.texA possible reason for transformation failure is invalid DocBook (as reported by xmllint)
Error: [Errno 2] No such file or directory make: *** [pdf/it/gimp.pdf] Errore 1
....
but log/it-xmllint.log
contains
it: no errors.Any hint?
xelatex was not installed but autoconf did not signal the problem ... anyway... to me...
make pdf-it
...
no new compilation is needed
running last-compilation scripts...
Character U+E0 (à) not in font 'cmmi10'
Character U+2CB (ˋ) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+2CB (ˋ) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+3B1 (α) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+2245 (≅) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+592A (太) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+5CF6 (島) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+672C (本) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+6768 (杨) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+7EA2 (红) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+826F (良) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+828A (芊) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+8521 (蔡) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+C9C0 (지) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+CD5C (최) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D76C (희) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
'gimp.pdf' successfully built
works ;-)
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
Help building help.
On Sun, Aug 18, 2013 at 04:02:46PM +0200, Marco Ciampa wrote: [...]
xelatex was not installed but autoconf did not signal the problem ... anyway... to me...
make pdf-it
...
no new compilation is needed running last-compilation scripts...
Character U+E0 (à) not in font 'cmmi10' Character U+2CB (ˋ) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;' Character U+2CB (ˋ) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+3B1 (α) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+2245 (≅) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+592A (太) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+5CF6 (島) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+672C (本) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+6768 (杨) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+7EA2 (红) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+826F (良) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+828A (芊) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+8521 (蔡) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+C9C0 (지) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+CD5C (최) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D76C (희) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' 'gimp.pdf' successfully builtworks ;-)
and even ...
make pdf-ko
....
Character U+D6C4 (후) not in font 'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;' Character U+D6C4 (후) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;' Character U+D6C4 (후) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D6CC (훌) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D6E8 (훨) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D718 (휘) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D71C (휜) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D720 (휠) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;' Character U+D720 (휠) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D734 (휴) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;' Character U+D734 (휴) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D749 (흉) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D750 (흐) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;' Character U+D750 (흐) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;' Character U+D750 (흐) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D751 (흑) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D754 (흔) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D761 (흡) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D765 (흥) not in font 'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;' Character U+D765 (흥) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D769 (흩) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;' Character U+D76C (희) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D770 (흰) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;' Character U+D770 (흰) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D788 (히) not in font 'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;' Character U+D788 (히) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;' Character U+D788 (히) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D78C (힌) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;' Character U+D78C (힌) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D790 (힐) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D798 (힘) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' Character U+D799 (힙) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;' 'gimp.pdf' successfully built
... to you works! ;-)
If you like I can send you a copy...
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
Help building help.
wow.. it works! I made a pdf file for korean. it doesn't show any korean
character though.
I reckon that's just a font problem. I read a document about this before.
Thank you, Marco!!
ps. I'm going to Milan in the middle of Sep. if you are in Italy, I want to meet you. :)
--
Regards,
Jihui Choi
On Sun, Aug 18, 2013 at 11:32 PM, Marco Ciampa wrote:
On Sun, Aug 18, 2013 at 04:02:46PM +0200, Marco Ciampa wrote: [...]
xelatex was not installed but autoconf did not signal the problem ...
anyway... to me...
make pdf-it
...
no new compilation is needed running last-compilation scripts...
Character U+E0 (à) not in font 'cmmi10' Character U+2CB (ˋ) not in font 'URW Palladio LBold/ICU:mapping=tex-text;'
Character U+2CB (ˋ) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+3B1 (α) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+2245 (≅) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+592A (太) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+5CF6 (島) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+672C (本) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+6768 (杨) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+7EA2 (红) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+826F (良) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+828A (芊) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+8521 (蔡) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+C9C0 (지) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+CD5C (최) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
Character U+D76C (희) not in font 'URW Palladio L
Roman/ICU:mapping=tex-text;'
'gimp.pdf' successfully built
works ;-)
and even ...
make pdf-ko
....
Character U+D6C4 (후) not in font 'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;' Character U+D6C4 (후) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D6C4 (후) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D6CC (훌) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D6E8 (훨) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D718 (휘) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D71C (휜) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D720 (휠) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+D720 (휠) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D734 (휴) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+D734 (휴) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D749 (흉) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D750 (흐) not in font 'URW Palladio L Bold/ICU:mapping=tex-text;'
Character U+D750 (흐) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D750 (흐) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D751 (흑) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D754 (흔) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D761 (흡) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D765 (흥) not in font
'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;' Character U+D765 (흥) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D769 (흩) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D76C (희) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D770 (흰) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D770 (흰) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D788 (히) not in font
'FreeSans/ICU:script=latn;language=DFLT;mapping=tex-text;' Character U+D788 (히) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D788 (히) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D78C (힌) not in font 'URW Palladio L Italic/ICU:mapping=tex-text;'
Character U+D78C (힌) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D790 (힐) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D798 (힘) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
Character U+D799 (힙) not in font 'URW Palladio L Roman/ICU:mapping=tex-text;'
'gimp.pdf' successfully built... to you works! ;-)
If you like I can send you a copy...
--
Marco Ciampa
+--------------------+ | Linux User #78271 |
| FSFE fellow #364 |
+--------------------+
_______________________________________________ gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list
Help building help.
On Mon, Aug 19, 2013 at 12:43:57AM +0900, Jihui Choi wrote:
wow.. it works! I made a pdf file for korean. it doesn't show any korean character though.
I reckon that's just a font problem. I read a document about this before.
Same problem here.
Only chapter titles in korean chars.
The other text is blank... :-(
I've made a
apt-get install texlive-full
with no visible difference though.
I think that this is a _big_ problem for many reasons:
1) english is more understandable by American and European people than for asiatic people. It is a bit hironic that asiatic people (pdf) translation isn't working...
2) now that we have a constant korean translator voluteer we have to do something to not make him go away... ;-)
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
Help building help.
I did install texlive-full as well on ubuntu 12.04 Though there are still problems, I'm happy with it. At least I can make a pdf for korean and that means I can move to next step.
And when I started this work, I said I wanted to do this for many years
like 10-20 years.
I stopped it for a while because of my long trip for almost 3 years and
others.. But now I'm back and I believe someone will show up to work with
me soon. :)
--
Regards,
Jihui Choi
On Mon, Aug 19, 2013 at 6:04 PM, Marco Ciampa wrote:
On Mon, Aug 19, 2013 at 12:43:57AM +0900, Jihui Choi wrote:
wow.. it works! I made a pdf file for korean. it doesn't show any korean character though.
I reckon that's just a font problem. I read a document about this before.Same problem here.
Only chapter titles in korean chars. The other text is blank... :-(I've made a
apt-get install texlive-full
with no visible difference though.
I think that this is a _big_ problem for many reasons:
1) english is more understandable by American and European people than for asiatic people. It is a bit hironic that asiatic people (pdf) translation isn't working...
2) now that we have a constant korean translator voluteer we have to do something to not make him go away... ;-)
--
Marco Ciampa
+--------------------+ | Linux User #78271 |
| FSFE fellow #364 |
+--------------------+
_______________________________________________ gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list
GIMP doc on Cygwin
The version of Cygwin which I have used for years refused a month or so ago to work with the programs used for translating GIMP documents. Perhaps because I switched to a 64 bits computer. I therefore had to install 64 bits Cygwin, but alas I have forgotten which packages needed.
I remember there was some problems but not the solutions and neither where to find the threads where the installation(s) was discussed. Julien, are your "cookbook" (Using Cygwin for GIMP translations) still available somewhere?
Someone who remembers and are willing to help me?
Kolbjoern Stuestoel
GIMP doc on Cygwin
On Sat, Sep 07, 2013 at 02:15:07PM +0200, Kolbjrn Stuestl wrote:
The version of Cygwin which I have used for years refused a month or so ago to work with the programs used for translating GIMP documents. Perhaps because I switched to a 64 bits computer. I therefore had to install 64 bits Cygwin, but alas I have forgotten which packages needed.
I remember there was some problems but not the solutions and neither where to find the threads where the installation(s) was discussed. Julien, are your "cookbook" (Using Cygwin for GIMP translations) still available somewhere?
Someone who remembers and are willing to help me?
Kolbjoern Stuestoel
Why not install Virtualbox and inside it a Linux (Ubuntu) machine? In that case I can help ...
Marco Ciampa +--------------------+ | Linux User #78271 | | FSFE fellow #364 | +--------------------+
GIMP doc on Cygwin
Den 07.09.2013 19:04, skreiv Marco Ciampa:
On Sat, Sep 07, 2013 at 02:15:07PM +0200, Kolbjrn Stuestl wrote:
The version of Cygwin which I have used for years refused a month or so ago to work with the programs used for translating GIMP documents. Perhaps because I switched to a 64 bits computer. I therefore had to install 64 bits Cygwin, but alas I have forgotten which packages needed.
I remember there was some problems but not the solutions and neither where to find the threads where the installation(s) was discussed. Julien, are your "cookbook" (Using Cygwin for GIMP translations) still available somewhere?
Someone who remembers and are willing to help me?
Kolbjoern Stuestoel
Why not install Virtualbox and inside it a Linux (Ubuntu) machine? In that case I can help ...
I am a bit lazy, Marco, and as I have used Cygwin for several years I hold on it. But perhaps Virtualbox is worth a try. I'l give it a look.
(At the moment I have to use my ten years old Windows XP computer for this work, but would like to update on a newer computer). Kolbjoern
GIMP doc on Cygwin
I remember there was some problems but not the solutions and neither where to find the threads where the installation(s) was discussed. Julien, are your "cookbook" (Using Cygwin for GIMP translations) still available somewhere?
Unfortunately no.
But did you try cygwin + git on Google ?
Julien
GIMP doc on Cygwin
Den 10.09.2013 21:30, skreiv Julien Hardelin:
I remember there was some problems but not the solutions and neither where to find the threads where the installation(s) was discussed. Julien, are your "cookbook" (Using Cygwin for GIMP translations) still available somewhere?
Unfortunately no.
But did you try cygwin + git on Google ?
Nice to hear from you.
Yes, I have searched several times and have found some old threads, so
perhaps I will manage it some rainy day. It is not very important as I
still am able to use an old computer. In fact the one you and some
others helped me to set up many years ago. :-)
The main reason for changing to 64 bits is the speed and of course the safety in having Cygwin/git etc. running on two or more computers.
The reason for the trouble is that Cygwin refuses to update my 32 bits version running on a 64 bits computer. I have to install the 64 bits version.
Kolbjoern
Julien
Updating quickreference
It looks like I have forgotten something, so: How do I update the
quickreference/po/nn.po file?
I tried to add it the same way as the others po files, i.e.
git add -> git commit -> git push, but failed.
BTW: The Norwegian file in Keys and Mouse Quickreference (PDF) on the docs.gimp.org site is missing.
Kolbjoern
Updating quickreference
On Wed, Sep 11, 2013 at 2:13 AM, Kolbjrn Stuestl wrote:
It looks like I have forgotten something, so: How do I update the quickreference/po/nn.po file?
I tried to add it the same way as the others po files, i.e. git add -> git commit -> git push, but failed.
Failed how? :)
Alexandre
Updating quickreference
Den 11.09.2013 06:11, skreiv Alexandre Prokoudine:
On Wed, Sep 11, 2013 at 2:13 AM, Kolbjrn Stuestl wrote:
It looks like I have forgotten something, so: How do I update the quickreference/po/nn.po file?
I tried to add it the same way as the others po files, i.e. git add -> git commit -> git push, but failed.Failed how? :)
Sorry. I deleted all messages and do not remember them. Do your question means that i could use add -> commit -> push the normal way? I'll give it a new try during this night. Kolbjoern
Alexandre
