|
[Feb. 9th, 2003|04:47 pm]
LogJam
|
I just committed my "entrycache" branch to the main CVS. It's not complete and it has a different file format for configuration, so (as always :P) don't grab CVS if you can't handle the bleeding edge.
These changes are the steps towards making LogJam work with offline copies of your journal. For now, you can save an entry you're working on as a "draft", which is managed by LogJam (it gets stuck as an XML file under ~/.logjam/servers/servername/users/username/drafts/n) and is nicer than having LogJam save files littered all over your home directory. (The offline journal will use GNU dbm for speed, once I write it.)
I updated the Windows build a few days ago, so that should work again. (Does anyone actually use LogJam on Windows?)
Finally, thanks go to Ricardo Mones Lastra for contributing a Spanish translation. After clicking about while running LogJam in Spanish, I found a lot more strings to marked as translatable, so the translations could all use updates. (I will mail the translators directly once I'm nearing release; if you care to update your translation / contribute a new translation now, though, that's good too.)
Current translation status:
$ for i in *.po; do echo -n "$i: "; ./completion.pl $i; done
en_GB.po: 6 translated out of 382 total: 1.57% complete.
es.po: 337 translated out of 382 total: 88.22% complete.
he.po: 247 translated out of 382 total: 64.66% complete.
ru_RU.po: 245 translated out of 382 total: 64.14% complete. |
|
|
| Comments: |
![[User Picture]](https://l-userpic.livejournal.com/54541970/2) | From:  brad
2003-02-09 05:32 pm (UTC)
| (Link)
|
I use Logjam for Windows.
The filename seems kind of cumbersome. Why not ~/.logjam/drafts/username@server.date or something like that?
From: evan
2003-02-09 05:54 pm (UTC)
| (Link)
|
1) When you rename a server, I only need to rename one directory.
2) Offline journal copies will be at .logjam/.../username/journal/ or something like that.
![[User Picture]](https://l-userpic.livejournal.com/89017570/479302) | From: wolfieboy
2003-02-09 06:43 pm (UTC)
Re: don't grab CVS if you can't handle the bleeding edge | (Link)
|
Did you possibly tag it before the change?
From: evan
2003-02-09 06:54 pm (UTC)
Re: don't grab CVS if you can't handle the bleeding edge | (Link)
|
No, I didn't. All that has really changed is the structure for saving entries (Entry->Save, Entry->Load, and submenus) so if you avoid those you're ok. (Deleted comment)
From: evan
2003-02-10 12:47 am (UTC)
Re: if you care to update your translation / contribute a new translation | (Link)
|
It'd be very welcome! Here is a post directing you to more information. (Deleted comment)
From: evan
2003-02-11 02:37 am (UTC)
 Re: if you care to update your translation / contribute a new translation
| (Link)
|
Mail it to me as an attachment and I'll include it.
![[User Picture]](https://l-userpic.livejournal.com/101446490/123760) | From: stas
2003-02-10 03:35 am (UTC)
slightly off-topic | (Link)
|
Is 3.0 branch stil supported? I can't use 4.0, since it requires GTK2, which pretty much would require reinstalling all the OS (GTK2 has a lot of dependencies, and I have Redhat 6.2 and don't want to waste a work-week to upgrade just for Logjam). And 3.0 does not work lately - gives various "protocol errors". If it's supported, I can quote the errors and the situations where they happen.
From: evan
2003-02-11 02:38 am (UTC)
Re: slightly off-topic | (Link)
|
I haven't really considered supporting 3.0, though if there's anything obviously wrong I'd be happy to fix it. Those errors are likely LogJam being unable to interpret the LiveJournal response when there's an error on LiveJournal's end. High site load tends to make these things unreliable.
I don't know how hard it is to get GTK2 running in Redhat but it shouldn't be that bad. LogJam 4 is significantly better... :)
| From: stas
2003-02-11 03:11 am (UTC)
Re: slightly off-topic | (Link)
|
No, the errors happen when I try to load firends list, for example. It is reproducible - happens every time. After it finishes loading data, it says "Unable to parse server response". Also, when I try to load old record via the calendar, it displays "cannot be shown" as entry titles and when I click on the entry is says: "Client error: Protocol version mismatch: Cannot display/edit a Unicode post with a non-Unicode client. Please see http://www.livejournal.com/support/encodings.bml for more information." As for RH - it shouldn't be, maybe, but it is. All compiled RPMS are for libc used with RH7 and RH8 - means I have to compile all GTK package anew, with all dependencies. Would take a lot of time, and at the end I'm not even sure it will live peacefully with old GTK install I have...
From: evan
2003-02-11 12:08 pm (UTC)
Re: slightly off-topic | (Link)
|
Oh, hmm. GTK 1.2 doesn't support Unicode, so LogJam 3.x doesn't support it either. If you were writing English you might be able to just force the unicode flag on, but since I see Cyrillic (Russian? I can't tell the Cyrillic languages apart, yet) and Hebrew you're likely out of luck unless you want to write some code that transcodes between your local language and UTF-8. (GTK2, on the other hand, supports Hebrew quite well, or at least that's what gaal tells me: LogJam running in right-to-left Hebrew.) Sorry... :\ | |
