You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(11) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(17) |
Feb
(32) |
Mar
(1) |
Apr
(33) |
May
(101) |
Jun
(8) |
Jul
(4) |
Aug
(13) |
Sep
(27) |
Oct
(27) |
Nov
(36) |
Dec
(22) |
2004 |
Jan
(91) |
Feb
(99) |
Mar
(109) |
Apr
(40) |
May
(18) |
Jun
(20) |
Jul
(42) |
Aug
(78) |
Sep
(35) |
Oct
(15) |
Nov
(43) |
Dec
(53) |
2005 |
Jan
(95) |
Feb
(80) |
Mar
(12) |
Apr
(45) |
May
(3) |
Jun
(18) |
Jul
(10) |
Aug
(12) |
Sep
(7) |
Oct
(4) |
Nov
(12) |
Dec
(7) |
2006 |
Jan
|
Feb
|
Mar
(7) |
Apr
(5) |
May
(11) |
Jun
(5) |
Jul
(4) |
Aug
(21) |
Sep
(4) |
Oct
(5) |
Nov
(4) |
Dec
(1) |
2007 |
Jan
|
Feb
|
Mar
(4) |
Apr
(17) |
May
(12) |
Jun
(11) |
Jul
(3) |
Aug
(4) |
Sep
|
Oct
(4) |
Nov
|
Dec
(1) |
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2009 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
(8) |
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(6) |
Nov
(11) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
(62) |
May
(3) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2016 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Edward M. <em...@co...> - 2011-04-19 17:27:31
|
Later on, I'll send a link to prebuilt OS 9 system that includes the Japanese and one or two other language kits. It can be run in the SheepShaver emulator and may help. On 4/19/2011 1:18 PM, Fridrich Strba wrote: > So, > > On 19/04/11 17:16, Edward Mendelson wrote: >> Here's a link to a PDF created by saving to a .PS file and letting OS X convert it: >> http://dl.dropbox.com/u/271144/Kanji.wpmac.pdf >> And here's a screen image of the file open in WPMac: >> Again, I can't judge. Does anyone on the list have the necessary expertise? > The two are not identical at all, told my colleague Kohei Yoshida. Now > the next step would be to gather from mac users some information about > WorldScript. Can we have somewhere the codes for different letters, or > understand the structure? > > I tried to ask Uncle Google, but no information for the while was useful. > > Fridrich > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Libwpd-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libwpd-devel > |
From: Fridrich S. <fri...@bl...> - 2011-04-19 17:18:45
|
So, On 19/04/11 17:16, Edward Mendelson wrote: > Here's a link to a PDF created by saving to a .PS file and letting OS X convert it: > http://dl.dropbox.com/u/271144/Kanji.wpmac.pdf > And here's a screen image of the file open in WPMac: > Again, I can't judge. Does anyone on the list have the necessary expertise? The two are not identical at all, told my colleague Kohei Yoshida. Now the next step would be to gather from mac users some information about WorldScript. Can we have somewhere the codes for different letters, or understand the structure? I tried to ask Uncle Google, but no information for the while was useful. Fridrich |
From: Edward M. <em...@co...> - 2011-04-19 15:17:08
|
On 19 Apr 2011, at 10:56 AM, Fridrich Strba wrote: > <kanji.html> This was interesting enough to send me back to my Mac. I don't know enough Japanese to know whether your HTML simply uses a very different script, but includes the same characters, but the original file looks very different to me. Here's a link to a PDF created by saving to a .PS file and letting OS X convert it: http://dl.dropbox.com/u/271144/Kanji.wpmac.pdf And here's a screen image of the file open in WPMac: |
From: Fridrich S. <fri...@bl...> - 2011-04-19 14:56:22
|
Edward, On 19/04/11 16:52, Edward Mendelson wrote: > I'll have to look at this later today when I can get back to my Mac. It > looks interesting! Disregard the previous attachment, check the following one. F. -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html |
From: Edward M. <em...@co...> - 2011-04-19 14:52:36
|
On 4/19/2011 10:46 AM, Fridrich Strba wrote: > Is the attached html file at least marginally looking like having some > characters right? > > f. > > On 19/04/11 16:07, Edward Mendelson wrote: >> I'm not expert enough in the WPMac file format to learn anything from >> it, but perhaps it may be useful to someone who knows a lot more than I >> do. When I open it in Writer, it's blank except for a single letter "t". I'll have to look at this later today when I can get back to my Mac. It looks interesting! E. |
From: Fridrich S. <fri...@bl...> - 2011-04-19 14:46:18
|
Is the attached html file at least marginally looking like having some characters right? f. On 19/04/11 16:07, Edward Mendelson wrote: > I'm not expert enough in the WPMac file format to learn anything from > it, but perhaps it may be useful to someone who knows a lot more than I > do. When I open it in Writer, it's blank except for a single letter "t". |
From: Fridrich S. <fri...@bl...> - 2011-04-19 14:28:53
|
Hello, Edward On 19/04/11 16:07, Edward Mendelson wrote: > I created a WPMac 3.5e file with a few lines of Japanese kanji. The text > is nonsense - I simply typed in random characters because I know about > ten words of Japanese and don't know how to type them. But it should > give you an idea of how kanji is stored in WPMac files. The file is here: > http://dl.dropbox.com/u/271144/Kanji.wpmac > I'm not expert enough in the WPMac file format to learn anything from > it, but perhaps it may be useful to someone who knows a lot more than I > do. When I open it in Writer, it's blank except for a single letter "t". OK, they are all in the C8 function. Now only if we could find a documentation about the double-byte Mac Script character sets. F. |
From: Fridrich S. <fri...@bl...> - 2011-04-19 14:10:27
|
On Tue, 2011-04-19 at 09:22 -0400, Edward Mendelson wrote: > Thanks for that quick reply. I don't have such a document, but I'll > ask the person who asked me for help, in the hope that he might be > able to create one. Yup, would be good to see how that document is. Whether the characters are stored as charset 12 or not. Because in WP for mac we do two things, first try to map the Mac character that is in the first byte of the 0xCO function, and if we don't succeed, we use the second two bytes to use the mapping of the WP5 character set/character. WP5 character set has some charset for japanese, but it is normally used only for documents that were converterted from windows/dos WP file-formats. Now, there is a function 0xC8 which is defined like this: Double-Byte Script Character <0xC8> (length = 4) [character]double-byte Macintosh script character <0xC8> I strongly suspect that those characters are encoded like that and we don't support this at all. Now, if we could have the table of those or at least parts of such table, it would be ~trivial to extend our coverage by mapping this to unicode. I did not find the tables anywhere and since I did not know how much is this used, I did not dig more. If you manage to get some more information, we can extend our support to this function in a ~trivial way. Cheers F. |
From: Edward M. <em...@co...> - 2011-04-19 14:08:17
|
On 4/19/2011 9:16 AM, William Lachance wrote: > On Tue, Apr 19, 2011 at 8:58 AM, Edward Mendelson <em...@co... > <mailto:em...@co...>> wrote: > > Hello, > > Recently I was asked to help someone convert hundreds of WPMac files > that include Japanese Kanji, files that were created on old Macs > that had the Japanese Language Kits installed. > > It seems - I could be wrong - that libwpd doesn't convert the > characters in those files. The method I found for converting them > was a bit roundabout: > ... > > Use a PowerPC Mac that runs OS 10.4 and "Classic" with the Japanese > Language Kit installed. Open the WPMac files in WPMac in Classic. > Copy the contents of the file to the clipboard. Paste the contents > of the file from the Clipboard into OS X's TextEdit or any other > unicode-aware Mac application. Save the resulting file as an RTF or > DOC file. The resulting file opens correctly in LibreOffice, Pages, > Word, etc. > > This method obviously requires obsolete hardware and software. I > would guess that it would require an enormous amount of effort to > support double-byte CJK and other WorldScript-based scripts in > libwpd, and that the potential need for it is far too small to > justify the effort. But is this something that might someday be > possible in the future? > > > Actually, it's not really that difficult. Unless Japanese is > dramatically different from what we've seen so far, all we should need > to make this conversion work is a table mapping from WordPerfect > extended characters to their unicode equivalents. Over the years we've > expanded support for languages from only plain latin to relatively > obscure ones like Tibetan courtesy of mappings submitted by various people. > > If you don't have the expertise to create such a mapping yourself, we > could probably derive one from (1) a WP document containing all the > characters in a Japanese script and (2) one converted to RTF/DOC. If > you're interested in producing something like this, let us know! > > -- > William Lachance > wr...@gm... <mailto:wr...@gm...> I created a WPMac 3.5e file with a few lines of Japanese kanji. The text is nonsense - I simply typed in random characters because I know about ten words of Japanese and don't know how to type them. But it should give you an idea of how kanji is stored in WPMac files. The file is here: http://dl.dropbox.com/u/271144/Kanji.wpmac I'm not expert enough in the WPMac file format to learn anything from it, but perhaps it may be useful to someone who knows a lot more than I do. When I open it in Writer, it's blank except for a single letter "t". Edward Mendelson Contributing Editor PC Magazine |
From: Edward M. <em...@co...> - 2011-04-19 13:23:05
|
On 19 Apr 2011, at 9:16 AM, William Lachance wrote: > On Tue, Apr 19, 2011 at 8:58 AM, Edward Mendelson <em...@co...> wrote: > Hello, > > Recently I was asked to help someone convert hundreds of WPMac files that include Japanese Kanji, files that were created on old Macs that had the Japanese Language Kits installed. > > It seems - I could be wrong - that libwpd doesn't convert the characters in those files. The method I found for converting them was a bit roundabout: > ... > Use a PowerPC Mac that runs OS 10.4 and "Classic" with the Japanese Language Kit installed. Open the WPMac files in WPMac in Classic. Copy the contents of the file to the clipboard. Paste the contents of the file from the Clipboard into OS X's TextEdit or any other unicode-aware Mac application. Save the resulting file as an RTF or DOC file. The resulting file opens correctly in LibreOffice, Pages, Word, etc. > > This method obviously requires obsolete hardware and software. I would guess that it would require an enormous amount of effort to support double-byte CJK and other WorldScript-based scripts in libwpd, and that the potential need for it is far too small to justify the effort. But is this something that might someday be possible in the future? > > Actually, it's not really that difficult. Unless Japanese is dramatically different from what we've seen so far, all we should need to make this conversion work is a table mapping from WordPerfect extended characters to their unicode equivalents. Over the years we've expanded support for languages from only plain latin to relatively obscure ones like Tibetan courtesy of mappings submitted by various people. > > If you don't have the expertise to create such a mapping yourself, we could probably derive one from (1) a WP document containing all the characters in a Japanese script and (2) one converted to RTF/DOC. If you're interested in producing something like this, let us know! > > -- > William Lachance > wr...@gm... Thanks for that quick reply. I don't have such a document, but I'll ask the person who asked me for help, in the hope that he might be able to create one. Japanese/Chinese/Korean in WPMac formats are I *think* completely different from extended characters in WPDOS/WPWin/WPUnix formats. They don't use the CharacterSet/CharacterNumber system, because thousands of characters are supported in each language. So a document that included the extended characters would be enormous. My guess is that Tibetan fits fairly well into character set 12, but this would be different. Or am I completely wrong about this? Edward Mendelson |
From: William L. <wr...@gm...> - 2011-04-19 13:16:25
|
On Tue, Apr 19, 2011 at 8:58 AM, Edward Mendelson <em...@co...> wrote: > Hello, > > Recently I was asked to help someone convert hundreds of WPMac files that > include Japanese Kanji, files that were created on old Macs that had the > Japanese Language Kits installed. > > It seems - I could be wrong - that libwpd doesn't convert the characters in > those files. The method I found for converting them was a bit roundabout: > ... Use a PowerPC Mac that runs OS 10.4 and "Classic" with the Japanese Language > Kit installed. Open the WPMac files in WPMac in Classic. Copy the contents > of the file to the clipboard. Paste the contents of the file from the > Clipboard into OS X's TextEdit or any other unicode-aware Mac application. > Save the resulting file as an RTF or DOC file. The resulting file opens > correctly in LibreOffice, Pages, Word, etc. > > This method obviously requires obsolete hardware and software. I would > guess that it would require an enormous amount of effort to support > double-byte CJK and other WorldScript-based scripts in libwpd, and that the > potential need for it is far too small to justify the effort. But is this > something that might someday be possible in the future? > Actually, it's not really that difficult. Unless Japanese is dramatically different from what we've seen so far, all we should need to make this conversion work is a table mapping from WordPerfect extended characters to their unicode equivalents. Over the years we've expanded support for languages from only plain latin to relatively obscure ones like Tibetan courtesy of mappings submitted by various people. If you don't have the expertise to create such a mapping yourself, we could probably derive one from (1) a WP document containing all the characters in a Japanese script and (2) one converted to RTF/DOC. If you're interested in producing something like this, let us know! -- William Lachance wr...@gm... |
From: Edward M. <em...@co...> - 2011-04-19 12:58:35
|
Hello, Recently I was asked to help someone convert hundreds of WPMac files that include Japanese Kanji, files that were created on old Macs that had the Japanese Language Kits installed. It seems - I could be wrong - that libwpd doesn't convert the characters in those files. The method I found for converting them was a bit roundabout: Use a PowerPC Mac that runs OS 10.4 and "Classic" with the Japanese Language Kit installed. Open the WPMac files in WPMac in Classic. Copy the contents of the file to the clipboard. Paste the contents of the file from the Clipboard into OS X's TextEdit or any other unicode-aware Mac application. Save the resulting file as an RTF or DOC file. The resulting file opens correctly in LibreOffice, Pages, Word, etc. This method obviously requires obsolete hardware and software. I would guess that it would require an enormous amount of effort to support double-byte CJK and other WorldScript-based scripts in libwpd, and that the potential need for it is far too small to justify the effort. But is this something that might someday be possible in the future? Edward Mendelson Contributing Editor PC Magazine |
From: Fridrich S. <fri...@bl...> - 2011-04-19 06:22:01
|
Hi, Mark, On 18/04/11 17:18, Mark Coolen wrote: > BTW, I have libwpd 0.9.1 and libwpg 0.2.0 from Arch Linux. Is that new > enough? Writerperfect I'll have to install myself (0.8.0). OK, there was a fix landing to the libwpd master after 0.9.1, which was solving some issues with loading documents with mildly corrupted prefix for WP6 parser. Would be good to see whether that one is not solving the issue already before reporting, I guess. F. |
From: Mark C. <mar...@gm...> - 2011-04-18 15:18:49
|
BTW, I have libwpd 0.9.1 and libwpg 0.2.0 from Arch Linux. Is that new enough? Writerperfect I'll have to install myself (0.8.0). Mark On Mon, Apr 18, 2011 at 11:06 AM, Mark Coolen <mar...@gm...> wrote: > I'll see what I can do. I'll make sure I have the latest version to > test on. I'd like to see our organization use LibreOffice as a > replacement for WP, so libwpd et al are an important part of this. > > Mark > > On Fri, Apr 15, 2011 at 5:15 PM, Fridrich Strba > <fri...@bl...> wrote: >> Hello, Mark, >> >> On 15/04/2011 19:51, Mark Coolen wrote: >>> Would it be at all useful to submit .wpd files that don't open >>> correctly with the latest version of libwpd? >> >> Very useful indeed, provided that they don't open correctly with the >> master branch of libwpd/libwpg/writerperfect mix. I fixed some problems >> of document loading last weeks, so some problem might be dupplicates. >> >>> I work in an organization that makes extensive use of WP 12 and can >>> get my hands on many such documents. >> >> Very nice! We normally like to add a sample document corresponding to a >> problem we fixed to our regression testing suite >> <http://libwpd.git.sourceforge.net/git/gitweb.cgi?p=libwpd/libwpd-regression;a=summary> >> to avoid the same class of problems biting us ever again. So, if you are >> submitting a file, it would be nice to specify whether we are legally >> entitled to commit it there. We like to have the problematic document >> public in order to lower the bus factor as much as possible. >> >> Thanks for your willingness to help. >> >> Cheers >> >> Fridrich >> >> ------------------------------------------------------------------------------ >> Benefiting from Server Virtualization: Beyond Initial Workload >> Consolidation -- Increasing the use of server virtualization is a top >> priority.Virtualization can reduce costs, simplify management, and improve >> application availability and disaster protection. Learn more about boosting >> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev >> _______________________________________________ >> Libwpd-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libwpd-devel >> > > > > -- > ___________________________ > | Coolen Software Solutions > | +1.519.652.9378 > | mar...@gm... > |___________________________ > -- ___________________________ | Coolen Software Solutions | +1.519.652.9378 | mar...@gm... |___________________________ |
From: Mark C. <mar...@gm...> - 2011-04-18 15:06:58
|
I'll see what I can do. I'll make sure I have the latest version to test on. I'd like to see our organization use LibreOffice as a replacement for WP, so libwpd et al are an important part of this. Mark On Fri, Apr 15, 2011 at 5:15 PM, Fridrich Strba <fri...@bl...> wrote: > Hello, Mark, > > On 15/04/2011 19:51, Mark Coolen wrote: >> Would it be at all useful to submit .wpd files that don't open >> correctly with the latest version of libwpd? > > Very useful indeed, provided that they don't open correctly with the > master branch of libwpd/libwpg/writerperfect mix. I fixed some problems > of document loading last weeks, so some problem might be dupplicates. > >> I work in an organization that makes extensive use of WP 12 and can >> get my hands on many such documents. > > Very nice! We normally like to add a sample document corresponding to a > problem we fixed to our regression testing suite > <http://libwpd.git.sourceforge.net/git/gitweb.cgi?p=libwpd/libwpd-regression;a=summary> > to avoid the same class of problems biting us ever again. So, if you are > submitting a file, it would be nice to specify whether we are legally > entitled to commit it there. We like to have the problematic document > public in order to lower the bus factor as much as possible. > > Thanks for your willingness to help. > > Cheers > > Fridrich > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Libwpd-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libwpd-devel > -- ___________________________ | Coolen Software Solutions | +1.519.652.9378 | mar...@gm... |___________________________ |
From: Mark a. N. <the...@gm...> - 2011-04-18 12:38:42
|
I'll see what I can do. I'll make sure I have the latest version to test on. I'd like to see our organization use LibreOffice as a replacement for WP, so libwpd et al are an important part of this. Mark On Fri, Apr 15, 2011 at 5:15 PM, Fridrich Strba <fri...@bl...> wrote: > Hello, Mark, > > On 15/04/2011 19:51, Mark Coolen wrote: >> Would it be at all useful to submit .wpd files that don't open >> correctly with the latest version of libwpd? > > Very useful indeed, provided that they don't open correctly with the > master branch of libwpd/libwpg/writerperfect mix. I fixed some problems > of document loading last weeks, so some problem might be dupplicates. > >> I work in an organization that makes extensive use of WP 12 and can >> get my hands on many such documents. > > Very nice! We normally like to add a sample document corresponding to a > problem we fixed to our regression testing suite > <http://libwpd.git.sourceforge.net/git/gitweb.cgi?p=libwpd/libwpd-regression;a=summary> > to avoid the same class of problems biting us ever again. So, if you are > submitting a file, it would be nice to specify whether we are legally > entitled to commit it there. We like to have the problematic document > public in order to lower the bus factor as much as possible. > > Thanks for your willingness to help. > > Cheers > > Fridrich > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Libwpd-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libwpd-devel > |
From: Fridrich S. <fri...@bl...> - 2011-04-15 21:15:50
|
Hello, Mark, On 15/04/2011 19:51, Mark Coolen wrote: > Would it be at all useful to submit .wpd files that don't open > correctly with the latest version of libwpd? Very useful indeed, provided that they don't open correctly with the master branch of libwpd/libwpg/writerperfect mix. I fixed some problems of document loading last weeks, so some problem might be dupplicates. > I work in an organization that makes extensive use of WP 12 and can > get my hands on many such documents. Very nice! We normally like to add a sample document corresponding to a problem we fixed to our regression testing suite <http://libwpd.git.sourceforge.net/git/gitweb.cgi?p=libwpd/libwpd-regression;a=summary> to avoid the same class of problems biting us ever again. So, if you are submitting a file, it would be nice to specify whether we are legally entitled to commit it there. We like to have the problematic document public in order to lower the bus factor as much as possible. Thanks for your willingness to help. Cheers Fridrich |
From: Mark C. <mar...@gm...> - 2011-04-15 17:52:17
|
Hi; Would it be at all useful to submit .wpd files that don't open correctly with the latest version of libwpd? I work in an organization that makes extensive use of WP 12 and can get my hands on many such documents. |
From: William L. <wr...@gm...> - 2010-11-19 04:21:55
|
I just migrated the following modules to git: libwpg-www perfectspot wpgtest I think this completes everything, because as far as I know we didn't want to move the other (obsolete) modules over from CVS. Just in case I'm wrong, here's the procedure I used to do this, so someone else can finish the work if I'm busy (obviously substitute your sourceforge username for mine): aubergine:perfectspot wlach$ ssh -t lachancew,li...@sh... create ... -bash-3.2$ -bash-3.2$ cd /home/scm_git/l/li/libwpg -bash-3.2$ mkdir <module> # e.g. perfectspot -bash-3.2$ git --git-dir=<module> init --shared=all --bare Then, on the client end of things: aubergine:libwpg-www wlach$ cvs -d:pserver:ano...@li...:/cvsroot/libwpg login aubergine:libwpg-www wlach$ git cvsimport -A ~/Documents/libwpg-authors.txt -o master -d :pserver:ano...@li.../cvsroot/libwpg <modulen> Where libwpg-authors.txt is a text file containing author info for libwpg. Here's the one I used for perfectspot, libwpg-www, and wpgtest: strbafridrich = Fridrich Strba <fri...@bl...> ariya = Ariya Hidayat <ar...@kd...> When you've done that, you're ready to push: git remote add origin ssh://lac...@li.../gitroot/libwpg/<module> git push --mirror origin And that's it! If there's no further action required, I'll probably be turning off CVS on sourceforge for libwpd/libwpg in the next week or so. -- William Lachance wr...@gm... |
From: William L. <wr...@gm...> - 2010-11-18 03:00:26
|
2010/11/17 Fridrich Strba <fri...@bl...>: > Hello, good people. > > Since the shell access on sourceforge.net is now a bit more difficult to > script, I came with a different approach to updating the web-pages: > > For libwpd: I cloned a read-only libwpd-www git repository to htdocs > directory and updating is done basically by pushing your local git to > the server and then pulling it from the shell on the web-space. > > For libwpd: I checked out the libwpg-www CVS repository to htdocs and > the updating is done by committing into the server CVS repo and updating > it on the web-space. I assume you mean libwpg here. We really should just by using git for everything. It looks like I forgot to convert all the modules for libwpg: I'll try to get to this later tonight. > This has two advantages: > > 1) I hope that it helps us to keep the git repos on the server in sync > with our local git repos which does not seem to have been the case right > now :) Oops, guess I forgot to commit my later changes. > 2) It works around the new way of accessing the shell services on > sourceforge.net, where one has to create the shell using "ssh -t > USERNAME,PR...@sh... create" before being able to > access that shell for 4 hours. After which it is again destroyed :) > > I hope I did not mess up anybody For libwpd, I'd actually automated the process of updating the web site using the sync-me script, unfortunately that didn't get pushed: #!/bin/bash [ -z $1 ] || UNAME=$1 scp ./*html ./*png ./*jpg ./*css ./*dia $UNAME,li...@we...:/home/groups/l/li/libwpd/htdocs ssh $UNAME,li...@we... chmod g+w /home/groups/l/li/libwpd/htdocs/* I like the idea of always using what's stored in git for the web site. Maybe we could write a new shell script that does the pull for you automatically? What's the manual procedure you're currently using for that? -- William Lachance wr...@gm... |
From: William L. <wr...@gm...> - 2010-11-18 00:56:06
|
Awesome work everyone! (especially Fridrich) I'm cracking open a newcastle to celebrate as I type this. :) For those interested, I wrote up a blog entry (with screenshots) highlighting the new features of libwpd 0.9.0 here: http://masalalabs.ca/2010/11/back-to-wordperfect-libwpd-0-9-0/ Will 2010/11/17 Fridrich Strba <fri...@bl...>: > Hello, good people, > > The good news is that on Tuesday, November 16th 2010, after more then > five years of development, libwpd 0.9.0 and writerperfect 0.8.0 have > been released. > > libwpd 0.9.0 is not backward compatible with libwpd 0.8.14. Both 0.9.x > and 0.8.x series are installable in parallel except for the wpd2html and > wpd2text tools. > > The main features of this release are: > > * Conversion of page-numbering. > * Conversion of embedded images and text boxes in WP1, WP3, WP5 > and WP6 documents. > * Conversion of password protected WP1, WP3, WP42 and WP5 > documents. > * Conversion of annotations/comments in WP6 parser. > * Fix some greek characters so that Text written in WP5.1 with > Printer Polyglott convert correct. > * Fix unicode mappings of some older Symbol and Dingbats fonts. > * Drop the libgsf dependency in favour of pure C++ implementation > of the WPXInputStream interface. > * Fix the footnote/endnote/comment/annotation/textbox writing in > wpd2html converter. > * Improve metadata parsing. > > The libwpd development team hopes that you enjoy the new functionality > and that you stay tuned for more exciting news. > > Cheers > > Fridrich > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > Libwpd-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libwpd-devel > -- William Lachance wr...@gm... |
From: Fridrich S. <fri...@bl...> - 2010-11-17 12:08:03
|
Hello, good people, The good news is that on Tuesday, November 16th 2010, after more then five years of development, libwpd 0.9.0 and writerperfect 0.8.0 have been released. libwpd 0.9.0 is not backward compatible with libwpd 0.8.14. Both 0.9.x and 0.8.x series are installable in parallel except for the wpd2html and wpd2text tools. The main features of this release are: * Conversion of page-numbering. * Conversion of embedded images and text boxes in WP1, WP3, WP5 and WP6 documents. * Conversion of password protected WP1, WP3, WP42 and WP5 documents. * Conversion of annotations/comments in WP6 parser. * Fix some greek characters so that Text written in WP5.1 with Printer Polyglott convert correct. * Fix unicode mappings of some older Symbol and Dingbats fonts. * Drop the libgsf dependency in favour of pure C++ implementation of the WPXInputStream interface. * Fix the footnote/endnote/comment/annotation/textbox writing in wpd2html converter. * Improve metadata parsing. The libwpd development team hopes that you enjoy the new functionality and that you stay tuned for more exciting news. Cheers Fridrich |
From: Fridrich S. <fri...@bl...> - 2010-11-17 12:03:48
|
Hello, good people. Since the shell access on sourceforge.net is now a bit more difficult to script, I came with a different approach to updating the web-pages: For libwpd: I cloned a read-only libwpd-www git repository to htdocs directory and updating is done basically by pushing your local git to the server and then pulling it from the shell on the web-space. For libwpd: I checked out the libwpg-www CVS repository to htdocs and the updating is done by committing into the server CVS repo and updating it on the web-space. This has two advantages: 1) I hope that it helps us to keep the git repos on the server in sync with our local git repos which does not seem to have been the case right now :) 2) It works around the new way of accessing the shell services on sourceforge.net, where one has to create the shell using "ssh -t USERNAME,PR...@sh... create" before being able to access that shell for 4 hours. After which it is again destroyed :) I hope I did not mess up anybody Cheers Fridrich |
From: William L. <wr...@gm...> - 2010-11-02 22:06:28
|
2010/11/2 <Lau...@lo...>: > Hello, > when testing if my version of libwps still works with the new version of libwpd, one test <<ends>> in a infinite loop. > This is probably my fault, but as this infinite loop can be easily avoided by the following patch > > > a small proposition... I'm not sure if I'm totally comfortable with the patch. It sounds like maybe in your case you're not setting the page span correctly? I think the right fix is to fix that problem rather than change the logic of how page spans work. -- William Lachance wr...@gm... |
From: <Lau...@lo...> - 2010-11-02 07:52:25
|
Hello, when testing if my version of libwps still works with the new version of libwpd, one test <<ends>> in a infinite loop. This is probably my fault, but as this infinite loop can be easily avoided by the following patch |