Stefan Ritt wrote:

Andreas Luedeke wrote: Jim Tinlin wrote: Andreas Luedeke wrote: scogordo wrote: I've been asked to export one of our logbooks to xls or csv. Doable? Thanks, Scott Hi Scott, yes, every user can export entries using the "find" command. Just select the export format in the first line Export to:  CSV ("," separated)   CSV (";" separated)   XML   Raw     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program. I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document. There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format. I tried EXPORTING logbooks as .csv but have not been fully successful.  Elog seems to only export the data entered for various fields with the exception of the text field. Here is an example export from my logbook (used to track simulator problems), I would like to also export the TEXT field so it can be used by my managers in excel...but as you can see there is no entry for "TEXT" fields... Thanks in advance! "Message ID","Date","Author","Type","Status","Priority" 107,Thu  30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low" 106,Thu  30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low" 105,Thu  30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium" 104,Thu  30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium" 103,Wed  29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High" 102,Wed  29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High" Yes, you're right: the text field is only exported in XML and Raw mode. It is questionable how EXCEL should cope with HTML or ELCode output from the text fields. But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.   I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'. (This string has not yet been added to the localization.) As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text. Of course the spreadsheet programs just display the HTML source.   Stefan, do you think this should be added to the official branch?     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.

 Has this been added yet?

I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.

Thanks!

Jim Tinlin wrote:

Stefan Ritt wrote: Andreas Luedeke wrote:   Yes, you're right: the text field is only exported in XML and Raw mode. It is questionable how EXCEL should cope with HTML or ELCode output from the text fields. But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.   I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'. (This string has not yet been added to the localization.) As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text. Of course the spreadsheet programs just display the HTML source.   Stefan, do you think this should be added to the official branch?  Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.   Has this been added yet? I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work. Thanks!

Andreas

> > Well I didn't crash the server this time, and I could invert the image in the demo logbook by doing two rotations.
> > But, this is elog v2.9.0-2435, and I am using v2.9.2-2475.  And I remember there was a recent issue about the image manipulation at some point, so I went to the
> > download section to read the subversion listing to find where this occurred.  But you've changed subversion!  I couldn't find my way around it, so I not only could
> > I find the changefile that showed what happened for each subversion issue, but even how I could download the current (or indeed any past) subversion issue.
> > 
> > As far as I can recall, you made a change, I reported an issue, and you undid the change, or partially undid it.  Do you know when this was?  Could it be relivent?
> 
> I upgraded to V2.9.2, so please try again.
> 
> /Stefan

I can confirm this bug in V2.9.2. Also after submitting the entry, the orginal image is being displayed, with no rotation, resizing etc...

> I can confirm this bug in V2.9.2. Also after submitting the entry, the orginal image is being displayed, with no rotation, resizing etc...

Have you tried on the Demo logbook on the PSI server or on your installation. I just attached an image to this entry, rotated it twice, reduced its size 
and it works fine. The point is that I have to reproduce your bug in order to fix it, but it seems I cannot.

/Stefan

 Hi all

Tested browsers on my SL6.4 desktop computer are Firefox 17.07, Konqueror 4.3.4. Here the rotation and rescaling is all wonky and the changes are  not saved when submitting the entry.

On my Android mobile phone (Chrome 28.0.1500.64) the images rotate and rescale nicely, but the changes are not saved aswell. I tried to force reloading and clearing my cache with all of the browsers.

The elogs I tested are served from Ubuntu 10.04.4 LTS and Debian 3.2.46-1 x86_64 running IM 6.5.7-8 and 6.7.7-10 respectively.

Martin

Yes. Just make sure that both elog servers are not running when you move the password file. 

> Hello,
> 
> I've had much success and use with ELOG.  However there is one thing that I wish I could figure out in order to 
> make ELOG work exactly as I need it.
> 
> When I either create a new ELOG entry, or, have one created via an automated scrip run by CRON, the paragraph 
> width is preset. 
> 
> I've read the notes and experimented with setting the text size, but it seems that if I either adjust it via the 
> config file, or, change the size by dragging the message box itself, then I end up with an ELOG entry that has an 
> irregular message size to it than all the others.  Consistency and uniformity is very important to me for how I 
> use ELOG.
> 
> It would be idea, if the log entries did not contain <CR>'s or justified lines.  In other words, I would like to 
> be able to have my ELOG entry fill the width of the screen, be it a wide screen or standard portrait scree, and 
> at whatever resolution and text size I have my browser set to.
> 
> By not filling the entire width (and also by not having it auto adjust depending on screen size, resolution, 
> etc.) there are large portions of the screen real estate that is lost and you end up with very long, scrolling 
> log entries versus entries that file the entire width and therefor take less vertical screen space.
> 
> With all that said -- Does anyone else have this issue?  And, is there anything I can do to correct this?  This 
> would make me a very happy user if it could be done.
> 
> Thank you in advance!
Hi Ryan,

Do you quote the previous entries in later entries, with the '>' character (as above)?  I ask this because that will
make what you are requesting much more complicated, soon making those previous entries very difficult to read
indeed.

For me, readabiliy of previous quoted entries is important - along with the indenting '>' character to denote each
entry - your request would be an issue for me simply because of how many times an entry may get re-quoted in later
replies - over 40 is not uncommon.  As such, I tend to keep my lines short when writing an entry, being aware
that it could soon have a large number of '>' characters preceeding it.

[Sep 03 07:30]
Not an aside as such, but I have tried to experiment with this quoting business, to remove the '>' character (easy
enough) but have each quoted reply headed with a simple date/timestamp *within* this text box, such as I headed this
paragraph.  It hasn't worked as I expected, and I'm not sure why - maybe it might even be a bug!  But if that
could be cracked, then your suggestion would be a boon to me as well.
 

 One hour adrift at this time of the year sounds like daylight saving.  Or compensation thereof.  What is your computer clock set to (not what time the clock reads)?

Personally I think it rather naughty that [at least older] Windoze automatically sets the clock one hour forward the first reboot after the spring switch forward, and the same in the autumn back.  What if you'd already done it, like all the rest of the clocks in the house?