On Mon, Feb 26, 2001 at 12:48:35PM -0500, Enrique Vega wrote:
> on 2/26/01 2:30 AM, Alexander Bokovoy at [EMAIL PROTECTED] wrote:
> 
> >> Alexander, I've read the repligard chapter and you are correct in saying
> >> that it is a basic overview of the replication process. That's it! The
> >> documentation seems to assume that the user is an expert programmer. This
> >> would be ok if all of us intending to use repligard were experts, but I have
> >> to tell you that this is not the case for all of the users that will use
> >> repligard.
> > I understand. Unfortunately, my English skills are far from needed for
> > creating
> > something readable as far as documentation concerned :-( If somebody more
> > skilled
> > and with Russian knowledge could do (good) translation, I'll be happy to
> > communicate.
> Alexander, if my programming skills were as good as your English skills, I
> would consider myself an expert. Your English communication skills are
> fantastic! So please don't consider yourself a poor English communicator.
Thank you :-) But communication and documentation are different sides of
lingiustic story. Ron Parker can prove this in more elegant English manner :-)

> I have a friend who knows some Russian. She lived in Belaruse (?) for six
> months. I'm not sure if she could help, but if you would like for me to put
> the two of you in contact, I'll be happy to do so.
Let's give this proposal a try.

> >> which of these would repligard use? Both?
> > I'm assuming that 'accolarts.org' and 'artmetal.com' are names of sitegroups.
> > In this case, login info should be 'user!sitegroup'. Reason for it is that
> > Repligard cannot deduce sitegroup from host information like mod_midgard
> > because there is no host information provided when user runs Repligard.
> 
> So if accollarts.org is sitegroup 2 I would use the username 'enrique!2' ?
Each sitegroup has a name, if your SG2 has name '2', then true. If it is
called 'accolarts.org', then use 'enrique!accolarts.org' or 'enrique+accolarts.org'
for admin access.

> >> <!ATTLIST database schema CDATA #REQUIRED>
> >> <!ATTLIST database name CDATA #REQUIRED>
> >> <!ATTLIST database username CDATA #REQUIRED>
> >> <!ATTLIST database password CDATA #REQUIRED>
> >> <!ATTLIST database encoding CDATA #REQUIRED>
> >> <!ATTLIST database blobdir CDATA #REQUIRED>
> >> 
> >> <!ELEMENT login EMPTY>
> >> <!ATTLIST login username CDATA #REQUIRED>
> >> <!ATTLIST login password CDATA #REQUIRED>
> >> 
> >> <!ELEMENT replicate (resource*)>
> >> <!ATTLIST replicate all (yes|no) 'no'>
> >> 
> >> <!ELEMENT resource EMPTY>
> >> <!ATTLIST resource type CDATA #IMPLIED>
> >> <!ATTLIST resource id CDATA #IMPLIED>
> >> <!ATTLIST resource guid CDATA #IMPLIED>
> >> ]>
> > Schema above describes fully which elements and their attributes can be used
> > and which of them are required.
> 
> I can understand the schema a little. I guess if it was in Russian I would
> probably understand it as much. ;-)
:-) Well, if you'll have some spare time, do not hesitate to look at
http://www.xml.com/pub/a/98/10/guide2.html for Norman Walsh's article
named "What do XML documents Look Like?". It is worth to read.

-- 
Sincerely yours, Alexander Bokovoy 
  The Midgard Project   | www.midgard-project.org |    Aurora R&D team 
Minsk Linux Users Group |    www.minsk-lug.net    |  www.aurora-linux.com  
   IPLabs Linux Team    |     linux.iplabs.ru     | Architecte Open Source
-- We are each only one drop in a great ocean -- but some of the drops sparkle!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to