Hi,
It is a question about fedora-docs. Almost all the file names of fedora-docs do not correspond to multilingual.
ex) documentation-guide/documentation-guide.xml developer-guide/developers-guide.xml
Originally you should be as follows.
ex) documentation-guide/documentation-guide-en.xml developer-guide/developers-guide-en.xml
Is such correction made?
----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf@elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/
Good point. I will make such corrections in CVS.
Cheers, Tammy
On Fri, Nov 21, 2003 at 04:31:06PM +0900, Tadashi Jokagi wrote:
Hi,
It is a question about fedora-docs. Almost all the file names of fedora-docs do not correspond to multilingual.
ex) documentation-guide/documentation-guide.xml developer-guide/developers-guide.xml
Originally you should be as follows.
ex) documentation-guide/documentation-guide-en.xml developer-guide/developers-guide-en.xml
Is such correction made?
----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf@elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/
Done. I tested the guides, and they still build. Let me know if you see any problems.
Tam
On Fri, Nov 21, 2003 at 08:48:22AM -0500, Tammy Fox wrote:
Good point. I will make such corrections in CVS.
Cheers, Tammy
On Fri, Nov 21, 2003 at 04:31:06PM +0900, Tadashi Jokagi wrote:
Hi,
It is a question about fedora-docs. Almost all the file names of fedora-docs do not correspond to multilingual.
ex) documentation-guide/documentation-guide.xml developer-guide/developers-guide.xml
Originally you should be as follows.
ex) documentation-guide/documentation-guide-en.xml developer-guide/developers-guide-en.xml
Is such correction made?
----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf@elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/
-- fedora-docs-list mailing list fedora-docs-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list
Hi, Thanks your works. Regard.
Tammy Fox's20031121224542.GE12282@redhat.com wrote:
Done. I tested the guides, and they still build. Let me know if you see any problems.
Tam
On Fri, Nov 21, 2003 at 08:48:22AM -0500, Tammy Fox wrote:
Good point. I will make such corrections in CVS.
Cheers, Tammy
On Fri, Nov 21, 2003 at 04:31:06PM +0900, Tadashi Jokagi wrote:
Hi,
It is a question about fedora-docs. Almost all the file names of fedora-docs do not correspond to
multilingual.
ex) documentation-guide/documentation-guide.xml developer-guide/developers-guide.xml
Originally you should be as follows.
ex) documentation-guide/documentation-guide-en.xml developer-guide/developers-guide-en.xml
Is such correction made?
----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf@elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitana with PukiWiki http://elf.no-ip.org/wiki/
-- fedora-docs-list mailing list fedora-docs-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list
--
-- fedora-docs-list mailing list fedora-docs-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list
Hi,
I thought that it would contribute to bugzilla. However, since a category was not found, it gave up;-) ENTITY has a mistake.
RCS file: /usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v retrieving revision 1.1 diff -r1.1 fedora-install-guide-en.xml 12c12 < <!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice.xml"> ---
<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
At 09:35 28/11/2003, you wrote:
Hi,
I thought that it would contribute to bugzilla. However, since a category was not found, it gave up;-) ENTITY has a mistake.
RCS file: /usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v retrieving revision 1.1 diff -r1.1 fedora-install-guide-en.xml 12c12 < <!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice.xml">
Would a net address be easier, then we could map it to a local file via a catalog? Tammy?
regards DaveP
Hi,
RCS file: /usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v retrieving revision 1.1 diff -r1.1 fedora-install-guide-en.xml 12c12 < <!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice.xml">
Would a net address be easier,
Sure -- It seems to be better to use Content Negotiation. Example: index.html.en index.html.ja index.html.de
Although it is not a not good way,
It is realizable if a docbook html template is changed. It is necessary to also change fedora-docs/*/Makefile.
It is as follows if it does by this method.
developers-guide/*.html.en *.html.ja *.html.de
Other ideas?
[/usr/share/xmlto/format/docbook/html] == --- html.default 2003-12-01 03:05:46.000000000 +0900 +++ html 2003-12-01 04:47:33.000000000 +0900 @@ -7,6 +7,11 @@ echo "http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl" ;; post-process) - cp -- * "$OUTPUT_DIR" + if [ ! -z "$LANG" ] + then + for i in *; do + cp -- $i "$OUTPUT_DIR"/$i.$LANG + done + fi ;; esac
[$FEDORA-DOCS/*/Makefile] == --- Makefile.default 2003-11-22 07:39:22.000000000 +0900 +++ Makefile 2003-12-01 04:03:34.000000000 +0900 @@ -10,8 +10,9 @@ XSLPDF = ../xsl/main-pdf.xsl XSLHTML = ../xsl/main-html.xsl LANG = en -DOCNAME = developers-guide-$(LANG) -XMLFILE = $(DOCNAME).xml +#DOCNAME = developers-guide-$(LANG) +DOCNAME = developers-guide +XMLFILE = $(DOCNAME)-$(LANG).xml
###################################################### html:
-- Naoki Shigematsu
Hi,
I propose creating the directory of a language name.
ex) - /de/developers-guide/index.html - /en/developers-guide/index.html - /ja/developers-guide/index.html
Reason
- There is no reason in being intermingled by many languages. -- However, there may be a merit about a web page. - It is hard to treat with a local file system. - Finally, the number of files becomes huge.
As far as I know, as for a many languages manual, PHP's is consulted very much. If there is time, please make it reference.
http://pear.php.net/manual/ http://cvs.php.net/cvs.php/peardoc
Are you proposing this for the website or CVS?
On Mon, Dec 01, 2003 at 08:09:47AM +0900, Tadashi Jokagi wrote:
Hi,
I propose creating the directory of a language name.
ex)
- /de/developers-guide/index.html
- /en/developers-guide/index.html
- /ja/developers-guide/index.html
Reason
- There is no reason in being intermingled by many languages.
-- However, there may be a merit about a web page.
- It is hard to treat with a local file system.
- Finally, the number of files becomes huge.
As far as I know, as for a many languages manual, PHP's is consulted very much. If there is time, please make it reference.
http://pear.php.net/manual/ http://cvs.php.net/cvs.php/peardoc
-- ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf@elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitawiki http://elf.no-ip.org/wiki/ Yokukitablog http://elf.no-ip.org/blog/
-- fedora-docs-list mailing list fedora-docs-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list
Hi,
Tammy Fox's "Re: mistake entity (was: filename)" wrote:
Are you proposing this for the website or CVS?
It is website. As for PHP, CVS is also the same. However, if the optimal, I think that now is still sufficient as CVS.
On Tue, Dec 02, 2003 at 02:22:16PM +0900, Tadashi Jokagi wrote:
Hi,
Tammy Fox's "Re: mistake entity (was: filename)" wrote:
Are you proposing this for the website or CVS?
It is website. As for PHP, CVS is also the same. However, if the optimal, I think that now is still sufficient as CVS.
For the website, we will probably go with a fedora.redhat.com/<lang>/ or <lang>.fedora.redhat.com so the translated versions can be divided into separate virtual servers.
For CVS, the translation team has already started to create the structure using a po/ subdirectory in each directory that contains a document. The Makefile will allow you to generate translatable po files from the source DocBook XML files, translate the translated po files back into translated DocBook XML files, and generate HTML output. They are also writing a document about the process.
Regards, Tammy
Hi,
For the website, we will probably go with a fedora.redhat.com/<lang>/ or <lang>.fedora.redhat.com so the translated versions can be divided into separate virtual servers.
Nice! About what time can this be used?
Thanks.
上鍵です.こんにちわ.
tfox@redhat.comさんの20031203160035.GE4099@redhat.comから
For the website, we will probably go with a fedora.redhat.com/<lang>/ or <lang>.fedora.redhat.com so the translated versions can be divided into separate virtual servers.
Nice!!
For CVS, the translation team has already started to create the structure using a po/ subdirectory in each directory that contains a document. The Makefile will allow you to generate translatable po files from the source DocBook XML files, translate the translated po files back into translated DocBook XML files, and generate HTML output. They are also writing a document about the process.
I have seldom understood. I will check what was completed.
Hi,
tfox@redhat.com's "Re: mistake entity (was: filename)" wrote:
For CVS, the translation team has already started to create the structure using a po/ subdirectory in each directory that contains a
(snip)
Is this portion mail subject of "Software translation steps"? I do not understand the meaning which uses po for translation of a docbook document. What do I misunderstand?
Hi,
On Fri, 05 Dec 2003 10:50:09 +0900 Tadashi Jokagi ml@elf.no-ip.org wrote:
Is this portion mail subject of "Software translation steps"? I do not understand the meaning which uses po for translation of a docbook document. What do I misunderstand?
This mail is described about _Software_ translation, not a docbook document.
-- Naoki Shigematsu sigematu@impress.co.jp Impress Corporation 20 Sanbancho, Chiyoda-ku, Tokyo 102-0075, Japan Tel: +81-3-5275-9017 Fax: +81-3-5275-9047 Uri: http://www.impress.co.jp/
Hi, Naoki Shigematsuさんの「Re: mistake entity (was: filename)」から
This mail is described about _Software_ translation, not a docbook document.
I understood. It was the talk of docbook from the first. Since po had come there, it got confused. My understanding was right if it was the talk of software.
Hi,
I also proposed in the past.
Date: Mon, 01 Dec 2003 08:09:47 +0900 Message-ID: 3fca78bb.2183%ml@elf.no-ip.org
+1 vote.
There is also another problem in addition to file composition now. It is using xmlto. That is because xmlto probably does not correspond to many languages. The character code of docbook is UTF-8. On the level, it is multilingual correspondence. However, HTML outputted is ASCII and a HTML entity. For example, now, it is difficult to create text browsing environment. Moreover, combined use of each text filter or a format conversion program is difficult.
It seems that this problem can be avoided if openjapde is used. HTML created by PHP can do a full-text search. #The site of PHP is an English full-text search. ;-(
Is there any evasion method of this problem by xmlto?
Regards,
On Thu, Jan 08, 2004 at 06:34:59PM +0900, Tadashi Jokagi wrote:
[the fact that non-ASCII characters come out as HTML entities even with UTF-8 output]
Is there any evasion method of this problem by xmlto?
We saw this with anaconda too, but I think Matt Wilson just added support in anaconda for reading the entities.
It would be a good idea to create a tiny example document that shows the behaviour, and file it in bugzilla -- against xmlto if you like, although I think it is probably either xsltproc or the DocBook stylesheets that cause it.
Tim. */
On Fri, Nov 28, 2003 at 06:05:43PM +0000, Dave Pawson wrote:
At 09:35 28/11/2003, you wrote:
Hi,
I thought that it would contribute to bugzilla. However, since a category was not found, it gave up;-) ENTITY has a mistake.
RCS file: /usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v retrieving revision 1.1 diff -r1.1 fedora-install-guide-en.xml 12c12 < <!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice.xml">
Would a net address be easier, then we could map it to a local file via a catalog? Tammy?
I would rather keep it all in CVS. Everyone has to checkout the module anyway. Being able to compile without an Internet is nice if you need to work on the road or elsewhere
Tammy
regards DaveP
-- fedora-docs-list mailing list fedora-docs-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list
At 02:12 02/12/2003, you wrote:
Would a net address be easier, then we could map it to a local file via a catalog? Tammy?
I would rather keep it all in CVS. Everyone has to checkout the module anyway. Being able to compile without an Internet is nice if you need to work on the road or elsewhere
Which is where the catalog proves its worth. http://www.sagehill.net/docbookxsl/Catalogs.html and http://www.oasis-open.org/committees/entity/background/9401.html Norm explains it well at http://wwws.sun.com/software/xml/developers/resolver/article/
regards DaveP
Sorry about that. I fixed it in CVS.
Tammy
On Fri, Nov 28, 2003 at 06:35:45PM +0900, Tadashi Jokagi wrote:
Hi,
I thought that it would contribute to bugzilla. However, since a category was not found, it gave up;-) ENTITY has a mistake.
RCS file: /usr/local/CVS/fedora-docs/install-guide/fedora-install-guide-en.xml,v retrieving revision 1.1 diff -r1.1 fedora-install-guide-en.xml 12c12
< <!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice.xml">
<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
-- ----.----1----.----2----.----3----.----4----.----5----.----6----.----7 Tadashi Jokagi/Shibuya city mailto:elf@elf.no-ip.org Yokukitana http://elf.no-ip.org/ Yokukitawiki http://elf.no-ip.org/wiki/ Yokukitablog http://elf.no-ip.org/blog/
-- fedora-docs-list mailing list fedora-docs-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-docs-list