[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-bugs] xDT import problems

From: Jim Busser
Subject: Re: [Gnumed-bugs] xDT import problems
Date: Mon, 15 Nov 2010 23:17:50 -0800

On 2010-11-15, at 12:34 AM, Karsten Hilbert wrote:

>> 1) are files that live in known directories supposed to be automagically 
>> listed?
> No. Because there is no known magic directory associated
> with xDT format files.

I was thinking about .conf configurations (appended) and thinking these could 
define a directory that could be opened so that any files contained therein 
(with or without a filter) could be listed. 

Were these configurational definitions not for listing, but intended to be used 
"blindly: so that when the file exists, a function will work but when the file 
does not exist, a function will not work?

And/or were these intended to work with slave mode?


[XDT profile Terminiko]

filename = /home/ncq/gnumed/tmp/terminiko2gnumed.xdt

[XDT profile TurboMed/Win]

source = TM/Win
encoding = cp437
DOB format = %d%m%Y
filename = C:\Turbomed\patient.xdt


source = PracSoft (fake)
filename = ~/gnumed/xDT/PATIENTS.IN

[CA Medical Manager MSVA]

# typically something along the lines:
#filename = <DRIVE>:\somewhere\VMEDICAL\EXPORT\PATEXPORT

# in the git tree:
filename = ../data/other/CA-MSVA.txt.test


reply via email to

[Prev in Thread] Current Thread [Next in Thread]