Bug 56456
| Summary: | Initial import of the ro_RO.ISO889-2 doc/handbook tree | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Documentation | Reporter: | Adrian Penisoara <ady> | ||||
| Component: | Books & Articles | Assignee: | Marc Fonvieille <blackend> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Responsible Changed From-To: freebsd-doc->blackend I will work on this one. Hi, I just looked at your files, quite nothing is translated (only the 1st page, the colophon and the parts forewords), maybe we can wait for a chapter before committing. For the moment, it is not really useful for the romanian reader. Another thing, you should use SGML codes for ã,î etc. Marc Hi, On Fri, 5 Sep 2003, Marc Fonvieille wrote: > Hi, > > I just looked at your files, quite nothing is translated (only the 1st > page, the colophon and the parts forewords), maybe we can wait for a That's what it I supposed it was needed for the initial commit: the Makefile and directory hierarchy plus placeholders for the chapters content. > chapter before committing. For the moment, it is not really useful for The Preface should be ready in a few hours. Then, the next few days, I will import the chapters translated by some of my students, with minor adapations. They covered about 30% of the chapters until now. > the romanian reader. > Another thing, you should use SGML codes for ã,î etc. Well, I have been thinking about this. I know it's recommended to use SGML entities, but I miss a few of them: s with a comma below and t with a comma below. I haven't found corresponding entitied in the DSSL catalogs. And, besides, the ISO8859-16 charset, a very new encoding specific for the Romanian language, which, besides the introduction of the euro symbol, uses true commas under those letters, and not cedills like in Turkish that we observe in the ISO8859-2 charset, has the very same positions for the romanian-specific accents. Later it will be easy to migrate this documentation from ISO8859-2 to ISO8859-16. Officialy there is not so much support for ISO8859-16 right now. That's why I decided to use verbatim characters over the SGML entities. Not to mention the ease of reading and writing this way. :) I would like to know what is needed to complete the first commit to the FreeBSD CVS tree. Thank you, Adrian Penisoara Ady (@rofug.ro, @nscl.eed.usv.ro) ROFUG USV, EED, NSCL On Fri, Sep 05, 2003 at 08:05:27PM +0300, Adrian Penisoara wrote: > Hi, > > On Fri, 5 Sep 2003, Marc Fonvieille wrote: > > > Hi, > > > > I just looked at your files, quite nothing is translated (only the 1st > > page, the colophon and the parts forewords), maybe we can wait for a > > That's what it I supposed it was needed for the initial commit: the > Makefile and directory hierarchy plus placeholders for the chapters > content. > > > chapter before committing. For the moment, it is not really useful for > > The Preface should be ready in a few hours. Then, the next few days, > I will import the chapters translated by some of my students, > with minor adapations. They covered about 30% of the chapters until now. > We really need at least a translated chapter/article, for the moment there is no "real content". > > the romanian reader. > > Another thing, you should use SGML codes for ã,î etc. > > Well, I have been thinking about this. I know it's recommended to use > SGML entities, but I miss a few of them: s with a comma below and t with > a comma below. I haven't found corresponding entitied in the DSSL > catalogs. > They are the same used for HTML. > And, besides, the ISO8859-16 charset, a very new encoding specific for > the Romanian language, which, besides the introduction of the euro > symbol, uses true commas under those letters, and not cedills like in > Turkish that we observe in the ISO8859-2 charset, has the very same > positions for the romanian-specific accents. Later it will be easy to > migrate this documentation from ISO8859-2 to ISO8859-16. Officialy there > is not so much support for ISO8859-16 right now. > > That's why I decided to use verbatim characters over the SGML entities. > Not to mention the ease of reading and writing this way. :) > This can be done, once the content is translated, please use the entities. > I would like to know what is needed to complete the first commit to the > FreeBSD CVS tree. > As I said, I need at least an article or a small chapter :) It's what did every translation team. Marc State Changed From-To: open->feedback Anything New? I think this PR should be suspended for now, since more that a year has passed since the date of the PR and many things have changed in the doc (share) infrastructure; I will be reviewing the changes in the next week and I hope to come out with the appropriate patches. I think we should continue our work on rofug cvs server and come back here when we really have something to add. ( But of course members of FRTP Team @ rofug.ro could think otherwise, hence the list is cc'ed ). I think we've agreed to go on ISO8859-2 for now, because the support for -16 in apps is not as wide as we would like; sometime in the future we would like to switch from ISO8859-2 ls -16 or UTF8 because the characters from -2 aren't really appropriate for Romanian (they are Turkish), but that shouldn't pose many problems once we have the translation done. I believe we would be ready with a quality translation of the handbook and some articles by the end of the year. The team is bigger now and its members are all experienced FreeBSD users thus I'm confident this won't be a false start as it was the last year. -- IOnut Unregistered ;) FreeBSD "user" State Changed From-To: feedback->suspended One of the members of the Romanian translation team stated that this PR should be 'suspended' awaiting further content revisions. State Changed From-To: suspended->closed Close this PR since Romanian (translation) team activity is currently concentrated on other areas (ports and such). |
Initial import of the doc/ro_RO.ISO8859-2 tree. The tree is also kept under a CVS tree at NSCL; the RCS id string is $Id$. Most of the directories and all of the files are new to the FreeBSD CVS tree. Fix: Attached below is an uuencoded tar.gz archive which contains the ro_RO.ISO8859-2 tree. Please review and import into the official FreeBSD CVS tree. The handbook tree has been tested to compile and install. The file is also available here: ftp://ftp.rofug.ro/pub/ro-l10n/doc/ro-handbook-initial.tar.gz ftp://ftp.nscl.eed.usv.ro/pub/FreeBSD/ro-l10n/ro-handbook-initial.tar.gz