Return-Path: Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: (qmail 14300 invoked from network); 12 Sep 2006 00:41:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Sep 2006 00:41:35 -0000 Received: (qmail 81851 invoked by uid 500); 12 Sep 2006 00:41:35 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 81816 invoked by uid 500); 12 Sep 2006 00:41:35 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" List-Id: Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 81805 invoked by uid 99); 12 Sep 2006 00:41:35 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Sep 2006 17:41:35 -0700 Authentication-Results: idunn.apache.osuosl.org smtp.mail=fuzzylogic@apache.org; spf=permerror X-ASF-Spam-Status: No, hits=-9.8 required=5.0 tests=ALL_TRUSTED,NO_REAL_NAME Received-SPF: error (idunn.apache.osuosl.org: domain apache.org from 140.211.166.113 cause and error) Received: from ([140.211.166.113:62150] helo=eris.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id BE/B0-28385-44206054 for ; Mon, 11 Sep 2006 17:41:42 -0700 Received: by eris.apache.org (Postfix, from userid 65534) id BB0091A981A; Mon, 11 Sep 2006 17:41:26 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r442401 - in /db/derby/docs/trunk/src: adminguide/ devguide/ getstart/ pt_BR/adminguide/ pt_BR/getstart/ pt_BR/ref/ ref/ tuning/ Date: Tue, 12 Sep 2006 00:41:25 -0000 To: derby-commits@db.apache.org From: fuzzylogic@apache.org X-Mailer: svnmailer-1.1.0 Message-Id: <20060912004126.BB0091A981A@eris.apache.org> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: fuzzylogic Date: Mon Sep 11 17:41:23 2006 New Revision: 442401 URL: http://svn.apache.org/viewvc?view=rev&rev=442401 Log: DERBY-1223: Update Getting Started guide to include instructios on setting JAVA_HOME and DERBY_HOME. Committed for Laura Stewart Removed: db/derby/docs/trunk/src/getstart/cgsmanuallysetting.dita db/derby/docs/trunk/src/getstart/tgs36360.dita Modified: db/derby/docs/trunk/src/adminguide/adminconrefs.dita db/derby/docs/trunk/src/devguide/devconrefs.dita db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita db/derby/docs/trunk/src/getstart/cgsusingsysinfo.dita db/derby/docs/trunk/src/getstart/cgsusingtoolsutils.dita db/derby/docs/trunk/src/getstart/getstartderby.ditamap db/derby/docs/trunk/src/getstart/gsconrefs.dita db/derby/docs/trunk/src/getstart/rgslib27507.dita db/derby/docs/trunk/src/getstart/tgs26250.dita db/derby/docs/trunk/src/getstart/tgsrunningij.dita db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita db/derby/docs/trunk/src/pt_BR/adminguide/adminconrefs.dita db/derby/docs/trunk/src/pt_BR/getstart/gsconrefs.dita db/derby/docs/trunk/src/pt_BR/ref/refconrefs.dita db/derby/docs/trunk/src/ref/refconrefs.dita db/derby/docs/trunk/src/tuning/tunconrefs.dita Modified: db/derby/docs/trunk/src/adminguide/adminconrefs.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/adminconrefs.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/adminguide/adminconrefs.dita (original) +++ db/derby/docs/trunk/src/adminguide/adminconrefs.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,7 @@ + + - - +--> Product specific entities @@ -29,7 +29,7 @@

Derby

Apache Derby

Derby_10

-

DERBY_INSTALL

+

DERBY_HOME

derby

 @@ -56,4 +56,3 @@ - Modified: db/derby/docs/trunk/src/devguide/devconrefs.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/devconrefs.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/devguide/devconrefs.dita (original) +++ db/derby/docs/trunk/src/devguide/devconrefs.dita Mon Sep 11 17:41:23 2006 @@ -1,8 +1,7 @@ - + - - Product specific entities @@ -31,7 +29,7 @@

Derby

Apache Derby

Derby_10

-

DERBY_INSTALL

+

DERBY_HOME

