Re: release notes: Mandrakesoft/Mandriva
quote who=Vincent Untz Le lundi 05 septembre 2005 à 02:35 +0200, Reinout van Schouwen a écrit : Hi, Just wanted to point out that a string in the release notes mentions Mandrakesoft. The company has been renamed to Mandriva. Please adjust the text. :) Also: GNOME 2.12 is the third 'time-based' GNOME release. 2.4 was time-based too, IIRC. So, we have 2.4, 2.6, 2.8, 2.10 and now 2.12. It should probable be fifth instead of third, shouldn't it? I gues we've been saying that for a while now. I'd like to fix both these things, but gnome-i18n must approve it, because it breaks the translations. It might not be worth it. CCed. Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Press Release VI
On 05/09/2005, at 5:22 PM, Murray Cumming wrote: Added. Please try to send these to gnome-i18n, or a gnome-i18n coordinator, though it would be best to check them in directly. I can't guarantee that I will respond quickly enough personally. Sorry, Murray, these are my first efforts at documentation translation. Where do I check them in? For example, the press-release on the docs status page has this link: http://cvs.gnome.org/viewcvs/gnomeweb-wml/www.gnome.org/start/2.12/ press_release/docbook?only_with_tag=HEAD Would I check my vi.po into: start/2.12/press_release/ ? or is there a .po directory? Copying this to gnome-i18n since it's a general documentation- translation question. Hope that's OK. Assuming so since you wanted similar qs about the release notes asked there. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gtkhtml has been branched
Today at 9:59, Kaushal Kumar wrote: The gnome-2-12 branch of gtkhtml has been created. This would be the stable branch for GtkHTML 3.8.0. The development branch is CVS HEAD. Thanks for the notice. Translation status pages should show the new branch when they next update. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: release notes: Mandrakesoft/Mandriva
Today at 9:45, Murray Cumming wrote: That sounds ideal. Please mention it in the wiki if you do this. Many thanks. Did it. So guys, please fix all typos using en.po translation, and generally, follow the guidelines from: http://live.gnome.org/ReleaseNotes_2fTranslating (Typos section). For changed meaning, also add a comment in XML file so translators get to know about it as well. Unfortunately, I only now noticed that rnwhy.xml is not included at all in the release notes—and that's where the MandrakeSoft/Mandriva and third/sixth (right? 2.2, 2.4, 2.6, 2.8, 2.10, 2.12 is sixth) problems are. Do we want to include it somewhere, or completely drop it (translators have already been translating it, so it's not a problem for them either way)? http://www.gnome.org/start/2.4/notes/rnwhy.html are the last notes that included this section as second time-based release. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Press Release VI
On 05/09/2005, at 5:22 PM, Murray Cumming wrote: Added. Please try to send these to gnome-i18n, or a gnome-i18n coordinator, though it would be best to check them in directly. I can't guarantee that I will respond quickly enough personally. Sorry, Murray, these are my first efforts at documentation translation. Where do I check them in? For example, the press-release on the docs status page has this link: http://cvs.gnome.org/viewcvs/gnomeweb-wml/www.gnome.org/start/2.12/ press_release/docbook?only_with_tag=HEAD Yes, and there (under docbook/) you should see directories for other locales, such as de. And now you even see a directory for your vi locale, because I added the .po file that you sent. I did. $ mkdir vi $ cvs add vi $ cp /home/murrayc/your_vi.po vi/vi.po $ cd vi $ cvs add vi.po Then I edited the ChangeLog (in start/2.12), and did a $ cvs commit -m copy of my changelog entry. Would I check my vi.po into: start/2.12/press_release/ ? or is there a .po directory? Copying this to gnome-i18n since it's a general documentation- translation question. Hope that's OK. Of course. Assuming so since you wanted similar qs about the release notes asked there. Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: release notes: Mandrakesoft/Mandriva
Today at 9:45, Murray Cumming wrote: That sounds ideal. Please mention it in the wiki if you do this. Many thanks. Did it. So guys, please fix all typos using en.po translation, and generally, follow the guidelines from: http://live.gnome.org/ReleaseNotes_2fTranslating (Typos section). For changed meaning, also add a comment in XML file so translators get to know about it as well. Unfortunately, I only now noticed that rnwhy.xml is not included at all in the release notesâand that's where the MandrakeSoft/Mandriva and third/sixth (right? 2.2, 2.4, 2.6, 2.8, 2.10, 2.12 is sixth) problems are. Do we want to include it somewhere, or completely drop it (translators have already been translating it, so it's not a problem for them either way)? Best to drop it. http://www.gnome.org/start/2.4/notes/rnwhy.html are the last notes that included this section as second time-based release. Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze break in gedit
Today at 9:39, Paolo Maggi wrote: On Sun, 2005-09-04 at 02:57 +0200, Francisco Javier F. Serrador wrote: I have noticed there has been an unanounced string freeze breakage in gedit. Is that correct? AFAIK, it is not correct. What strings are you referring to? Paolo, Paolo and Paolo ;-), no need to worry about it, we believe it was due to usage of incompatible intltool version (one between 0.28 and 0.30). It's not a string freeze break. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: release notes: Mandrakesoft/Mandriva
Today at 11:47, Murray Cumming wrote: Unfortunately, I only now noticed that rnwhy.xml is not included at Best to drop it. Ok, dropped from DOC_INCLUDES at least. If you wish, you may cvs rm it as well. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: From every continent (release notes)
On 05/09/2005, at 12:20 AM, Francisco Javier F. Serrador wrote: According to this http://www.gnome.org/~jdub/random/GnomeWorldWideHuge.jpg nat and miguel Fantastic!! It doesn't seem that long ago that communicating with someone down on an Antarctic station meant very occasional code telegrams. :) Thankyou, Francisco. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing to branches :(
On 05/09/2005, at 12:47 AM, Арангел Ангов wrote: I've tried this too. Tried even deleting the whole gnome-volume- manager directory and the did the checkout with -r gnome-2-12, commited the translation again but no luck. Clytie, if you did resolve this, how did you do it? Арангел , I'm relieved to hear I'm not the only person having trouble with gnome-volume-manager. The update process worked for every branch file I had, _except_ g-v-m. Yet, it's CVS dir. has a Tag file with contents: Tgnome-2-12 I don't know why it's not working. :( from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze break in gedit
On 05/09/2005, at 3:42 AM, Francisco Javier F. Serrador wrote: msgid Symbol msgstr #: ../plugins/taglist/Latex.tags.xml.in.h:51 msgid Symbol = msgstr #: ../plugins/taglist/Latex.tags.xml.in.h:52 msgid Symbol = msgstr #: ../plugins/taglist/Latex.tags.xml.in.h:53 msgid Symbol msgstr While this is being discussed, I understand the ASCII shorthand for ≤ and ≥, but what do and mean? Thankyou to anyone who can enlighten me. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
docs qs (was: Re: Release notes translated to VI
Please try to email gnome-i18n instead of me directly. They will be more responsive and informed. OK, but they've probably seen enough of my questions recently. Whenever I start something different, it's difficult for me, so I have to ask a lot of questions. The .po is in the gnomeweb-wml module, as described here: http://live.gnome.org/ReleaseNotes/Translating I have read the document, but I've only just started with CVS/SVN. I can commit my application .po files, but unless I have a very definite committal address which I can relate to my working copy, I don't know exactly what to do with anything else. Just saying: Commit it to gnomeweb-wml/www.gnome.org/start/2.12/notes/docbook/ LANG/LANG.po where LANG is your language code isn't enough information for me. How does that relate to my working copy? Where do I put this document, so it's in the right place? I don't have a directory called www.gnome.org. Once I know where to create directories in my working copy, do I simply cd to the ../docbook/vi dir. and commit from there? Do I edit a changelog? I don't think we can assume that everyone is experienced in CVS. 3. I don't know how to add my language to gnomeweb-wml/www.gnome.org/ start/2.12/notes/docbook/Makefile_shared.am_fragment (DOC_LINGUAS variable). What do I do? Edit the file and add your locale name to the list. Where do I find the file? What do you mean by your locale name? Sure. Try to make sure that the screenshots are similar to the originals. If you can't translate all the screenshots, then it's not the end of the world. He's gone to a lot of trouble to send me quite a few shots, so I think we'll have a good representation. However, I'll need exact instructions on how to commit them, too. I can update the translation, but I don't know how to track build errors. http://live.gnome.org/ReleaseNotes/Translating has a link to the build log. I know. However, I can't track build errors, since I don't know what they are. What am I supposed to look for? When I find it, what am I supposed to do? (I feel awfully stupid, asking all these basic questions, but I don't know the answers, and I need to know.) Do talk to gnome-i18n and the docs mailing list. _Another_ mailing list? Where do I find it, please? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Release notes, Greek bug (Docbook XML related)
2005/9/4, Danilo Šegan [EMAIL PROTECTED]: Hi Simos, Today at 21:02, Simos Xenitellis wrote: ... though it may take a bit to appear in distributions. Do you really want to know what distribution is being used on window.gnome.org (server where everything is generated)? I don't think you do, but anyway, it's RHEL 3 (released in September 2003[1])! [1]http://www.redhat.com/software/rhel/3features/ It may take a bit more than a bit to appear in that distribution, y'a know :) FWIW, Serbian translations show the English Figure 1. title. can we use the same for Greek release notes if changes in server cant be made in time? Anyway, we definitely want to port the stylesheets to use Shaun's excellent l10n xsl stylesheets (as used in Yelp), but that's only 2.14 material. Maybe you can see with web, marketing or sysadmin teams about fixing this short-term for you, but I really think we should go with everything Shaun is doing inside gnome-doc-utils in the future. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing press release (was: Re: Press Release VI
Thankyou for your prompt and helpful reply, Murray. :) On 05/09/2005, at 7:16 PM, Murray Cumming wrote: Yes, and there (under docbook/) you should see directories for other locales, such as de. And now you even see a directory for your vi locale, because I added the .po file that you sent. I did. I see it. :) Thankyou. $ mkdir vi $ cvs add vi $ cp /home/murrayc/your_vi.po vi/vi.po $ cd vi $ cvs add vi.po Then I edited the ChangeLog (in start/2.12), and did a $ cvs commit -m copy of my changelog entry. I can do all this if I know where to do it. I currently have the press release and release notes in separate directories at the top of my Gnome working copy. Where should they be? Or doesn't it matter? They are both under gnomeweb-wml/www.gnome.org/start/2.12/ For example, I have separate second-level (under gnome) directories for gnome-2-10, gnome-2-12 and HEAD. I just can't work out where the docs directories fit in with this. I would still use a branch with both these docs, because they're gnome-2-12? No, the gnomeweb-wml module does not have branches like the software source code. Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze break in gedit
Am Montag, den 05.09.2005, 21:35 +0930 schrieb Clytie Siddall: While this is being discussed, I understand the ASCII shorthand for ≤ and ≥, but what do and mean? Thankyou to anyone who can enlighten me. :) These are Latex symbols \gg and \ll or naturally written much greater and much less. Image to see how they look like: http://www.math.tau.ac.il/~elip/latex_symbols3.gif Unicode would be: ≪ U+226A MUCH LESS-THAN ≫ U+226B MUCH GREATER-THAN Regards, Frank ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GnomeMeeting 1.2.2
On 9/5/05, Damien Sandras [EMAIL PROTECTED] wrote: Hello to all, GnomeMeeting 1.2.2 has been uploaded to the GNOME FTP server for release with GNOME 2.12. It is a very minor bugfixes release. It contains several translations updates. I have created a gnome-2-12 branch. Development will continue in the opal branch which should be merged to HEAD soon when we judge that SIP support is good enough for public consommation! In line with my other requests for information, care to share a bit more about your goals for the 'opal' branch? I'm hoping you think it'll hit for 2.14? Luis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Release notes, Greek bug (Docbook XML related)
Hi Nikos, Today at 14:26, Nikos Charonitakis wrote: can we use the same for Greek release notes if changes in server cant be made in time? This will also have to be arranged with sysadmin team. There is really nothing we can do without privileged access to the machine. So, while you are at it, just have it fixed instead! Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Invariant sections? GFPL
Today at 13:58, Clytie Siddall wrote: Thanks, Danilo. I'm always uncomfortable about translating any legal statements, because I'm not a professional translator with liability insurance. If someone sues and uses my translation as evidence, I'm in real trouble. What is Gnome's position on non-professional (and thus not protected by insurance) translators translating legal statements? GFDL (and any other GNU licenses) itself is valid only in original English language[1]. Translated versions are there only for convenience, so just do not worry about it. Cheers, Danilo [1] http://www.gnu.org/licenses/translations.html ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing to branches :(
Clytie Siddall wrote: Арангел , I'm relieved to hear I'm not the only person having trouble with gnome-volume-manager. The update process worked for every branch file I had, _except_ g-v-m. Yet, it's CVS dir. has a Tag file with contents: Tgnome-2-12 I don't know why it's not working. :( How about this.. hmmm, can anyone check this out? I've uploaded the mk.po for gnome-volume-manager here: http://ufo.softver.org.mk/po/mk.po Can someone try to commit it and see what's wrong? Thanks. -Arangel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing to branches :(
Today at 18:00, Арангел Ангов wrote: How about this.. hmmm, can anyone check this out? I've uploaded the mk.po for gnome-volume-manager here: http://ufo.softver.org.mk/po/mk.po Can someone try to commit it and see what's wrong? This one is already in CVS: http://cvs.gnome.org/viewcvs/gnome-volume-manager/po/mk.po?rev=1.4.2.4only_with_tag=gnome-2-12view=log I have checked, and the diff shows no changes at all. You seem to have outdated CVS checkout instead. Just translate the version grabbed from l10n-status pages and submit that one without using intltool-update mk on it if you are still having problems. Also note that there are some · symbols (centered dot) instead of spaces in some messages, probably a result of copy-pasting in GTranslator (you probably want to fix those). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GnomeMeeting 1.2.2
Hi Damien, Today at 13:51, Damien Sandras wrote: I have created a gnome-2-12 branch. Development will continue in the opal branch which should be merged to HEAD soon when we judge that SIP support is good enough for public consommation! Thanks for the notice: I've now removed gnomemeeting altogether from the Gnome 2.12 translation status pages. Hey, just kidding: translation status pages will use the new branch as soon as they update :) Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Broken build of relnotes
Hi, I tried to build release notes # xml2po -e -p lt.po ../C/release-notes.xml release-notes.xml but I get --- Traceback (most recent call last): File /usr/bin/xml2po, line 750, in ? CurrentXmlMode.postProcessXmlTranslation(doc, translationlanguage, outtxt) File /usr/share/xml2po/docbook.py, line 181, in postProcessXmlTranslation copy.newChild(None, year, match.group(3)) File /usr/lib/python2.4/site-packages/libxml2.py, line 3208, in newChild ret = libxml2mod.xmlNewChild(self._o, ns__o, name, content) UnicodeEncodeError: 'ascii' codec can't encode character u'\u0117' in position 21: ordinal not in range(128) --- Any suggestions how to fix it? Btw, why Python is trying to convert „ė“, to from unicode, to ascii? Žygis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ro broke gnome-doc-utils
On Mon, 2005-09-05 at 14:40 +0300, Mugurel Tudor wrote: On Mon, 2005-09-05 at 04:01 -0500, Shaun McCance wrote: I've had to completely revert the recent changes to ro.po in gnome-doc-utils. The translation was incorrect, and it was causing gnome-doc-utils to fail to build. We are deeply sorry for this, we modified the translation and re-commit it now. Hope it's correct this time. Wow, a full translation of gnome-doc-utils while I slept. You guys are amazing. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gnome-doc-utils and ug, so very close
The ug translation for gnome-doc-utils is one fuzzy string away from being 100% complete. I suspect that one string is really easy. #: ../xslt/gettext/l10n.xml.in.h:865 #, fuzzy msgid msgidpreface.xref/msgid msgstrtitle//msgstr msgstr msgidrefentry.xref/msgid msgstrtitle//msgstr Given how the ug team has chosen to handle other similar xref formattings, I'm betting they just want this: msgstr msgidpreface.xref/msgid msgstrtitle//msgstr Really simple. If I were to roll a tarball right now, I would have to report 28/46 languages with 100% translation. I would love to report 29/46 languages instead. I can wait a few hours, if anybody from the team is around and awake. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken build of relnotes
:) Sorry for false alarm. I'd missed the '\n' part at the end of the first line in translator-credits and on the second line there were non-ascii char (ė) in translators family name which caused xml2po to fail. Fixed it by adding \n at the end of the first line. However, the debugging was tought. Is it possible to make xml2po more verbose on errors in the future? :) Žygis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Invariant sections? GFPL
2005/9/5, Danilo Šegan [EMAIL PROTECTED]: Today at 13:58, Clytie Siddall wrote: GFDL (and any other GNU licenses) itself is valid only in original English language[1]. Translated versions are there only for convenience, so just do not worry about it. Good to know that. Is there a default disclamer notice for that kind of thing? So we don't have to come up with a new way of saying that on each language GNOME is translated for. Sorry if it is a stupid question. :) Cheers -- Pedro de Medeiros - Ciência da Computação - Universidade de Brasília Email: [EMAIL PROTECTED] - Home Page: http://www.nonseq.net Linux User No.: 234250 - ICQ: 2878740 - Jabber: [EMAIL PROTECTED] ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Broken build of relnotes
Yesterday at 19:32, Žygimantas Beručka wrote:
copy.newChild(None, year, match.group(3))
Fix is:
+ copy.newChild(None, year, match.group(3).encode('utf-8'))
(problem is that a name of the translator got pattern matched as year,
and name contains Unicode while libxml2 expects UTF-8)
Cheers,
Danilo
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: docs qs (was: Re: Release notes translated to VI
Thankyou again for your help, Murray. :) Ccing this to cvsmaster, who have always been very helpful, and have a lot of experience in the CVS area. There's a clue in the name, somewhere... ;) On 05/09/2005, at 10:42 PM, Murray Cumming wrote: If you have checked the source out then, wherever, or however, you have checked it out, you can just change the file and do a cvs commit. Ah. I'd thought where they were mattered. Maybe that's just keeping them organized for yourself? I thought a working copy should mirror the on-server structure? Do I edit a changelog? With a text editor. The question was, Do I do it? Not How do I do it? ;) Some commits don't require changelogs, e.g. the debian installer Level 1 via SVN, so I'm learning to check if a changelog edit is required. Working in several different projects can be confusing. :S I don't think we can assume that everyone is experienced in CVS. But you need to learn that sometime. I recommend this: http://developer.gnome.org/tools/cvs.html Thankyou. What I was trying to say, is that there's a distinct gap between I know nothing and I am experienced, and it helps if people take that into account. A bit more information can save questions afterward. If you have checked out gnomeweb-wml/www.gnome.org/start/2.12/ Yay, it worked. :D I didn't know I needed to checkout all that first. No wonder I didn't know what to work with. :S or you are somehow in the 2.12/ directory, then do $ cd press_release $ gedit ChangeLog Thankyou, I just needed to know where to start. I know where the po application files fit in the structure; I didn't know where the docs fit, and I found that confusing. A visual map of the structure helps me a lot, since my processing capacity has been damaged. [In any case, presenting information from different sensory points of view (visual, aural, touch etc.) is generally more effective than only one method.] If you are not starting in exactly the same directory then you will need to understand how to cd into the correct directory. I am quite confident that you can do that. My solemn thanks for that vote of confidence. ;) What do you mean by your locale name? vi is a locale name, I think. Then I add that. There are already several translations, so you should already be able to guess how your files and directories should look. Create the figures directory. For instance, in your docbook/vi directory, $ mkdir figures $ cvs add figures $ cd figures $ cp yourdirectorysomewhere/figure-somethingorother.png . $ cp yourdirectorysomewhere/figure-somethingorother.png . (The filenames must be the same as the filenames in the original docbook/C/figures/) yes, having the directory contents checked out will help a lot here. $ cvs add -kb *.png (The -kb is for binary files in cvs. Try to remember it, though it is annoying.) definitely not intuitive mnemonics. $ cvs commit -m Added vi figures. Thankyou. I'll get started on that right away, now I know where to start. :) I know. However, I can't track build errors, since I don't know what they are. What am I supposed to look for? When I find it, what am I supposed to do? If it doesn't look wrong then don't worry. If it looks wrong and/or mentions error somewhere, then ask here or on irc. Error is fairly intuitive in this context. Thankyou. I'll do that. :) _Another_ mailing list? Where do I find it, please? http://mail.gnome.org/archives/gnome-doc-list/ I've just joined. That's counts 24 mailing lists for i18n projects. frustrated sigh I'll see you there. I'm currently cursing a lot about the shouted copyright messages in the bug-buddy docs... I'd be muttering into my beard — if I had a beard. [Note: get a beard first. Then mutter into it.] from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Latex symbols (was: Re: String freeze break in gedit)
On 06/09/2005, at 12:34 AM, Frank Arnold wrote: Am Montag, den 05.09.2005, 21:35 +0930 schrieb Clytie Siddall: While this is being discussed, I understand the ASCII shorthand for ≤ and ≥, but what do and mean? Thankyou to anyone who can enlighten me. :) These are Latex symbols \gg and \ll or naturally written much greater and much less. Image to see how they look like: http://www.math.tau.ac.il/~elip/latex_symbols3.gif Unicode would be: ≪ U+226A MUCH LESS-THAN ≫ U+226B MUCH GREATER-THAN Frank, thanks a heap for this. Since I'm using UTF-8, I try to input the correct characters if I can, but I don't know latex. With this excellent diagram, I can do much better. Thankyou! from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Invariant sections? GFPL
On 06/09/2005, at 1:13 AM, Danilo Šegan wrote: GFDL (and any other GNU licenses) itself is valid only in original English language[1]. Translated versions are there only for convenience, so just do not worry about it. relieved sigh Thanks, Danilo. I checked, and there isn't an (unofficial) translation of any of those main licences for my language. I can't say I feel really inspired to translate them. :S from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing to branches :(
On 06/09/2005, at 2:29 AM, Danilo Šegan wrote: I have checked, and the diff shows no changes at all. This is really weird. I have grabbed the current po from the status pages and updated it (quite a few of the strings add info about VCDs), then committed it. No change in the status pages. When I get out my current copy and have a look, those changes are not there! I know I've done them, repeatedly. I also doubt that Арангел would have kept trying to commit an un-updated file. You can see our repeated attempts for both languages in the ChangeLogs. There is something very strange here. I'll try again. I'll send you a copy: 1. of the file I have now 2. of the file I get off the status page and 3. of the file I commit today. (Sorry, editing a page and uploading files is beyond me today. :( ) I hope that's useful. I've done those changes over and over... :S from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