derby

 @@ -59,4 +57,3 @@ - Modified: db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita (original) +++ db/derby/docs/trunk/src/getstart/cgsinstallingderby.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,5 @@ + Installing Derby -In order to install you +To install you must first download the zip or tar archive from the Web site. + +DerbyinstallinginstallDerby +distributionsbindistributionslib +distributionslib-debugdistributionssrc + + -

Navigate your Web browser to Navigate your Web browser to . This downloads page provides several distributions of , -including snapshot packages as well as stable-version binary distributions. -You will also find information on accessing the active source distributions -for . The distributions -come in bin, lib and src packages. This guide assumes -that you have downloaded the bin distribution package.

+including prerelease snapshots as well as stable-version binary distributions. +You will also find information on how to use the Subversion version control +system to access the source +code that is currently in development.

+

The distributions are:

    +
  • The bin distribution contains scripts, demonstration programs, +and documentation. The optimized jar files are available in the lib distribution.
    • +
  • The lib distribution contains an optimized, small footprint set +of the Derby jar files for deployment.
    • +
  • The lib-debug distribution contains a larger footprint set of the +Derby jar files that are useful for debugging or reporting issues.
    • +
  • The src distribution contains the source files that are used to +create the bin, lib, and lib-debug distributions.
    • +

+

This guide assumes that you have downloaded the bin distribution.

Extract the downloaded package. The extracted installation contains several subdirectories:

    -
  • The demo subdirectory contains demonstration programs.
    • -
  • The frameworks subdirectory contains scripts for executing +
  • The demo subdirectory contains the demonstration +programs.
    • +
  • The bin subdirectory contains the scripts for executing utilities and setting up the environment.
    • -
  • The javadoc subdirectory contains the api documentation +
  • The javadoc subdirectory contains the api documentation that was generated from source code comments.
    • -
  • The doc subdirectory contains the documentation.
    • -
  • The lib subdirectory contains the jar +
  • The doc subdirectory contains the documentation.
    • +
  • The lib subdirectory contains the jar files.

 Modified: db/derby/docs/trunk/src/getstart/cgsusingsysinfo.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/cgsusingsysinfo.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/getstart/cgsusingsysinfo.dita (original) +++ db/derby/docs/trunk/src/getstart/cgsusingsysinfo.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,5 @@ + -Using sysinfo -'s sysinfo -tool displays information about your Java environment and your version of . +Using the sysinfo tool +The sysinfo tool +displays information about your Java environment and your version of . + +Derbytools, sysinfo +sysinfo toolrunning + -

The sysinfo script sets the appropriate environment variables, including -the classpath, and executes the sysinfo program. Once you have the /bin directory -in your PATH, run sysinfo by entering the following in a command window:

-sysinfo +

After you add the /bin directory +to your PATH environment variable, run the sysinfo tool. +The sysinfo script sets the appropriate environment variables, +including the classpath, and runs the sysinfo tool. To +run the sysinfo tool, issue the following command in a +command window: sysinfo

+

 Modified: db/derby/docs/trunk/src/getstart/cgsusingtoolsutils.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/cgsusingtoolsutils.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/getstart/cgsusingtoolsutils.dita (original) +++ db/derby/docs/trunk/src/getstart/cgsusingtoolsutils.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,5 @@ + -Using the tools and startup utilities - tools include -dblook, ij, and sysinfo. utilities -include the import, export and database class utilities. +Using the <ph conref="gsconrefs.dita#prod/productshortname"></ph> tools +and startup utilities +There are several tools and utilities that you might want to use +as you begin to work with . -Tools and utilities +Derbyscripts, using +Derbytools, usingtoolsin +Derbyscriptsin Derby + -

The /frameworks/embedded/bin directory contains scripts for running some -of the tools and utilities -in embedded mode. You can find similar scripts for running tools and utilities -for the Network Server in the /frameworks/NetworkServer/bin directory. In -discussion of these tools and utilities in embedded mode, the /frameworks/embedded/bin -directory is referred to as the /bin directory unless stated otherwise.

-

The scripts have descriptive names such as sysinfo.bat or ij.ksh. -Like the classpath scripts, these scripts end with different extensions depending -on your environment. Windows scripts have a .bat extension, while Unix scripts -have a .ksh extension. You might need to modify these scripts in order for -the tools and utilities to run properly on Windows and Unix platforms.

-

The following information applies only to UNIX platforms.

-

In order to use the script files to run the tools and utilities, do the -following:

-
    -
  1. Turn on the execute bit for the script files. For example:chmod +x fileName

    where fileName is -any script file with a .ksh extension. This tells the system to execute the -commands in the script every time you use it.

    2. -
  2. Add the /bin directory to your PATH variable. This allows you to use shortened -commands to start the tools.
    3. -
-

For more information on scripts, see .

+

The tools that are included with are dblook, ij, +and sysinfo. You can use the scripts +to start the tools.

+

There are Derby utilities that are system procedures that you can call +by using the ij tool. . For example, there are system procedures +that you can use to import and export external files. Instructions on how +to use these system procedures are included in the and +the .

+

The scripts that run these tools are in the /bin directory. +These scripts also help you set up your classpath.

+

The scripts in /bin directory +are setup to run in the embedded mode. To run these tools with the Network +Server, use the following commands:

    +
  • For the dblook tool, call the script and specify the +-d option and the full URL to the Network Server database. For example: dblook +-d 'jdbc:derby://localhost/myDB;user=usr;'
    • +
  • For the ij tool, issue the command set DERBY_OPTS=-Dij.protocol=jdbc:derby://localhost/ and +then start ij by issuing the command ij.
    • +
  • For the sysinfo tool, issue the command NetworkServerControl +sysinfo.
    • +

+

To show how to use the scripts +to launch the tools, +the examples in the assume +that you are using the embedded mode of the database +engine.

 Modified: db/derby/docs/trunk/src/getstart/getstartderby.ditamap URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/getstartderby.ditamap?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/getstart/getstartderby.ditamap (original) +++ db/derby/docs/trunk/src/getstart/getstartderby.ditamap Mon Sep 11 17:41:23 2006 @@ -1,4 +1,5 @@ + -Scripts provided by Derby - provides -scripts in the /bin directory. Each script comes in two flavors, one -ending in .bat and one ending in .ksh. +Scripts included with Derby +The scripts +are located in the /bin directory. + +Derbyscriptsscriptsin +Derbydblook scriptin Derby +ij scriptin DerbysetEmbeddedCP +scriptin Derbysysinfo scriptin +DerbyNetworkServerControl scriptin +DerbysetNetworkClientCP scriptin +DerbystartNetworkServer scriptin +DerbystopNetworkServer scriptin +Derbyscriptsdblook +scriptsijscriptssetEmbeddedCP +scriptssysinfoscriptsNetworkServerControl +scriptssetNetworkClientCPscriptsstartNetworkServer +scriptsstopNetworkServer + -

Here is a complete listing:

    -
  • frameworks/embedded/bin/dblook

    Runs dblook.

    • -
  • frameworks/embedded/bin/ij

    Starts ij.

    • -
  • frameworks/embedded/bin/setEmbeddedCP

    Puts all the libraries +

    The complete list of scripts that are included with Derby are: +

      +
    • bin/dblook

      Runs the dblook tool.

      • +
    • bin/ij

      Starts the ij tool.

      • +
    • bin/NetworkServerControl

      Runs NetworkServerControl.

      • +
    • bin/setEmbeddedCP

      Puts all of the libraries for an embedded environment in the classpath.

      • -
    • frameworks/embedded/bin/sysinfo

      Runs sysinfo.

      • -
    • frameworks/NetworkServer/bin/dblook

      Runs dblook in a Network -Server client context.

      • -
    • frameworks/NetworkServer/bin/ij

      Runs ij in a Network Server -client context.

      • -
    • frameworks/NetworkServer/bin/NetworkServerControl

      Runs NetworkServerControl.

      • -
    • frameworks/NetworkServer/bin/setNetworkClientCP

      Puts the libraries -needed to connect to Network -Server into the classpath.

      • -
    • frameworks/NetworkServer/bin/setNetworkServerCP

      Puts the libraries -needed for Network -Server into the classpath.

      • -
    • frameworks/NetworkServer/bin/startNetworkServer

      Starts the Network -Server on the local machine.

      • -
    • frameworks/NetworkServer/bin/stopNetworkServer

      Stops the Network -Server on the local machine.

      • -
    • frameworks/NetworkServer/bin/sysinfo

      Gets the system information -from a running Network -Server.

      • +
    • bin/setNetworkClientCP

      Puts the libraries needed to connect +to the Network Server +into the classpath.

      • +
    • bin/setNetworkServerCP

      Puts the libraries needed to start the Network Server into the +classpath.

      • +
    • bin/startNetworkServer

      Starts the Network Server on the local +machine.

      • +
    • bin/stopNetworkServer

      Stops the Network Server on the local +machine.

      • +
    • bin/sysinfo

      Runs the sysinfo tool.

    Modified: db/derby/docs/trunk/src/getstart/tgs26250.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgs26250.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/getstart/tgs26250.dita (original) +++ db/derby/docs/trunk/src/getstart/tgs26250.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,5 @@ + - Set the classpath -The JVM needs to know the path of every class file needed by your -application. The classpath is a list of the class libraries needed by the -JVM and other Java applications to run your program. +Setting the classpath +The classpath is a list of the class libraries that are needed +by the JVM and other Java applications to run your program. The scripts that +are included with Derby set up their own classpath for running the tools. +However, to call the tools directly using Java and not using the scripts, +you need to manually set the CLASSPATH environment variable. -Classpathsetting +classpathsettingenvironment +variablesCLASSPATHscriptssetEmbeddedCP +scriptssetNetworkServerCPscriptssetNetworkClientCP +

    You can set the CLASSPATH environment variable in the operating system either temporarily, permanently, or at run time when you start your -Java application and the JVM. If you set the environment variable temporarily, -you must set it each time that you open a new command window.

    In most -development environments, it is best to set the operating system's CLASSPATH -environment variable temporarily. provides -some scripts to help you set your classpath this way; they are found in the -/frameworks/embedded/bin directory or the /frameworks/NetworkServer/bin directory. -To set the class path temporarily, run a script every time you open a new -command window.

    - -Set your CLASSPATH so that it includes the derby.jar and derbytools.jar -files.For example:set CLASSPATH=%%\lib\derby.jar; -%%\lib\derbytools.jar;%CLASSPATH% - -To manually run the sysinfo utility, enter the following in a command -window or shell: java org.apache.derby.tools.sysinfo - -To manually run the ij utility and connect to the database: - -Enter the following in a command window or shell: java org.apache.derby.tools.ij -ij> connect 'jdbc:derby:<dbname>;create=true';where <dbname> -is the name of the database you are connecting to. -To exit the ij utility, enter:ij> exit; - - - - -For more information on running the ij and sysinfo utilities, see -the +Java application and the JVM.

    In most development environments, it +is best to temporarily set the CLASSPATH environment variable in the command +line shell where you are entering commands. provides +several scripts in the /bin directory +to help you set your classpath quickly. These scripts are:

    +
    setEmbeddedCP
    +
    The setEmbeddedCP script adds the derby.jar and derbytools.jar +files to the classpath, when the database engine is used in embedded mode.
    +     +
    setNetworkServerCP
    +
    The setNetworkServerCP script adds the derby.jar and +derbynet.jar files to the classpath, so that you can start the network server.
    +     +
    setNetworkClientCP
    +
    The setNetworkClientCP script adds the derbyclient.jar +and derbytools.jar files to the classpath, so that you can access databases +using the network client.
    +

    To set the classpath temporarily, run the script that +is appropriate for your environment every time that you open a new command +window.

    To see the classpath that the script sets, issue the following +command after you run the script:

      +
    • On UNIX, use echo $CLASSPATH
      • +
    • On Windows, use echo %CLASSPATH%
      • +

    +For more information on running the ij and sysinfo utilities, +see the     Modified: db/derby/docs/trunk/src/getstart/tgsrunningij.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgsrunningij.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/getstart/tgsrunningij.dita (original) +++ db/derby/docs/trunk/src/getstart/tgsrunningij.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,5 @@ + Running ij -You can use the ij tool to connect to a database. +You can use the ij tool to connect to a database. + +Derbytools, ijij +toolrunning + -

    You must include the /bin directory in your PATH environment -variable to run ij.

     +

    You must add the /bin directory +in your PATH environment variable before you can run the ij tool.

     -You can run ij by typing the following command: ij -The ij script executes the ij program and sets up environment -variables like CLASSPATH. -To create a database with ij, type the following command: -ij> connect 'jdbc:derby:testdb;create=true'; -This command creates a database called testdb in the current directory, -populates the system tables, and connects to the database. You can then execute -any SQL statements from the ij command line. -When you are ready to leave ij, type: ij> exit; - +To start the ij tool, run the ij script +from the command line. For example:ij +The ij script starts the ij tool +and sets up the environment variables like CLASSPATH. +To create a database with the ij tool, type +the following command:ij> connect 'jdbc:derby:testdb;create=true'; +This command creates a database called testdb in +the current directory, populates the system tables, and connects to the database. +You can then run any SQL statements from the ij command +line. +When you are ready to leave the ij tool, type: +ij> exit; See the for -more information on running ij. +more information about ij.     Modified: db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita (original) +++ db/derby/docs/trunk/src/getstart/tgssetupjavaenvir.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,5 @@ + - Setting up your Java environment -You need to set your PATH environment variable so the JVM and Java -applications run correctly. This is extremely important for the success of -your installation because the PATH variable enables your operating system -to find the appropriate programs from any directory. +Setting up your environment +You need to set several environment variables so that the scripts +that are included with the bin distribution +run correctly. -PATHsetting +Derbyenvironment setup +environment variablesDERBY_HOME +environment variablesJAVA_HOME +environment variablesDERBY_HOME +environment variablesPATHDERBY_HOMEenvironment +variable, settingJAVA_HOMEenvironment +variable, settingPATHenvironment +variable, setting -

    If you have more than one JVM installed, the JVM you want to -use must appear before any of the others in the PATH variable.

    To check -the PATH environment variable:

     +

    To set the environment variables:

     -In a command window, type the following: java -version -If the path is set correctly, you will see a printout telling -you the version of your JVM. -If the command does not return the correct version of your JVM, -set the PATH variable by adding the bin subdirectory of the -JVM directory to the beginning of the path.For example, if -the directory is C:\JDK1.4, add C:\JDK1.4\bin to -the beginning of the path. -Repeat step 1 to make sure the PATH environment variable is set -correctly. +Set the environment +variable to the location where you extracted the bin +distribution.For example, if you installed in +the c:\ directory, +use the following command to set the environment +variable: set =c:\ + +Set the JAVA_HOME environment variable. The JAVA_HOME environment +variable is used by the scripts to locate the JVM and Java applications. + +Operating SystemCommand + +UNIXexport JAVA_HOME=/usr/j2se + +Windowsset JAVA_HOME=C:\Program +Files\Java\j2se1.4.2_05 + + +Add the /bin directory +to the PATH environment variable so that you can run the scripts +from any directory. + +Operating SystemCommand + +UNIXexport PATH="$/bin:$PATH" + +Windowsset PATH=%\bin;%PATH% + + +When the environment +variable is set in the PATH environment variable, you can use shortened commands +to start the tools. + +Verify that the DERBY_HOME and the JAVA_HOME environment variables +are set correctly, and that the $DERBY_HOME/bin directory is added to the +PATH environment variable. Use the following command to check +the settings: sysinfo If the +environment variables are set correctly, the sysinfo command displays information +about your JVM and the version of Derby you have installed. + +For more information on the scripts included in the bin distribution, see .     Modified: db/derby/docs/trunk/src/pt_BR/adminguide/adminconrefs.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/pt_BR/adminguide/adminconrefs.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/pt_BR/adminguide/adminconrefs.dita (original) +++ db/derby/docs/trunk/src/pt_BR/adminguide/adminconrefs.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,7 @@ + + - - Entidades específicas do produto -

    Convenção para nomes: -abb (abreviatura do produto) -seguida por l (versão longa) ou -s (versão curta), seguida por t -se a referência for pré-marcada por marca registrada.

    +

    Convenção para nomes: abb (abreviatura +do produto) seguida por l (versão longa) ou s (versão +curta), seguida por t se a referência for pré-marcada +por marca registrada.

    Derby

    Apache Derby

    Derby_10

    -

    DERBY_INSTALL

    +

    DERBY_HOME

    derby

         @@ -43,10 +42,9 @@ Publicações -

    Convenção para nomes: -citABB, onde -cit é o indicador que o conref é para o título da -publicação e ABB é a abreviatura da publicação +

    Convenção para nomes: citABB, +onde cit é o indicador que o conref é para o +título da publicação e ABB é a abreviatura da publicação (digamos, 2-6 caracteres).

    Não é possível utilizar a marca cite "correta" do DITA porque o empacotador de IDD não pode tratá-la.

    Modified: db/derby/docs/trunk/src/pt_BR/getstart/gsconrefs.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/pt_BR/getstart/gsconrefs.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/pt_BR/getstart/gsconrefs.dita (original) +++ db/derby/docs/trunk/src/pt_BR/getstart/gsconrefs.dita Mon Sep 11 17:41:23 2006 @@ -1,7 +1,7 @@ + - - - Entidades específicas do produto -

    Convenção para nomes: -abb (abreviatura do produto) -seguida por l (versão longa) ou -s (versão curta), seguida por t -se a referência for pré-marcada por marca registrada.

    +

    Convenção para nomes: abb (abreviatura +do produto) seguida por l (versão longa) ou s (versão +curta), seguida por t se a referência for pré-marcada +por marca registrada.

    Derby

    Apache Derby

    Derby_10

    -

    DERBY_INSTALL

    +

    DERBY_HOME

    derby

         @@ -43,10 +42,9 @@ Publicações -

    Convenção para nomes: -citABB, onde -cit é o indicador que o conref é para o título da -publicação e ABB é a abreviatura da publicação +

    Convenção para nomes: citABB, +onde cit é o indicador que o conref é para o +título da publicação e ABB é a abreviatura da publicação (digamos, 2-6 caracteres).

    Não é possível utilizar a marca cite "correta" do DITA porque o empacotador de IDD não pode tratá-la.

    @@ -59,4 +57,3 @@     - Modified: db/derby/docs/trunk/src/ref/refconrefs.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/refconrefs.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/ref/refconrefs.dita (original) +++ db/derby/docs/trunk/src/ref/refconrefs.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,7 @@ + + - - Product specific entities @@ -29,7 +29,7 @@

    Derby

    Apache Derby

    Derby_10

    -

    DERBY_INSTALL

    +

    DERBY_HOME

    derby

         @@ -56,4 +56,3 @@     - Modified: db/derby/docs/trunk/src/tuning/tunconrefs.dita URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/tuning/tunconrefs.dita?view=diff&rev=442401&r1=442400&r2=442401 ============================================================================== --- db/derby/docs/trunk/src/tuning/tunconrefs.dita (original) +++ db/derby/docs/trunk/src/tuning/tunconrefs.dita Mon Sep 11 17:41:23 2006 @@ -1,4 +1,7 @@ + + - - Product specific entities @@ -29,7 +29,7 @@

    Derby

    Apache Derby

    Derby_10

    -

    DERBY_INSTALL

    +

    DERBY_HOME

    derby

     @@ -56,4 +56,3 @@     -