openerp-chinese-team team mailing list archive
-
openerp-chinese-team team
-
Mailing list archive
-
Message #00187
[Merge] lp:~openerp-chinese-team/openobject-doc/Chinese-init into lp:~openerp-community/openobject-doc/6.1
Joshua Jan(SHINEIT) has proposed merging lp:~openerp-chinese-team/openobject-doc/Chinese-init into lp:~openerp-community/openobject-doc/6.1.
Requested reviews:
OpenERP Community (openerp-community)
For more details, see:
https://code.launchpad.net/~openerp-chinese-team/openobject-doc/Chinese-init/+merge/137749
Hello expert,
This is the document initialization in Chinese language. I hope it could be merged.
Thank you very much.
Joshua
--
The attached diff has been truncated due to its size.
https://code.launchpad.net/~openerp-chinese-team/openobject-doc/Chinese-init/+merge/137749
Your team Open ERP Chinese is subscribed to branch lp:~openerp-chinese-team/openobject-doc/Chinese-init.
=== added directory 'i18n/zh_CN'
=== added file 'i18n/zh_CN/Makefile'
--- i18n/zh_CN/Makefile 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/Makefile 2012-12-04 03:46:24 +0000
@@ -0,0 +1,107 @@
+# Makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS =
+SPHINXBUILD = sphinx-build
+#PAPER = a4
+PAPER =
+BUILDDIR = build
+
+# Internal variables.
+PAPEROPT_a4 = -D latex_paper_size=a4
+PAPEROPT_letter = -D latex_paper_size=letter
+ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
+
+# I18N stuff:
+BUILDI18N = ./build_i18n.py
+LANG =
+
+.PHONY: help clean html web pickle htmlhelp latex changes linkcheck i18n
+
+help:
+ @echo "Please use \`make <target>' where <target> is one of"
+ @echo " html to make standalone HTML files"
+ @echo " pickle to make pickle files"
+ @echo " json to make JSON files"
+ @echo " htmlhelp to make HTML files and a HTML help project"
+ @echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
+ @echo " changes to make an overview over all changed/added/deprecated items"
+ @echo " linkcheck to check all external links for integrity"
+ @echo " i18n LANG=<your_lang> to convert untranslated sources to translatable templates"
+
+clean:
+ -rm -rf $(BUILDDIR)/*
+
+html:
+ mkdir -p build/html build/doctrees
+ $(SPHINXBUILD) -b html $(ALLSPHINXOPTS) build/html
+ ./copy_images.sh
+ cp ./index.php build/html
+ @echo
+ @echo "Build finished. The HTML pages are in build/html."
+
+pickle:
+ mkdir -p build/pickle build/doctrees
+ $(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) build/pickle
+ @echo
+ @echo "Build finished; now you can process the pickle files."
+
+web: pickle
+
+json:
+ mkdir -p build/json build/doctrees
+ $(SPHINXBUILD) -b json $(ALLSPHINXOPTS) build/json
+ @echo
+ @echo "Build finished; now you can process the JSON files."
+
+htmlhelp:
+ mkdir -p build/htmlhelp build/doctrees
+ $(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) build/htmlhelp
+ @echo
+ @echo "Build finished; now you can run HTML Help Workshop with the" \
+ ".hhp project file in build/htmlhelp."
+
+latex:
+ mkdir -p build/latex build/doctrees
+ $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) build/latex
+ cp texfiles/howto.cls build/latex
+ @echo
+ @echo "Build finished; the LaTeX files are in build/latex."
+ @echo "Run \`make all-pdf' or \`make all-ps' in that directory to" \
+
+latexpdf:
+ $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+ @echo "Running LaTeX files through pdflatex..."
+ make -C $(BUILDDIR)/latex all-pdf
+ @echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+text:
+ $(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
+ @echo
+ @echo "Build finished. The text files are in $(BUILDDIR)/text."
+
+man:
+ $(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
+ @echo
+ @echo "Build finished. The manual pages are in $(BUILDDIR)/man."
+
+changes:
+ mkdir -p build/changes build/doctrees
+ $(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) build/changes
+ @echo
+ @echo "The overview file is in build/changes."
+
+linkcheck:
+ mkdir -p build/linkcheck build/doctrees
+ $(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) build/linkcheck
+ @echo
+ @echo "Link check complete; look for any errors in the above output " \
+ "or in build/linkcheck/output.txt."
+
+i18n:
+ $(BUILDI18N) ${LANG}
+
+cleani18n:
+ -rm -rf i18n/*/build/*
+
=== added directory 'i18n/zh_CN/build'
=== added file 'i18n/zh_CN/copy_images.sh'
--- i18n/zh_CN/copy_images.sh 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/copy_images.sh 2012-12-04 03:46:24 +0000
@@ -0,0 +1,45 @@
+#!/bin/sh
+
+SRC_IMAGE_DIR=source/features/images
+DEST_IMAGE_NORMAL_DIR=build/html/images
+DEST_IMAGE_SMALL_DIR=build/html/images_small
+
+VERBOSE=0
+
+echo 'copying images'
+
+# create directory if it does not exists:
+if [ ! -d $DEST_IMAGE_SMALL_DIR ]; then
+ if [ $VERBOSE = 1 ]; then
+ echo creating directory: $DEST_IMAGE_SMALL_DIR
+ else
+ echo .'\c'
+ fi
+ mkdir -p $DEST_IMAGE_SMALL_DIR || exit
+fi
+
+if [ ! -d $DEST_IMAGE_NORMAL_DIR ]; then
+ if [ $VERBOSE = 1 ]; then
+ echo creating directory: $DEST_IMAGE_NORMAL_DIR
+ else
+ echo .'\c'
+ fi
+ mkdir -p $DEST_IMAGE_NORMAL_DIR || exit
+fi
+
+for f in ${SRC_IMAGE_DIR}/*.png; do
+ baseimage=$(basename $f)
+ if [ $VERBOSE = 1 ]; then
+ echo converting image $f in ${DEST_IMAGE_SMALL_DIR}/${baseimage}
+ else
+ echo .'\c'
+ fi
+ #convert -geometry 350x350 $f ${DEST_IMAGE_SMALL_DIR}/${baseimage} || exit
+ if [ $VERBOSE = 1 ]; then
+ echo copying image $f in ${DEST_IMAGE_NORMAL_DIR}
+ else
+ echo .'\c'
+ fi
+ cp -f $f $DEST_IMAGE_NORMAL_DIR || exit
+done;
+
=== added file 'i18n/zh_CN/index.php'
--- i18n/zh_CN/index.php 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/index.php 2012-12-04 03:46:24 +0000
@@ -0,0 +1,319 @@
+<?php
+$mapping = Array(
+ "account.account" => "book/3/3_9/chart_of_accounts.html#creating-a-chart-of-accounts",
+ "account.account.template" => "technical_guide/account.html#object-templates-for-accounts-account-account-template",
+ "account.account.type" => "book/3/3_9/chart_of_accounts.html#creating-a-chart-of-accounts",
+ "account.analytic.account" => "book/4/4_10_Accounts/4_10_Accounts_place.html",
+ "account.analytic.default" => "technical_guide/account_analytic_default.html#object-analytic-distributions-account-analytic-default",
+ "account.analytic.journal" => "book/4/4_10_Accounts/4_10_Accounts_place.html",
+ "account.analytic.line" => "book/4/4_10_Accounts/4_10_Accounts_place.html",
+ "account.analytic.plan" => "technical_guide/account_analytic_plans.html#object-analytic-plans-account-analytic-plan",
+ "account.analytic.plan.instance" => "technical_guide/account_analytic_plans.html#object-analytic-plan-instance-account-analytic-plan-instance",
+ "account.analytic.plan.instance.line" =>"technical_guide/account_analytic_plans.html#object-analytic-instance-line-account-analytic-plan-instance-line",
+ "account.analytic.plan.line" =>"technical_guide/account_analytic_plans.html#object-analytic-plan-lines-account-analytic-plan-line",
+ "account.asset.asset" =>"technical_guide/account_asset.html",
+ "account.asset.board" => "technical_guide/account_asset.html#object-asset-board-account-asset-board",
+ "account.asset.category" =>"technical_guide/account_asset.html#object-asset-category-account-asset-category",
+ "account.asset.property" => "technical_guide/account_asset.html#object-asset-property-account-asset-property",
+ "account.asset.property.history" =>"technical_guide/account_asset.html#object-asset-history-account-asset-property-history",
+ "account.bank.accounts.wizard" => "technical_guide/account.html#object-account-bank-accounts-wizard-account-bank-accounts-wizard",
+ "account.bank.statement" => "book/3/3_7/accounting_entries.html",
+ "account.bank.statement.line" => "book/3/3_7/accounting_entries.html",
+ "account.bank.statement.reconcile" => "book/3/3_7/accounting_entries.html",
+ "account.bank.statement.reconcile.line" => "book/3/3_7/accounting_entries.html",
+ "account.budget.post" => "book/3/3_8/company_financial_analysis.html#good-management-budgeting",
+ "account.budget.post.dotation" => "technical_guide/account_budget.html#object-budget-dotation-account-budget-post-dotation",
+ "account.chart.template" => "technical_guide/account.html#object-templates-for-account-chart-account-chart-template",
+ "account.config.wizard" => "technical_guide/account.html#object-account-config-wizard-account-config-wizard",
+ "account.fiscal.position" => "technical_guide/account.html#object-fiscal-position-account-fiscal-position",
+ "account.fiscal.position.account" => "technical_guide/account.html#object-fiscal-position-accounts-mapping-account-fiscal-position-account",
+ "account.fiscal.position.account.template" => "technical_guide/account.html#object-fiscal-position-template-account-mapping-account-fiscal-position-account-template",
+ "account.fiscal.position.tax" => "technical_guide/account.html#object-fiscal-position-taxes-mapping-account-fiscal-position-tax",
+ "account.fiscal.position.tax.template" => "technical_guide/account.html#object-fiscal-position-template-tax-mapping-account-fiscal-position-tax-template",
+ "account.fiscal.position.template" => "technical_guide/account.html#object-template-for-fiscal-position-account-fiscal-position-template",
+ "account.fiscalyear" => "book/3/3_9/periods_and_fiscal_years.html",
+ "account.invoice" => "book/3/3_7/invoicing.html",
+ "account.invoice.line" => "book/3/3_7/invoicing.html",
+ "account.invoice.tax" => "book/3/3_7/invoicing.html",
+ "account.journal" => "book/3/3_9/journals.html",
+ "account.journal.column" => "technical_guide/account.html#object-journal-column-account-journal-column",
+ "account.journal.period" => "technical_guide/account.html#object-journal-period-account-journal-period",
+ "account.journal.simulation" => "technical_guide/account_simulation.html#object-simulation-level-account-journal-simulation",
+ "account.journal.view" => "technical_guide/account.html#object-journal-view-account-journal-view",
+ "account.model" => "technical_guide/account.html#object-account-model-account-model",
+ "account.model.line" => "technical_guide/account.html#object-account-model-entries-account-model-linel",
+ "account.move" => "technical_guide/account.html#object-account-entry-account-move",
+ "account.move.line" => "technical_guide/account.html#object-entry-lines-account-move-line",
+ "account.move.reconcile" => "technical_guide/account.html#object-account-reconciliation-account-move-reconcile",
+ "account.payment.term" => "book/3/3_9/payment_terms.html",
+ "account.payment.term.line" => "book/3/3_9/payment_terms.html",
+ "account.period" => "book/3/3_9/periods_and_fiscal_years.html",
+ "account.report.history" => "book/4/4_10_Accounts/4_10_Accounts_fin_ana.html",
+ "account.report.report" => "book/4/4_10_Accounts/4_10_Accounts_fin_ana.html",
+ "account.sequence.fiscalyear" => "technical_guide/account.html#object-account-sequence-fiscalyear-account-sequence-fiscalyear",
+ "account.subscription" => "technical_guide/account.html#object-account-subscription-account-subscription",
+ "account.subscription.line" => "technical_guide/account.html#object-account-subscription-line-account-subscription-line",
+ "account.tax" => "book/3/3_8/statutory_taxes.html",
+ "account.tax.code" => "book/3/3_8/statutory_taxes.html",
+ "account.tax.code.template" => "book/3/3_8/statutory_taxes.html",
+ "account.tax.template" => "book/3/3_8/statutory_taxes.html",
+ "account_analytic_analysis.summary.month" => "book/4/4_10_Accounts/4_10_Accounts_fin_ana.html",
+ "account_analytic_analysis.summary.user" => "book/4/4_10_Accounts/4_10_Accounts_fin_ana.html",
+ "account_followup.followup" => "book/3/3_8/managing_accounts.html#multi-step-follow-ups",
+ "account_followup.followup.line" => "book/3/3_8/managing_accounts.html#multi-step-follow-ups",
+ "account_followup.stat" => "book/3/3_8/managing_accounts.html#multi-step-follow-ups",
+ "board.board" => "book/3/3_8/company_financial_analysis.html#the-accounting-dashboard",
+ "board.board.line" => "book/3/3_8/company_financial_analysis.html#the-accounting-dashboard",
+ "board.note" => "book/3/3_8/company_financial_analysis.html#the-accounting-dashboard",
+ "board.note.type" => "book/3/3_8/company_financial_analysis.html#the-accounting-dashboard",
+ "config.compute.remaining" => "technical_guide/project.html#object-config-compute-remaining-config-compute-remaining",
+ "crm.case" => "book/2/2_5_CRM/2_5_CRM_case.html",
+ "crm.case.categ" => "book/2/2_5_CRM/2_5_CRM_case.html#categories",
+ "crm.case.category2" => "book/2/2_5_CRM/2_5_CRM_case.html",
+ "crm.case.history" => "book/2/2_5_CRM/2_5_CRM_case.html#using-cases",
+ "crm.case.log" => "technical_guide/crm.html#object-case-communication-history-crm-case-log",
+ "crm.case.rule" => "book/2/2_5_CRM/2_5_CRM_case.html#automating-actions-using-rules",
+ "crm.case.section" => "book/2/2_5_CRM/2_5_CRM_case.html#sections",
+ "crm.case.stage" => "technical_guide/crm_configuration.html#object-stage-of-case-crm-case-stage",
+ "crm.menu.config_wizard" => "book/2/2_5_CRM/2_5_CRM_case.html#menu",
+ "crm.segmentation" => "book/2/2_5_CRM/2_5_CRM_profiling.html#using-profiles-effectively",
+ "crm.segmentation.line" =>"book/2/2_5_CRM/2_5_CRM_profiling.html#using-profiles-effectively",
+ "crossovered.budget" => "book/3/3_8/company_financial_analysis.html#good-management-budgeting",
+ "crossovered.budget.lines" => "book/3/3_8/company_financial_analysis.html#good-management-budgeting",
+ "delivery.carrier" => "book/6/6_16_Sales/6_16_Sales_carriers.html#management-of-carriers",
+ "delivery.grid" => "book/6/6_16_Sales/6_16_Sales_carriers.html#tariff-grids",
+ "delivery.grid.line" =>"book/6/6_16_Sales/6_16_Sales_carriers.html#tariff-grids",
+ "document.configuration.wizard"=>"book/7/7_19_Documents/7_19_Documents_OpenERP.html#installation",
+ "document.directory" => "book/7/7_19_Documents/7_19_Documents_mapping.html",
+ "document.directory.content" => "book/7/7_19_Documents/7_19_Documents_mapping.html",
+ "document.directory.content.type" =>"book/7/7_19_Documents/7_19_Documents_mapping.html",
+ "edi.log" => "technical_guide/edi.html#object-edi-log-edi-log",
+ "edi.log.line" =>"technical_guide/edi.html#object-edi-log-line-edi-log-line",
+ "event.event" =>"technical_guide/event.html#object-event-event-event",
+ "event.registration" =>"technical_guide/event.html#object-event-registration-event-registration",
+ "event.type" => "technical_guide/event.html#object-event-type-event-type",
+ "fiscalyear.seq" => "technical_guide/account.html#object-maintains-invoice-sequences-with-fiscal-year-fiscalyear-seq",
+ "hr.action.reason" => "technical_guide/hr_attendance.html#object-action-reason-hr-action-reason",
+ "hr.analytic.timesheet" => "book/4/4_11_HR/4_11_HR_timesheet.html",
+ "hr.attendance" => "book/4/4_11_HR/4_11_HR_timesheet.html#entering-timesheet-data",
+ "hr.department" => "book/4/4_11_HR/4_11_HR_timesheet.html#managing-by-department",
+ "hr.employee" => "book/4/4_11_HR/4_11_HR_timesheet.html#employee-configuration",
+ "hr.employee.category" => "book/4/4_11_HR/4_11_HR_timesheet.html#employee-configuration",
+ "hr.expense.expense" => "book/4/4_12_Services/4_12_Services_treatment.html",
+ "hr.expense.line" => "book/4/4_12_Services/4_12_Services_treatment.html",
+ "hr.timesheet" => "book/4/4_11_HR/4_11_HR_timesheet.html",
+ "hr.timesheet.group" => "book/4/4_11_HR/4_11_HR_timesheet.html",
+ "hr_timesheet_invoice.factor" => "book/4/4_11_HR/4_11_HR_timesheet.html#evaluation-of-service-costs",
+ "hr_timesheet_sheet.sheet" => "book/4/4_11_HR/4_11_HR_timesheet.html#entering-timesheet-data",
+ "hr_timesheet_sheet.sheet.account" =>"book/4/4_11_HR/4_11_HR_timesheet.html#entering-timesheet-data",
+ "hr_timesheet_sheet.sheet.day" => "book/4/4_11_HR/4_11_HR_timesheet.html#managing-by-department",
+ "ir.actions.act_window" => "/technical_guide/base.html#object-ir-actions-act-window",
+ "ir.actions.act_window.view" => "/technical_guide/base.html#object-ir-actions-act-window-view",
+ "ir.actions.act_window_close" => "/technical_guide/base.html#object-ir-actions-act-window-close",
+ "ir.actions.actions" => "/technical_guide/base.html#object-ir-actions-actions",
+ "ir.actions.configuration.wizard" => "/technical_guide/base.html#object-ir-actions-configuration-wizard",
+ "ir.actions.report.custom" => "/technical_guide/base.html#object-ir-actions-configuration-wizard",
+ "ir.actions.report.xml" =>"/technical_guide/base.html#object-ir-actions-report-xml",
+ "ir.actions.server" => "/technical_guide/base.html#object-ir-actions-server",
+ "ir.actions.todo" => "/technical_guide/base.html#object-ir-actions-todo",
+ "ir.actions.url" => "/technical_guide/base.html#object-ir-actions-url",
+ "ir.actions.wizard" => "/technical_guide/base.html#object-ir-actions-wizard",
+ "ir.attachment" =>"/technical_guide/base.html#object-ir-attachment",
+ "ir.cron" => "/technical_guide/base.html#object-ir-cron",
+ "ir.default" => "/technical_guide/base.html#object-ir-default",
+ "ir.exports" => "/technical_guide/base.html#object-ir-exports",
+ "ir.exports.line" =>"/technical_guide/base.html#object-ir-exports-line",
+ "ir.model" => "/technical_guide/base.html#objects",
+ "ir.model.access" => "/technical_guide/base.html#object-ir-model-access",
+ "ir.model.config" => "/technical_guide/base.html#object-ir-model-config",
+ "ir.model.data" => "/technical_guide/base.html#object-ir-model-data",
+ "ir.model.fields" => "/technical_guide/base.html#object-fields-ir-model-fields",
+ "ir.model.grid" => "/technical_guide/base.html#object-objects-security-grid-ir-model-grid",
+ "ir.module.category" =>"/technical_guide/base.html#object-module-category",
+ "ir.module.module" => "/technical_guide/base.html#object-module",
+ "ir.module.module.dependency" => "/technical_guide/base.html#object-module-dependency",
+ "ir.module.repository" => "/technical_guide/base.html#object-module-repository",
+ "ir.property" => "/technical_guide/base.html#object-ir-property",
+ "ir.report.custom" => "/technical_guide/base.html#object-ir-report-custom",
+ "ir.report.custom.fields" =>"/technical_guide/base.html#object-ir-report-custom-fields",
+ "ir.rule" =>"/technical_guide/base.html#object-ir-rule",
+ "ir.rule.group" =>"/technical_guide/base.html#object-ir-rule-group",
+ "ir.sequence" =>"/technical_guide/base.html#object-ir-sequence",
+ "ir.sequence.type" =>"/technical_guide/base.html#object-ir-sequence-type",
+ "ir.server.object.lines" => "/technical_guide/base.html#object-ir-server-object-lines",
+ "ir.translation" => "/technical_guide/base.html#object-ir-translation",
+ "ir.ui.menu" => "/technical_guide/base.html#object-ir-ui-menu",
+ "ir.ui.view" =>"/technical_guide/base.html#object-ir-ui-view",
+ "ir.ui.view.custom" => "/technical_guide/base.html#object-ir-ui-view-custom",
+ "ir.ui.view_sc" => "/technical_guide/base.html#object-ir-ui-view-sc",
+ "ir.values" => "/technical_guide/base.html#object-ir-values",
+ "maintenance.contract" => "book/8/8_21_Implem/8_21_Implem_support.html",
+ "maintenance.contract.module" => "/technical_guide/base.html#object-maintenance-contract-modules",
+ "maintenance.contract.wizard" => "/technical_guide/base.html#object-maintenance-contract-wizard",
+ "membership.membership_line" => "/features/membership.html",
+ "mrp.bom" => "book/5/5_15_Manufacturing/5_15_Manufacturing_production.html#bills-of-materials",
+ "mrp.bom.revision" => "book/5/5_15_Manufacturing/5_15_Manufacturing_production.html#bills-of-materials",
+ "mrp.procurement" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html#manual-procurement",
+ "mrp.production" => "book/5/5_15_Manufacturing/index.html",
+ "mrp.production.product.line" => "book/5/5_15_Manufacturing/index.html",
+ "mrp.production.workcenter.line" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html#workcenters",
+ "mrp.property" => "book/5/5_15_Manufacturing/5_15_Manufacturing_production.html#configurable-bills-of-materials",
+ "mrp.property.group" => "book/5/5_15_Manufacturing/5_15_Manufacturing_production.html#configurable-bills-of-materials",
+ "mrp.repair" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html",
+ "mrp.repair.fee" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html",
+ "mrp.repair.line" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html",
+ "mrp.routing" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html#routing",
+ "mrp.routing.workcenter" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html#workcenters",
+ "mrp.subproduct" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html",
+ "mrp.workcenter" => "book/5/5_15_Manufacturing/5_15_Manufacturing_lead.html#workcenters",
+ "payment.line" => "book/3/3_7/accounting_entries.html#management-of-payments",
+ "payment.mode" => "book/3/3_7/accounting_entries.html#management-of-payments",
+ "payment.order" => "book/3/3_7/accounting_entries.html#management-of-payments",
+ "payment.type" => "book/3/3_7/accounting_entries.html#management-of-payments",
+ "pos.config.journal" => "/features/point_of_sales.html",
+ "pos.order" =>"/features/point_of_sales.html",
+ "pos.order.line" => "/features/point_of_sales.html",
+ "pos.payment" => "/features/point_of_sales.html",
+ "pricelist.partnerinfo" => "technical_guide/product.html#object-pricelist-partnerinfo-pricelist-partnerinfo",
+ "process.condition" => "book/7/7_18_Process/index.html",
+ "process.node" => "book/7/7_18_Process/index.html",
+ "process.process" => "book/7/7_18_Process/index.html",
+ "process.transition" => "book/7/7_18_Process/index.html",
+ "process.transition.action" => "book/7/7_18_Process/index.html",
+ "product.category" => "book/1/1_3_Real_Case/1_3_Real_Case_db_setup.html#creating-products-and-their-categories",
+ "product.packaging" => "book/6/6_16_Sales/6_16_Sales_packing.html#management-of-packaging",
+ "product.price.type" => "book/6/6_16_Sales/6_16_Sales_pricing.html#different-bases-for-price-calculationl",
+ "product.pricelist" => "book/4/4_12_Services/4_12_Services_contract.html",
+ "product.pricelist.item" => "book/4/4_12_Services/4_12_Services_contract.html",
+ "product.pricelist.type" => "book/4/4_12_Services/4_12_Services_contract.html",
+ "product.pricelist.version" =>"book/4/4_12_Services/4_12_Services_contract.html",
+ "product.product" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_openerp.html#products",
+ "product.supplierinfo" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_openerp.html#products",
+ "product.template" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_openerp.html#products",
+ "product.ul" =>"book/1/1_2_Guided_Tour/1_2_Guided_Tour_openerp.html#products",
+ "product.uom" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_openerp.html#products",
+ "product.uom.categ" =>"book/1/1_2_Guided_Tour/1_2_Guided_Tour_openerp.html#products",
+ "profile.accounting.config.install_modules_wizard" => "index.html",
+ "profile.association.config.install_modules_wizard" => "index.html",
+ "profile.manufacturing.config.install_modules_wizard" => "index.html",
+ "profile.service.config.install_modules_wizard" => "index.html",
+ "project.gtd.context" => "book/4/4_13_Projects/4_13_Projects_productivity.html#context",
+ "project.gtd.timebox" => "book/4/4_13_Projects/4_13_Projects_productivity.html#timebox",
+ "project.project" => "book/4/4_13_Projects/4_13_Projects_management.html",
+ "project.task" => "book/4/4_13_Projects/4_13_Projects_management.html#managing-tasks",
+ "project.task.type" => "book/4/4_13_Projects/4_13_Projects_management.html#managing-tasks",
+ "project.task.work" => "book/4/4_13_Projects/4_13_Projects_management.html#managing-tasks",
+ "purchase.order" => "book/6/6_17_Purchases/index.html",
+ "purchase.order.line" => "book/6/6_17_Purchases/index.html",
+ "report.account.analytic.line.to.invoice" => "/technical_guide/report_analytic_line.html",
+ "report.account.invoice" =>"/technical_guide/sale_margin.html",
+ "report.account.invoice.category" =>"/technical_guide/sale_margin.html",
+ "report.account.invoice.partner" => "/technical_guide/sale_margin.html",
+ "report.account.invoice.partner.product" => "/technical_guide/sale_margin.html",
+ "report.account.invoice.product" => "/technical_guide/sale_margin.html",
+ "report.account.receivable" => "/technical_guide/report_account.html",
+ "report.analytic.account.close" => "report.analytic.account.close",
+ "report.crm.case.categ" => "/technical_guide/board_crm_configuration.html",
+ "report.crm.case.section.categ.categ2" => "/technical_guide/crm_configuration.html",
+ "report.crm.case.section.categ.stage" => "/technical_guide/crm_configuration.html",
+ "report.crm.case.section.categ2" => "/technical_guide/crm_configuration.html",
+ "report.crm.case.section.stage" => "/technical_guide/crm_configuration.html",
+ "report.crm.case.user" => "technical_guide/report_crm.html",
+ "report.document.file" =>"book/7/7_19_Documents/7_19_Documents_searching.html#working-with-users-changes",
+ "report.document.user" => "book/7/7_19_Documents/7_19_Documents_searching.html#working-with-users-changes",
+ "report.document.wall" => "book/7/7_19_Documents/7_19_Documents_searching.html#working-with-users-changes",
+ "report.event.registration" => "/technical_guide/event.html",
+ "report.event.type.registration" => "/technical_guide/event.html",
+ "report.files.partner" => "book/7/7_19_Documents/7_19_Documents_searching.html#working-with-users-changes",
+ "report.hr.timesheet.invoice.journal" => "/technical_guide/account.html",
+ "report.mrp.inout" => "/technical_guide/report_mrp.html",
+ "report.partner_member.year" => "/technical_guide/membership.html",
+ "report.partner_member.year_new" =>"/technical_guide/membership.html",
+ "report.stock.lines.date" => "/technical_guide/stock.html",
+ "report.task.user.pipeline.open" => "/technical_guide/report_task.html",
+ "report.transaction.pos" => "/technical_guide/point_of_sale.html",
+ "report.workcenter.load" => "/technical_guide/report_mrp.html",
+ "report_account_analytic.planning" => "/technical_guide/report_analytic_planning.html",
+ "report_account_analytic.planning.line" => "/technical_guide/report_analytic_planning.html",
+ "report_account_analytic.planning.stat" => "/technical_guide/report_analytic_planning.html",
+ "report_account_analytic.planning.stat.account" => "/technical_guide/report_analytic_planning.html",
+ "report_account_analytic.planning.stat.user" => "/technical_guide/report_analytic_planning.html",
+ "report_timesheet.account" => "/technical_guide/report_timesheet.html",
+ "report_timesheet.account.date" => "/technical_guide/report_timesheet.html",
+ "report_timesheet.invoice" => "/technical_guide/report_timesheet.html",
+ "report_timesheet.user" => "/technical_guide/report_timesheet.html",
+ "res.bank" => "/technical_guide/base.html#object-bank-res-bank",
+ "res.company" => "/technical_guide/base.html#object-res-company-res-company",
+ "res.config.view" => "/technical_guide/base.html#object-res-config-view-res-config-view",
+ "res.country" => "/technical_guide/base.html#object-country-res-country",
+ "res.country.state" =>"/technical_guide/base.html#object-country-state-res-country-state",
+ "res.currency" => "/technical_guide/base.html#object-currency-res-currency",
+ "res.currency.rate" => "/technical_guide/base.html#object-currency-rate-res-currency-rate",
+ "res.groups" => "book/8/8_20_Config/8_20_Config_accessRights.html#groups-and-users",
+ "res.lang" => "/technical_guide/base.html#object-languages-res-lang",
+ "res.partner" => "book/2/2_5_CRM/2_5_CRM_partners.html#partners",
+ "res.partner.address" => "book/1/1_3_Real_Case/1_3_Real_Case_db_setup.html#creating-partner-categories-partners-and-their-contacts",// "/technical_guide/base.html#object-partner-addresses",
+ "res.partner.bank" => "/technical_guide/base.html#object-bank-accounts",
+ "res.partner.bank.type" => "/technical_guide/base.html#object-bank-account-type",
+ "res.partner.bank.type.field" => "/technical_guide/base.html#object-bank-type-fields",
+ "res.partner.canal" => "/technical_guide/base.html#object-channels",
+ "res.partner.category" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.html#partner-categories",// "book/1/1_3_Real_Case/1_3_Real_Case_db_setup.html#creating-partner-categories-partners-and-their-contacts",
+ "res.partner.contact" => "book/2/2_5_CRM/2_5_CRM_partners.html#contacts",
+ "res.partner.event" => "/technical_guide/base.html#object-res-partner-event-res-partner-event",
+ "res.partner.event.type" => "/technical_guide/base.html#object-partner-events-res-partner-event-type",
+ "res.partner.function" => "book/2/2_5_CRM/2_5_CRM_partners.html#contacts",// "/technical_guide/base.html#object-function-of-the-contact",
+ "res.partner.job" => "/technical_guide/base_contact.html#object-contact-partner-function",
+ "res.partner.som" => "/technical_guide/base.html#object-res-partner-som",
+ "res.partner.title" => "book/2/2_5_CRM/2_5_CRM_partners.html#partners",
+ "res.payterm" => "book/3/3_9/payment_terms.html#payment-terms",
+ "res.request" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.html#requests-as-a-mechanism-for-internal-communication",
+ "res.request.history" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.html#requests-as-a-mechanism-for-internal-communication",
+ "res.request.link" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.html#requests-as-a-mechanism-for-internal-communication",
+ "res.roles" => "book/8/8_20_Config/8_20_Config_workflow.html#assigning-roles",
+ "res.users" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.html#configuring-users",
+ "sale.config.picking_policy" => "book/6/6_16_Sales/6_16_Sales_control.html#control-of-deliveries-and-invoicing",
+ "sale.order" => "book/6/6_16_Sales/6_16_Sales_quotations.html#sales-quotations",
+ "sale.order.line" => "book/6/6_16_Sales/6_16_Sales_quotations.html#entering-quotation-details",
+ "sale.shop" => "book/1/1_3_Real_Case/1_3_Real_Case_testing_wf.html#from-sales-proposal-to-sales-order",
+ "sale_journal.invoice.type" => "/technical_guide/sale_journal.html",
+ "sale_journal.invoice.type.stats" => "/technical_guide/sale_journal.html",
+ "sale_journal.picking.journal" => "/technical_guide/sale_journal.html",
+ "sale_journal.picking.stats" => "/technical_guide/sale_journal.html",
+ "sale_journal.sale.journal" => "/technical_guide/sale_journal.html",
+ "sale_journal.sale.stats" => "/technical_guide/sale_journal.html",
+ "stock.incoterms" => "/technical_guide/stock.html",
+ "stock.inventory" => "book/5/5_14_Stock/5_14_Stock_stocks.html#initial-inventory",
+ "stock.inventory.line" => "book/5/5_14_Stock/5_14_Stock_stocks.html#initial-inventory",
+ "stock.location" => "book/5/5_14_Stock /index.html#logistics-and-stock-management",
+ "stock.location.path" => "index.html",
+ "stock.move" => "book/5/5_14_Stock/5_14_Stock_lots.html#stock-moves",
+ "stock.picking" => "index.html",
+ "stock.picking.move.wizard" => "book/5/5_14_Stock/5_14_Stock_advanced.html#manual-data-entry-of-goods-receipt",
+ "stock.production.lot" => "book/5/5_15_Manufacturing/5_15_Manufacturing_production.html#traceability",
+ "stock.production.lot.revision" => "book/5/5_15_Manufacturing/5_15_Manufacturing_production.html#traceability",
+ "stock.report.prodlots" => "book/5/5_14_Stock/5_14_Stock_lots.html#traceability",
+ "stock.tracking" => "book/5/5_14_Stock/5_14_Stock_lots.html#traceability",
+ "stock.warehouse" => "book/5/5_14_Stock/5_14_Stock_warehouses.html#warehouses",
+ "stock.warehouse.orderpoint" => "book/5/5_14_Stock/5_14_Stock_warehouses.html#minimum-stock-rules",
+ "wiki.groups" => "/technical_guide/wiki.html#module-wiki",
+ "wiki.groups.link" => "technical_guide/wiki.html#module-wiki",
+ "wiki.wiki" => "/technical_guide/wiki.html#module-wiki",
+ "wiki.wiki.history" => "/technical_guide/wiki.html#module-wiki",
+ "wizard.ir.model.menu.create" => "index.html",
+ "wizard.ir.model.menu.create.line" => "index.html",
+ "wizard.module.lang.export" => "book/8/8_20_Config/8_20_Config_menu.html#translation-through-a-csv-file",
+ "wizard.module.update_translations" => "book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.html#installing-a-new-language",
+ "wizard.multi.charts.accounts" => "book/3/3_9/chart_of_accounts.html#creating-a-chart-of-accounts",
+ "wizard.wiki.history.show_diff" => "/technical_guide/wiki.html#module-wiki",
+ "workflow" => "book/8/8_20_Config/8_20_Config_workflow.html",
+ "workflow.activity" => "developer/3_9_Workflow_Business_Process/index.html#activity",
+ "workflow.instance" => "index.html",
+ "workflow.transition" => "developer/3_9_Workflow_Business_Process/index.html#transition",
+ "workflow.triggers" => "developer/3_9_Workflow_Business_Process/index.html",
+ "workflow.workitem" => "developer/3_9_Workflow_Business_Process/index.html",
+);
+if (array_key_exists('model', $_GET) && array_key_exists($_GET['model'], $mapping))
+ header('Location: http://doc.openerp.com/v6.1/'.$mapping[$_GET['model']] ) ;
+else
+ header('Location: http://doc.openerp.com/v6.1/index.html') ;
+?>
=== added directory 'i18n/zh_CN/source'
=== added directory 'i18n/zh_CN/source/.static'
=== added file 'i18n/zh_CN/source/.static/button-a-c.png'
Binary files i18n/zh_CN/source/.static/button-a-c.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/button-a-c.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/chevron.png'
Binary files i18n/zh_CN/source/.static/chevron.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/chevron.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/default.css'
--- i18n/zh_CN/source/.static/default.css 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/.static/default.css 2012-12-04 03:46:24 +0000
@@ -0,0 +1,1115 @@
+/**
+ * OpenERP Doc Design
+ */
+
+/* div.js-kit-comments { */
+/* border: 1px solid black; */
+/* background-color: #e6e6e6; */
+/* position: relative; */
+/* float: right; */
+/* padding: 2px; */
+/* top: -40px; */
+/* right: -10px; */
+/* width: 22%; */
+/* } */
+
+/* div.js-kit-comments a { */
+/* color: #444; */
+/* font-size: 10pt; */
+/* } */
+
+.js-poweredBy {
+ display: none;
+ visibility: hidden
+}
+
+#comments_control {
+ border: 1px solid #98DBCC;
+}
+
+td.search-exclude-tip {
+}
+
+td.search-exclude-tip span {
+ font-size: 8pt;
+ color: grey;
+ padding: 8px;
+}
+
+td.search-type {
+ vertical-align: top;
+}
+
+td.search-type span {
+ font-size: 8pt;
+ color: #333;
+}
+
+span.search-section-label{
+ color: red;
+}
+
+/*div.tiny-global-comment-area {*/
+/* border: 1px solid black;*/
+/* background-color: #e6e6e6;*/
+/* padding: 2px;*/
+/*}*/
+
+div.related-tiny li.right a.bottom-nav-links {
+ font-size: 75%;
+ /*float:right;*/
+ margin-right:5px;
+ position:relative;
+ top:-50px;
+ z-index:99;
+}
+
+div#openerp_page h1 {
+ color: #902D2D;
+ font-family: Verdana,Arial,Helvetica,sans-serif;
+ font-size: 18px;
+ font-weight: bold;
+ margin-top: 0;
+ padding-top: 0;
+ text-align: left;
+ text-decoration: none;
+}
+
+div.all-toctree { /* Main toctree should be hidden but present to have next/previous topic */
+ display: none;
+}
+
+/* Main presentation table */
+
+table.main-content-presentation {
+ width: 100%;
+}
+
+table.main-content-presentation colgroup col {
+ width: 50%;
+}
+
+table.main-content-presentation thead tr th,
+table.main-content-presentation tbody tr td {
+ border: 0px solid black;
+}
+
+table.main-content-presentation tbody tr td a {
+ font-size: 14pt;
+}
+
+table.main-content-presentation tbody tr td p.first {
+ margin-bottom: 0px;
+}
+
+table.main-content-presentation tbody tr td p.last {
+ margin-top: 0px;
+ font-style: italic;
+ font-size: 10pt;
+}
+
+body {
+ font-family: sans-serif;
+ font-size: 100%;
+ background-color: #FFF;
+ color: #000;
+ margin: 0;
+ padding: 0;
+ width: 1004px;
+ margin-left: auto;
+ margin-right: auto;
+}
+
+p {
+ font-size: 90%;
+}
+
+p.fortune {
+ font-weight: bold;
+ color: #666666;
+ font-style: italic;
+ margin-bottom: 0px;
+}
+
+div.body li.toctree-l1 {
+ line-height: 100%;
+}
+
+li.toctree-l1 a {
+ font-size: 70%;
+}
+
+ul.simple {
+ list-style-image: url(redarrow.png);
+}
+
+ul.simple ul {
+ list-style-image: none;
+}
+
+.headerlinkgrey {
+ background-image:url(headergreybg.gif);
+}
+
+.redline {
+ background-image:url(redline.gif);
+}
+
+.greyredcurve {
+ background-image:url(greyredcurve.gif);
+}
+
+.redcurve {
+ background-image:url(redcurve.gif);
+}
+
+.greycurveleft {
+ background-image:url(greycurveleft.gif);
+}
+
+div.headerlink a {
+ color:#FFFFFF;
+ font-family:Verdana,Arial,Helvetica,sans-serif;
+ font-size:12px;
+ text-align:center;
+ text-decoration:none;
+ top: -6px;
+ margin-top:1px;
+ position:relative;
+}
+
+div.headerlink a:link {
+ color:#FFFFFF;
+ font-family:Verdana,Arial,Helvetica,sans-serif;
+ font-size:12px;
+ text-align:center;
+ text-decoration:none;
+}
+
+div.openobject-header td.headerpic {
+ vertical-align: top;
+}
+
+td#menu-header {
+ background: transparent url(mainmenu_button_h25px.png) repeat-x scroll 0 0;
+ font-weight: bold;
+ padding: 0px;
+ text-align: center;
+ height: 25px;
+}
+
+td#menu-breadcrumb {
+ padding: 0px;
+ /*border: 2px solid red;*/
+ height: 25px;
+}
+
+td#menu-breadcrumb div {
+ font-size: 70%;
+}
+
+/* :::: LAYOUT :::: */
+
+div.document {
+ background-color: #FFF;
+}
+
+div.documentwrapper {
+ float: left;
+ width: 100%;
+ background-color: #f6f2f6;
+}
+
+div.bodywrapper {
+ margin: 0 0 0 230px;
+}
+
+div.body {
+ background-color: white;
+ padding: 0 20px 30px 20px;
+ border-left: 1px solid #CCCCCC;
+}
+
+div.sphinxsidebarwrapper {
+ padding: 10px 5px 0 10px;
+ background-color: #f6f2f6;
+}
+
+div.sphinxsidebar {
+ float: left;
+ width: 230px;
+ margin-left: -100%;
+ font-size: 90%;
+}
+
+div.clearer {
+ clear: both;
+}
+
+div.footer {
+ color: #626262;
+ width: 100%;
+ padding: 9px 0 9px 0;
+ text-align: center;
+ font-size: 75%;
+ border-top: 1px solid #CCCCCC;
+}
+
+div.footer a {
+ color: #626262;
+ text-decoration: underline;
+}
+
+div.related {
+ display: none;
+}
+
+div.related-tiny {
+ background-color: #666;
+ color:#FFF;
+ width: 100%;
+ line-height: 24px;
+ font-size: 90%;
+ border-top: 1px solid #CCCCCC;
+ border-bottom: 1px solid #CCCCCC;
+}
+
+div.related-tiny h3 {
+ display: none;
+}
+
+div.related-tiny ul {
+ margin: 0;
+ padding: 0 0 0 10px;
+ list-style: none;
+}
+
+div.related-tiny li {
+ display: inline;
+}
+
+div.related-tiny a {
+ color:#FFF;
+}
+
+div.related-tiny li.right {
+ float: right;
+ margin-right: 5px;
+ position: relative;
+ top: 25px;
+ z-index: 99;
+}
+
+div.related-tiny li.right a {
+ color: black;
+ background-color: white;
+ color: #902D2D;
+ font-weight: bold;
+ font-size: 100%;
+}
+
+/* ::: TOC :::: */
+div.sphinxsidebar h3 {
+ font-family: 'Trebuchet MS', sans-serif;
+ color:#414441;
+ font-size: 1.4em;
+ font-weight: normal;
+ margin: 0;
+ padding: 0;
+}
+
+div.sphinxsidebar h3 a {
+ color:#414441;
+}
+
+div.sphinxsidebar h4 {
+ font-family: 'Trebuchet MS', sans-serif;
+ color:#414441;
+ font-size: 1.3em;
+ font-weight: normal;
+ margin: 5px 0 0 0;
+ padding: 0;
+}
+
+div.sphinxsidebar p {
+ color:#414441;
+}
+
+div.sphinxsidebar p.topless {
+ margin: 5px 10px 10px 10px;
+}
+
+div.sphinxsidebar ul {
+ color:#414441;
+ margin: 10px;
+ padding: 0;
+ list-style: none;
+}
+
+div.sphinxsidebar ul ul,
+div.sphinxsidebar ul.want-points {
+ margin-left: 20px;
+}
+
+div.sphinxsidebar ul ul {
+ /*list-style-image: url(redarrow.png);*/
+ list-style-image: url(chevron.png);
+}
+
+div.sphinxsidebar ul ul ul{
+ list-style-image: none;
+}
+
+div.sphinxsidebar ul ul {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+
+div.sphinxsidebar a {
+ color:#414441;
+}
+
+div.sphinxsidebar form {
+ margin-top: 10px;
+}
+
+div.sphinxsidebar input {
+ border: 1px solid #98dbcc;
+ font-family: sans-serif;
+ font-size: 1em;
+}
+
+/* :::: MODULE CLOUD :::: */
+div.modulecloud {
+ margin: -5px 10px 5px 10px;
+ padding: 10px;
+ line-height: 160%;
+ border: 1px solid #cbe7e5;
+ background-color: #f2fbfd;
+}
+
+div.modulecloud a {
+ padding: 0 5px 0 5px;
+}
+
+/* :::: SEARCH :::: */
+ul.search {
+ margin: 10px 0 0 20px;
+ padding: 0;
+}
+
+ul.search li {
+ padding: 5px 0 5px 20px;
+ background-image: url(file.png);
+ background-repeat: no-repeat;
+ background-position: 0 7px;
+}
+
+ul.search li a {
+ font-weight: bold;
+}
+
+ul.search li div.context {
+ color: #888;
+ margin: 2px 0 0 30px;
+ text-align: left;
+}
+
+ul.keywordmatches li.goodmatch a {
+ font-weight: bold;
+}
+
+/* :::: COMMON FORM STYLES :::: */
+
+div.actions {
+ padding: 5px 10px 5px 10px;
+ border-top: 1px solid #cbe7e5;
+ border-bottom: 1px solid #cbe7e5;
+ background-color: #e0f6f4;
+}
+
+form dl {
+ color: #333;
+}
+
+form dt {
+ clear: both;
+ float: left;
+ min-width: 110px;
+ margin-right: 10px;
+ padding-top: 2px;
+}
+
+input#homepage {
+ display: none;
+}
+
+div.error {
+ margin: 5px 20px 0 0;
+ padding: 5px;
+ border: 1px solid #d00;
+ font-weight: bold;
+}
+
+/* :::: INLINE COMMENTS :::: */
+
+div.inlinecomments {
+ position: absolute;
+ right: 20px;
+}
+
+div.inlinecomments a.bubble {
+ display: block;
+ float: right;
+ background-image: url(style/comment.png);
+ background-repeat: no-repeat;
+ width: 25px;
+ height: 25px;
+ text-align: center;
+ padding-top: 3px;
+ font-size: 0.9em;
+ line-height: 14px;
+ font-weight: bold;
+ color: black;
+}
+
+div.inlinecomments a.bubble span {
+ display: none;
+}
+
+div.inlinecomments a.emptybubble {
+ background-image: url(style/nocomment.png);
+}
+
+div.inlinecomments a.bubble:hover {
+ background-image: url(style/hovercomment.png);
+ text-decoration: none;
+ color: #3ca0a4;
+}
+
+div.inlinecomments div.comments {
+ float: right;
+ margin: 25px 5px 0 0;
+ max-width: 50em;
+ min-width: 30em;
+ border: 1px solid #2eabb0;
+ background-color: #f2fbfd;
+ z-index: 150;
+}
+
+div#comments {
+ border: 1px solid #2eabb0;
+ margin-top: 20px;
+}
+
+div#comments div.nocomments {
+ padding: 10px;
+ font-weight: bold;
+}
+
+div.inlinecomments div.comments h3,
+div#comments h3 {
+ margin: 0;
+ padding: 0;
+ background-color: #2eabb0;
+ color: white;
+ border: none;
+ padding: 3px;
+}
+
+div.inlinecomments div.comments div.actions {
+ padding: 4px;
+ margin: 0;
+ border-top: none;
+}
+
+div#comments div.comment {
+ margin: 10px;
+ border: 1px solid #2eabb0;
+}
+
+div.inlinecomments div.comment h4,
+div.commentwindow div.comment h4,
+div#comments div.comment h4 {
+ margin: 10px 0 0 0;
+ background-color: #2eabb0;
+ color: white;
+ border: none;
+ padding: 1px 4px 1px 4px;
+}
+
+div#comments div.comment h4 {
+ margin: 0;
+}
+
+div#comments div.comment h4 a {
+ color: #d5f4f4;
+}
+
+div.inlinecomments div.comment div.text,
+div.commentwindow div.comment div.text,
+div#comments div.comment div.text {
+ margin: -5px 0 -5px 0;
+ padding: 0 10px 0 10px;
+}
+
+div.inlinecomments div.comment div.meta,
+div.commentwindow div.comment div.meta,
+div#comments div.comment div.meta {
+ text-align: right;
+ padding: 2px 10px 2px 0;
+ font-size: 95%;
+ color: #538893;
+ border-top: 1px solid #cbe7e5;
+ background-color: #e0f6f4;
+}
+
+div.commentwindow {
+ position: absolute;
+ width: 500px;
+ border: 1px solid #cbe7e5;
+ background-color: #f2fbfd;
+ display: none;
+ z-index: 130;
+}
+
+div.commentwindow h3 {
+ margin: 0;
+ background-color: #2eabb0;
+ color: white;
+ border: none;
+ padding: 5px;
+ font-size: 1.5em;
+ cursor: pointer;
+}
+
+div.commentwindow div.actions {
+ margin: 10px -10px 0 -10px;
+ padding: 4px 10px 4px 10px;
+ color: #538893;
+}
+
+div.commentwindow div.actions input {
+ border: 1px solid #2eabb0;
+ background-color: white;
+ color: #135355;
+ cursor: pointer;
+}
+
+div.commentwindow div.form {
+ padding: 0 10px 0 10px;
+}
+
+div.commentwindow div.form input,
+div.commentwindow div.form textarea {
+ border: 1px solid #3c9ea2;
+ background-color: white;
+ color: black;
+}
+
+div.commentwindow div.error {
+ margin: 10px 5px 10px 5px;
+ background-color: #fbe5dc;
+ display: none;
+}
+
+div.commentwindow div.form textarea {
+ width: 99%;
+}
+
+div.commentwindow div.preview {
+ margin: 10px 0 10px 0;
+ background-color: #70d0d4;
+ padding: 0 1px 1px 25px;
+}
+
+div.commentwindow div.preview h4 {
+ margin: 0 0 -5px -20px;
+ padding: 4px 0 0 4px;
+ color: white;
+ font-size: 1.3em;
+}
+
+div.commentwindow div.preview div.comment {
+ background-color: #f2fbfd;
+}
+
+div.commentwindow div.preview div.comment h4 {
+ margin: 10px 0 0 0!important;
+ padding: 1px 4px 1px 4px!important;
+ font-size: 1.2em;
+}
+
+/* :::: SUGGEST CHANGES :::: */
+div#suggest-changes-box input, div#suggest-changes-box textarea {
+ border: 1px solid #ccc;
+ background-color: white;
+ color: black;
+}
+
+div#suggest-changes-box textarea {
+ width: 99%;
+ height: 400px;
+}
+
+
+/* :::: PREVIEW :::: */
+div.preview {
+ background-image: url(style/preview.png);
+ padding: 0 20px 20px 20px;
+ margin-bottom: 30px;
+}
+
+
+/* :::: INDEX PAGE :::: */
+
+table.contentstable {
+ width: 90%;
+}
+
+table.contentstable p.biglink {
+ line-height: 150%;
+}
+
+a.biglink {
+ font-size: 1.3em;
+}
+
+span.linkdescr {
+ font-style: italic;
+ padding-top: 5px;
+ font-size: 90%;
+}
+
+/* :::: INDEX STYLES :::: */
+
+table.indextable td {
+ text-align: left;
+ vertical-align: top;
+}
+
+table.indextable dl, table.indextable dd {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+
+table.indextable tr.pcap {
+ height: 10px;
+}
+
+table.indextable tr.cap {
+ margin-top: 10px;
+ background-color: #f2f2f2;
+}
+
+img.toggler {
+ margin-right: 3px;
+ margin-top: 3px;
+ cursor: pointer;
+}
+
+form.pfform {
+ margin: 10px 0 20px 0;
+}
+
+/* :::: GLOBAL STYLES :::: */
+
+.docwarning {
+ background-color: #ffe4e4;
+ padding: 10px;
+ margin: 0 -20px 0 -20px;
+ border-bottom: 1px solid #f66;
+}
+
+p.subhead {
+ font-weight: bold;
+ margin-top: 20px;
+}
+
+a {
+ color: #355f7c;
+ text-decoration: none;
+}
+
+a:hover {
+ text-decoration: underline;
+}
+
+div.body h1,
+div.body h2,
+div.body h3,
+div.body h4,
+div.body h5,
+div.body h6 {
+ font-family: Verdana, Arial, Helvetica, sans-serif;
+ color: #902D2D;
+ margin: 20px -20px 10px -20px;
+ padding: 3px 0 3px 10px;
+}
+
+div.body h4,
+div.body h5,
+div.body h6 {
+ font-weight: normal;
+}
+
+div.body h1 {
+ margin-top: 0;
+ font-size: 160%;
+ width: 550px;
+}
+div.body h2 { font-size: 140%; }
+div.body h3 { font-size: 120%; }
+div.body h4 { font-size: 110%; }
+div.body h5 { font-size: 100%; }
+div.body h6 { font-size: 100%; }
+
+a.headerlink {
+ color: #c60f0f;
+ font-size: 0.8em;
+ padding: 0 4px 0 4px;
+ text-decoration: none;
+ visibility: hidden;
+}
+
+h1:hover > a.headerlink,
+h2:hover > a.headerlink,
+h3:hover > a.headerlink,
+h4:hover > a.headerlink,
+h5:hover > a.headerlink,
+h6:hover > a.headerlink,
+dt:hover > a.headerlink {
+ visibility: visible;
+}
+
+a.headerlink:hover {
+ background-color: #c60f0f;
+ color: white;
+}
+
+div.body p, div.body dd, div.body li {
+ text-align: justify;
+ /*line-height: 130%;*/
+}
+
+div.body p.caption {
+ text-align: inherit;
+}
+
+div.body td {
+ text-align: left;
+}
+
+ul.fakelist {
+ list-style: none;
+ margin: 10px 0 10px 20px;
+ padding: 0;
+}
+
+.field-list ul {
+ padding-left: 1em;
+}
+
+.first {
+ margin-top: 0 !important;
+}
+
+/* "Footnotes" heading */
+p.rubric {
+ margin-top: 30px;
+ font-weight: bold;
+}
+
+/* Sidebars */
+
+div.sidebar {
+ margin: 0 0 0.5em 1em;
+ border: 1px solid #ddb;
+ padding: 7px 7px 0 7px;
+ background-color: #ffe;
+ width: 40%;
+ float: right;
+ /*border-right:1px solid #CCCCCC;*/
+}
+
+p.sidebar-title {
+ font-weight: bold;
+}
+
+/* "Topics" */
+
+div.topic {
+ background-color: #eee;
+ border: 1px solid #ccc;
+ padding: 7px 7px 0 7px;
+ margin: 10px 0 10px 0;
+}
+
+p.topic-title {
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 10px;
+}
+
+/* Admonitions */
+
+div.admonition {
+ margin-top: 10px;
+ margin-bottom: 10px;
+ padding: 7px;
+}
+
+div.admonition dt {
+ font-weight: bold;
+}
+
+div.admonition dl {
+ margin-bottom: 0;
+}
+
+div.admonition p.admonition-title + p {
+ display: inline;
+}
+
+div.seealso {
+ background-color: #ffc;
+ border: 1px solid #ff6;
+}
+
+div.tip {
+ background-color: #fff583;
+ margin-left: 35px;
+ border: 1px dashed #ccc;
+ padding-left: 90px;
+ padding-right: 8px;
+ padding-top: 8px;
+ padding-bottom: 8px;
+ background-image:url(tip.png);
+ background-repeat: no-repeat;
+ background-position: 15px 10px;
+}
+
+div.warning {
+ background-color: #ffe4e4;
+ border: 1px solid #f66;
+}
+
+div.note {
+ background-color: #eee;
+ border: 1px solid #ccc;
+}
+
+p.admonition-title {
+ margin: 0px 10px 5px 0px;
+ font-weight: bold;
+ display: inline;
+}
+
+p.admonition-title:after {
+ content: ":";
+}
+
+div.body p.centered {
+ text-align: center;
+ margin-top: 25px;
+}
+
+table.docutils {
+ border: 0;
+}
+
+table.docutils td, table.docutils th {
+ padding: 1px 8px 1px 0;
+ border-top: 0;
+ border-left: 0;
+ border-right: 0;
+ border-bottom: 1px solid #aaa;
+}
+
+table.field-list td, table.field-list th {
+ border: 0 !important;
+}
+
+table.footnote td, table.footnote th {
+ border: 0 !important;
+}
+
+.field-list ul {
+ margin: 0;
+ padding-left: 1em;
+}
+
+.field-list p {
+ margin: 0;
+}
+
+dl {
+ margin-bottom: 15px;
+ clear: both;
+}
+
+dd p {
+ margin-top: 0px;
+}
+
+dd ul, dd table {
+ margin-bottom: 10px;
+}
+
+dd {
+ margin-top: 3px;
+ margin-bottom: 10px;
+ margin-left: 30px;
+}
+
+.refcount {
+ color: #060;
+}
+
+dt:target,
+.highlight {
+ background-color: #fbe54e;
+}
+
+dl.glossary dt {
+ font-weight: bold;
+ font-size: 1.1em;
+}
+
+th {
+ text-align: left;
+ padding-right: 5px;
+}
+
+pre {
+ padding: 5px;
+ background-color: #efc;
+ color: #333;
+ border: 1px solid #ac9;
+ border-left: none;
+ border-right: none;
+ overflow: auto;
+}
+
+td.linenos pre {
+ padding: 5px 0px;
+ border: 0;
+ background-color: transparent;
+ color: #aaa;
+}
+
+table.highlighttable {
+ margin-left: 0.5em;
+}
+
+table.highlighttable td {
+ padding: 0 0.5em 0 0.5em;
+}
+
+tt {
+ background-color: #ecf0f3;
+ padding: 0 1px 0 1px;
+ font-size: 0.95em;
+}
+
+tt.descname {
+ background-color: transparent;
+ font-weight: bold;
+ font-size: 1.2em;
+}
+
+tt.descclassname {
+ background-color: transparent;
+}
+
+tt.xref, a tt {
+ background-color: transparent;
+ font-weight: bold;
+}
+
+.footnote:target { background-color: #ffa }
+
+h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt {
+ background-color: transparent;
+}
+
+.optional {
+ font-size: 1.3em;
+}
+
+.versionmodified {
+ font-style: italic;
+}
+
+form.comment {
+ margin: 0;
+ padding: 10px 30px 10px 30px;
+ background-color: #eee;
+}
+
+form.comment h3 {
+ background-color: #326591;
+ color: white;
+ margin: -10px -30px 10px -30px;
+ padding: 5px;
+ font-size: 1.4em;
+}
+
+form.comment input,
+form.comment textarea {
+ border: 1px solid #ccc;
+ padding: 2px;
+ font-family: sans-serif;
+ font-size: 100%;
+}
+
+form.comment input[type="text"] {
+ width: 230px;
+}
+
+form.comment textarea {
+ width: 100%;
+ height: 200px;
+ margin-bottom: 10px;
+}
+
+.system-message {
+ background-color: #fda;
+ padding: 5px;
+ border: 3px solid red;
+}
+
+img.math {
+ vertical-align: middle;
+}
+
+div.math p {
+ text-align: center;
+}
+
+span.eqno {
+ float: right;
+}
+
+img.logo {
+ border: 0;
+}
+
+/* :::: PRINT :::: */
+@media print {
+ div.document,
+ div.documentwrapper,
+ div.bodywrapper {
+ margin: 0;
+ width : 100%;
+ }
+
+ div.sphinxsidebar,
+ div.related-tiny,
+ div.footer,
+ div#comments div.new-comment-box,
+ #top-link {
+ display: none;
+ }
+}
+
=== added file 'i18n/zh_CN/source/.static/favicon.ico'
Binary files i18n/zh_CN/source/.static/favicon.ico 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/favicon.ico 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/footer-bg-a.png'
Binary files i18n/zh_CN/source/.static/footer-bg-a.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/footer-bg-a.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/footer-seps-a.png'
Binary files i18n/zh_CN/source/.static/footer-seps-a.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/footer-seps-a.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/hide_objects_in_sidebar.css'
--- i18n/zh_CN/source/.static/hide_objects_in_sidebar.css 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/.static/hide_objects_in_sidebar.css 2012-12-04 03:46:24 +0000
@@ -0,0 +1,13 @@
+
+/*
+ * didn't found a way to hide certain levels in sidebar
+ * toctree.maxdepth didn't work
+ * */
+
+/*div.sphinxsidebarwrapper ul li ul li ul li a.reference {
+ display: none;
+}
+
+TODO: Should be completely removed from rst once safe to do so.
+*/
+
=== added file 'i18n/zh_CN/source/.static/list-a-bullet-a.gif'
Binary files i18n/zh_CN/source/.static/list-a-bullet-a.gif 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/list-a-bullet-a.gif 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/logo.png'
Binary files i18n/zh_CN/source/.static/logo.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/logo.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/nav-bg-one-active.png'
Binary files i18n/zh_CN/source/.static/nav-bg-one-active.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/nav-bg-one-active.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/nav-bg-one.png'
Binary files i18n/zh_CN/source/.static/nav-bg-one.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/nav-bg-one.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/nav-sub-active.png'
Binary files i18n/zh_CN/source/.static/nav-sub-active.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/nav-sub-active.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/nav-sub-down.gif'
Binary files i18n/zh_CN/source/.static/nav-sub-down.gif 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/nav-sub-down.gif 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/nav-sub-sep.gif'
Binary files i18n/zh_CN/source/.static/nav-sub-sep.gif 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/nav-sub-sep.gif 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/note.png'
Binary files i18n/zh_CN/source/.static/note.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/note.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/openerp.css'
--- i18n/zh_CN/source/.static/openerp.css 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/.static/openerp.css 2012-12-04 03:46:24 +0000
@@ -0,0 +1,245 @@
+* { margin: 0; padding: 0; text-rendering: optimizespeed; }
+html { min-height: 100%; margin: 0 0 1px; font-size: 100.01%; }
+body { background-color: #F5F5F5; font-size: 62.5%; }
+
+@media only screen and (max-device-width: 480px) { html { -webkit-text-size-adjust: none; } }
+body, textarea, input, select, option, button { color: #333; font-family: Myriad Pro,Lucida Grande,Lucida Sans Unicode,sans-serif; line-height: 1.5; }
+li, dt, dd, p, th, td, caption, pre { font-size: 1.3em; }
+ul, ol, dl, p, table, pre, h1, h2, h3, h4, h5, h6 { margin-bottom: 15px; }
+
+a { color: #91312a; text-decoration: none; }
+a:hover, a:focus, a:active { text-decoration: underline; }
+
+ul, ol, dd, blockquote { padding-left: 40px; }
+ul ul, ol ol, ul ol, ol ul { margin-bottom: 0; }
+li *, li p, li li, dt *, dd *, p *, th *, td * { font-size: 1em; }
+
+img { border: none; -ms-interpolation-mode: bicubic; }
+pre { font-family: "Courier New",monospace; }
+
+#top { background: url(top-bg-a.png) repeat-x; text-align: center; }
+#top div.topwrapit { position: relative; z-index: 20; height: 73px; }
+
+#logo { position: absolute; left: -2px; top: 4px; }
+#nav { display: -moz-inline-stack; display: inline-block; position: relative; z-index: 20; list-style: none; margin: 40px auto 0; padding: 0; background: url(nav-bg-one.png) 100% 0 no-repeat; }
+#nav h2 { display: none; }
+html* #nav { display: inline; zoom: 1; }
+
+#nav ul#superfish-1 { float: left; list-style: none; height: 26px; margin: 0; padding: 1px 8px 5px 6px; background: url(nav-bg-one.png) no-repeat; }
+#nav ul li { position: relative; float: left; font-size: 1.1em; font-weight: 600; font-weight:bolder; }
+#nav ul li a { float: left; background: url(nav-bg-one-active.png) -10001px -10001px no-repeat; color: #eee; /*text-shadow: #111 0 -1px 0;*/
+ /* text-decoration: none !important;*/text-decoration: none ; z-index:9999;}
+#nav ul li a:hover{ color: #fff;text-decoration: underline; }
+#nav ul li a span { float: left; height: 21px; padding: 4px 15px 0; background: url(nav-bg-one-active.png) -10001px -10001px no-repeat; cursor: pointer;font-size:1em; line-height : 120%! important }
+#nav ul li em { position: absolute; left: -10001px; top: -10001px; }
+#nav ul li ul { display: none; position: absolute;
+ /* left: 50px; */
+ width: 600px; top: 30px; list-style: none;
+ /* margin: 0 0 0 -57px; */
+ padding: 0; text-align: center; background-color:#fff; }
+#nav ul li ul li ul {
+ display: block; position: absolute;
+ /* left: 50%; */
+ width: 100px; top: 24px; list-style: none;
+ /*margin: 0 0 0 -60px;*/
+ padding: 0; text-align: center;
+ /*left:61px; */
+ background:none repeat scroll 0 0 transparent; /* added by tta, tta@xxxxxxxxxxx*/
+}
+#nav ul li.active ul { display: block; }
+#nav ul li ul li { display: -moz-inline-stack; display: inline-block; float: left; height: 20px; padding: 0 7px 0px 3px; /*background: url(nav-sub-sep.gif) 100% 1px no-repeat;*/ font-size:1em; vertical-align: top;font-weight:normal; text-align:left; margin-left:0px; width:140px;}
+#nav ul li ul li a { color: #474747; width: 190px; }
+#nav ul li ul li a:hover, #nav ul li ul li a:active, #nav ul li ul li a:focus { color: #8d241b; text-decoration: underline; }
+/* #nav ul li ul li.first,
+#nav ul li ul li:first-child { padding-left: 0; } */
+html* #nav ul li ul li { display: inline; }
+#nav ul li.active ul li a { background: none; }
+#nav ul li.active ul li a:hover,
+#nav ul li.active ul li a:focus,
+#nav ul li.active ul li a:active { color: #8d241b; text-decoration: underline; }
+#nav ul li ul li.first a,
+/* #nav ul li ul li:first-child a { padding-left: 18px; background: url(nav-sub-sep.gif) 0 1px no-repeat; } */
+#nav ul li.active ul li a span { height: 26px; height: auto; padding: 2px 0 0; background: none; line-height: 26px; }
+#nav ul li ul li a span.drop { padding-right: 14px; background: url(nav-sub-down.gif) 100% 55% no-repeat; }
+#nav ul li.active ul li.active a span { color: #474747; }
+#nav ul li.active ul li.active a span.regular { padding-bottom: 10px; background: url(nav-sub-active.png) 50% 100% no-repeat; }
+#nav ul.sf-shadow li.first { list-style: none; padding: 0 0.5em 0 0;font-size:1.1em; }
+#nav ul.sf-shadow li.leaf { list-style: none; padding: 0 0.5em 0 0; }
+#nav ul.sf-shadow li.expanded { list-style: none; padding: 0 0.5em 0 0; }
+#call1 { position: absolute; top: 45px; padding-left: 12px; color: #777; font-size: 1.1em; text-transform: uppercase; line-height: 1.25; }
+#call1 a { text-decoration: none; }
+#call { position: absolute; right: 0; top: 45px; padding-left: 12px; color: #777; background:url("list-a-bullet-a.gif") no-repeat scroll 0 50%; font-size: 1.1em; /*text-transform: uppercase; comment by tejas tank, tta@xxxxxxxxxxx */ line-height: 1.25; }
+#call strong { color: #111; font-weight: bold; }
+
+#content { background: WhiteSmoke; /*#fff;*/ /* #e1e0e0; */ }
+#content div.wrapit { padding: 35px 0 35px; }
+
+/* forum css */
+#footer { padding: 1px 0 0px 0px; background-color: #434343; /* background: url(footer-bg-a.png) repeat-x; */ color: #999; text-shadow: #000 0 -1px 0; }
+#footer div.wrapit { overflow: hidden; padding: 0 0 15px; background: url(footer-seps-a.png) no-repeat; }
+#footer ul { display: inline; float: left; list-style: none; width: 210px; margin: 0 0 0 2px; padding: 15px 8px 0 20px; }
+#footer ul.first { width: 218px; margin-left: 0; padding-left: 0; }
+#footer ul li { font-size: 1.2em; }
+#footer ul li strong { float: left; width: 100px; font-weight: normal; }
+#footer ul li span { position: absolute; left: -10001px; top: -10001px; }
+#footer ul li a { color: #999; text-decoration: none; }
+#footer ul li a:hover, #footer ul li a:focus, #footer ul li a:active { color: #ccc; }
+#footer ul li strong a { color: #ccc; }
+#footer ul li strong a:hover, #footer ul li strong a:focus, #footer ul li strong a:active { color: #fff; }
+#footer p { display: inline; float: left; width: 210px; margin: 0 0 0 2px; padding: 15px 0 0 20px; color: #161616; text-shadow: #575757 0 1px 0; font-size: 1.1em; }
+
+div.wrapit { width: 940px; margin: 0 auto; }
+
+div.topwrapit { margin : 0px auto; padding:0; width: 940px; }
+
+/* headers */
+
+h1, h2, h3, h4, h5, h6 { margin: 0 0 10px; color: #111; font-weight: bold; text-shadow: #fff 0 1px 0; }
+h1 { margin-bottom: 5px; font-size: 2.6em; }
+h2 { margin-bottom: 5px; font-size: 2.0em; }
+h3 { font-size: 1.3em;
+padding-left:8px;
+/*text-transform:capitalize;*/
+}
+h3 span{
+ color: gray;
+}
+h4 { font-size: 1.4em; }
+h5 { font-size: 1.2em; }
+h6 { font-size: 1.0em; }
+
+
+/*
+.left { display: inline; float: left; margin: 0 15px 10px 0; }
+.right { display: inline; float: right; margin: 0 15px 10px 0; }
+*/
+
+div.hide { display:none; }
+
+/*********************************************************
+ * FIXES
+ ********************************************************/
+body {
+ width: auto;
+}
+#logo {
+ position: absolute;
+ left: -4px;
+ top: 8px;
+}
+#nav ul#superfish-1 { padding: 5px 8px 5px 8px; }
+#doc_content {
+ font-size: 120%;
+}
+table, tbody, th, td {
+ border: 0px none;
+ border-collapse: separate;
+}
+/*div.bodywrapper {
+ margin:0 0 0 248px;
+}
+div.sphinxsidebar {
+ width:240px;
+}*/
+div.documentwrapper, div.sphinxsidebarwrapper {
+ background-color: #F5F5F5;
+}
+div.document {
+ background-color: transparent;
+}
+#comments_control, div.sphinxsidebar input, #language_control {
+ border: 1px solid #ccc;
+}
+div.related-tiny {
+ border-top: none;
+}
+div.related-tiny li.right a {
+ background: none;
+}
+div.body {
+ border: 1px solid #ccc;
+ -webkit-border-radius: 5px;
+ -moz-border-radius: 5px;
+ border-radius: 5px;
+}
+div.related-tiny {
+ color: #666;
+}
+div.related-tiny li.right {
+ top: 5px;
+}
+li.docnav {
+ color: #fff;
+}
+div#language_links, div#version_links {
+ position: absolute;
+ top: 31px;
+ left: 10px;
+ background: white;
+ padding: 2px;
+ border: 1px solid #ccc;
+ -webkit-border-radius: 5px;
+ -moz-border-radius: 5px;
+ border-radius: 5px;
+ -moz-box-shadow: 3px 3px 3px #666;
+ -webkit-box-shadow: 3px 3px 3px #666;
+ box-shadow: 3px 3px 3px #666;
+}
+div#language_links a, div#version_links a {
+ display: block;
+ padding: 0 2px 0 2px;
+ white-space: nowrap;
+}
+div#language_links a:hover, div#version_links a:hover {
+ background-color: #eee;
+ text-decoration: none;
+}
+div.sphinxsidebar ul a,
+p.topless a {
+ font-size: 80%;
+ color: #902D2D;
+}
+div.sphinxsidebar ul {
+ margin-top: 0px;
+}
+div.sphinxsidebar ul ul,
+div.sphinxsidebar ul ul ul {
+ list-style-image: url(list-a-bullet-a.gif);
+}
+div.sphinxsidebar h4,
+div.sphinxsidebar h3,
+div.sphinxsidebar h3 a {
+ font-weight: bold;
+ color: #000;
+}
+
+/* :::: PRINT :::: */
+@media print {
+ div#top,
+ div#footer {
+ display: none;
+ }
+}
+
+a.button-a {
+ display:block;
+ overflow:hidden;
+ width:100%;
+ height:56px;
+ padding:14px 0 0;
+ background:url(button-a-c.png) no-repeat;
+ color:#e6e6e6;
+ font-size:15px;
+ font-weight:bold;
+ text-align:center;
+ text-decoration:none !important;
+ line-height:1;
+}
+a.button-a span{
+ color:#e6e6e6;
+ position: relative;
+ top: 12px;
+}
+a.button-a:hover span {
+ color:#f5f5f5;
+}
=== added file 'i18n/zh_CN/source/.static/openerp.jpg'
Binary files i18n/zh_CN/source/.static/openerp.jpg 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/openerp.jpg 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/redarrow.png'
Binary files i18n/zh_CN/source/.static/redarrow.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/redarrow.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/searchtools.js'
--- i18n/zh_CN/source/.static/searchtools.js 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/.static/searchtools.js 2012-12-04 03:46:24 +0000
@@ -0,0 +1,519 @@
+/**
+ * helper function to return a node containing the
+ * search summary for a given text. keywords is a list
+ * of stemmed words, hlwords is the list of normal, unstemmed
+ * words. the first one is used to find the occurance, the
+ * latter for highlighting it.
+ */
+
+jQuery.makeSearchSummary = function(text, keywords, hlwords) {
+ var textLower = text.toLowerCase();
+ var start = 0;
+ $.each(keywords, function() {
+ var i = textLower.indexOf(this.toLowerCase());
+ if (i > -1)
+ start = i;
+ });
+ start = Math.max(start - 120, 0);
+ var excerpt = ((start > 0) ? '...' : '') +
+ $.trim(text.substr(start, 240)) +
+ ((start + 240 - text.length) ? '...' : '');
+ var rv = $('<div class="context"></div>').text(excerpt);
+ $.each(hlwords, function() {
+ rv = rv.highlightText(this, 'highlight');
+ });
+ return rv;
+}
+
+/**
+ * Porter Stemmer
+ */
+var PorterStemmer = function() {
+
+ var step2list = {
+ ational: 'ate',
+ tional: 'tion',
+ enci: 'ence',
+ anci: 'ance',
+ izer: 'ize',
+ bli: 'ble',
+ alli: 'al',
+ entli: 'ent',
+ eli: 'e',
+ ousli: 'ous',
+ ization: 'ize',
+ ation: 'ate',
+ ator: 'ate',
+ alism: 'al',
+ iveness: 'ive',
+ fulness: 'ful',
+ ousness: 'ous',
+ aliti: 'al',
+ iviti: 'ive',
+ biliti: 'ble',
+ logi: 'log'
+ };
+
+ var step3list = {
+ icate: 'ic',
+ ative: '',
+ alize: 'al',
+ iciti: 'ic',
+ ical: 'ic',
+ ful: '',
+ ness: ''
+ };
+
+ var c = "[^aeiou]"; // consonant
+ var v = "[aeiouy]"; // vowel
+ var C = c + "[^aeiouy]*"; // consonant sequence
+ var V = v + "[aeiou]*"; // vowel sequence
+
+ var mgr0 = "^(" + C + ")?" + V + C; // [C]VC... is m>0
+ var meq1 = "^(" + C + ")?" + V + C + "(" + V + ")?$"; // [C]VC[V] is m=1
+ var mgr1 = "^(" + C + ")?" + V + C + V + C; // [C]VCVC... is m>1
+ var s_v = "^(" + C + ")?" + v; // vowel in stem
+
+ this.stemWord = function (w) {
+ var stem;
+ var suffix;
+ var firstch;
+ var origword = w;
+
+ if (w.length < 3)
+ return w;
+
+ var re;
+ var re2;
+ var re3;
+ var re4;
+
+ firstch = w.substr(0,1);
+ if (firstch == "y")
+ w = firstch.toUpperCase() + w.substr(1);
+
+ // Step 1a
+ re = /^(.+?)(ss|i)es$/;
+ re2 = /^(.+?)([^s])s$/;
+
+ if (re.test(w))
+ w = w.replace(re,"$1$2");
+ else if (re2.test(w))
+ w = w.replace(re2,"$1$2");
+
+ // Step 1b
+ re = /^(.+?)eed$/;
+ re2 = /^(.+?)(ed|ing)$/;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ re = new RegExp(mgr0);
+ if (re.test(fp[1])) {
+ re = /.$/;
+ w = w.replace(re,"");
+ }
+ }
+ else if (re2.test(w)) {
+ var fp = re2.exec(w);
+ stem = fp[1];
+ re2 = new RegExp(s_v);
+ if (re2.test(stem)) {
+ w = stem;
+ re2 = /(at|bl|iz)$/;
+ re3 = new RegExp("([^aeiouylsz])\\1$");
+ re4 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+ if (re2.test(w))
+ w = w + "e";
+ else if (re3.test(w)) {
+ re = /.$/;
+ w = w.replace(re,"");
+ }
+ else if (re4.test(w))
+ w = w + "e";
+ }
+ }
+
+ // Step 1c
+ re = /^(.+?)y$/;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ re = new RegExp(s_v);
+ if (re.test(stem))
+ w = stem + "i";
+ }
+
+ // Step 2
+ re = /^(.+?)(ational|tional|enci|anci|izer|bli|alli|entli|eli|ousli|ization|ation|ator|alism|iveness|fulness|ousness|aliti|iviti|biliti|logi)$/;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ suffix = fp[2];
+ re = new RegExp(mgr0);
+ if (re.test(stem))
+ w = stem + step2list[suffix];
+ }
+
+ // Step 3
+ re = /^(.+?)(icate|ative|alize|iciti|ical|ful|ness)$/;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ suffix = fp[2];
+ re = new RegExp(mgr0);
+ if (re.test(stem))
+ w = stem + step3list[suffix];
+ }
+
+ // Step 4
+ re = /^(.+?)(al|ance|ence|er|ic|able|ible|ant|ement|ment|ent|ou|ism|ate|iti|ous|ive|ize)$/;
+ re2 = /^(.+?)(s|t)(ion)$/;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ re = new RegExp(mgr1);
+ if (re.test(stem))
+ w = stem;
+ }
+ else if (re2.test(w)) {
+ var fp = re2.exec(w);
+ stem = fp[1] + fp[2];
+ re2 = new RegExp(mgr1);
+ if (re2.test(stem))
+ w = stem;
+ }
+
+ // Step 5
+ re = /^(.+?)e$/;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ re = new RegExp(mgr1);
+ re2 = new RegExp(meq1);
+ re3 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+ if (re.test(stem) || (re2.test(stem) && !(re3.test(stem))))
+ w = stem;
+ }
+ re = /ll$/;
+ re2 = new RegExp(mgr1);
+ if (re.test(w) && re2.test(w)) {
+ re = /.$/;
+ w = w.replace(re,"");
+ }
+
+ // and turn initial Y back to y
+ if (firstch == "y")
+ w = firstch.toLowerCase() + w.substr(1);
+ return w;
+ }
+}
+
+
+/**
+ * Search Module
+ */
+var Search = {
+
+ _index : null,
+ _queued_query : null,
+ _pulse_status : -1,
+
+ init : function() {
+ var params = $.getQueryParameters();
+ if (params.q) {
+ var query = params.q[0];
+ var sections = params.sections || [""];
+ $('input[name="q"]').attr('value', query);
+ this.performSearch(query);
+ } else {
+ // section "All" should be the default:
+ $($('#search_sections').children()[0]).attr("selected", "selected");
+ }
+ },
+
+ /**
+ * Sets the index
+ */
+ setIndex : function(index) {
+ var q;
+ this._index = index;
+ if ((q = this._queued_query) !== null) {
+ this._queued_query = null;
+ Search.query(q);
+ }
+ },
+
+ hasIndex : function() {
+ return this._index !== null;
+ },
+
+ deferQuery : function(query) {
+ this._queued_query = query;
+ },
+
+ stopPulse : function() {
+ this._pulse_status = 0;
+ },
+
+ startPulse : function() {
+ if (this._pulse_status >= 0)
+ return;
+ function pulse() {
+ Search._pulse_status = (Search._pulse_status + 1) % 4;
+ var dotString = '';
+ for (var i = 0; i < Search._pulse_status; i++)
+ dotString += '.';
+ Search.dots.text(dotString);
+ if (Search._pulse_status > -1)
+ window.setTimeout(pulse, 500);
+ };
+ pulse();
+ },
+
+ /**
+ * perform a search for something
+ */
+ performSearch : function(query) {
+ // create the required interface elements
+ this.out = $('#search-results');
+ this.title = $('<h2>' + _('Searching') + '</h2>').appendTo(this.out);
+ this.dots = $('<span></span>').appendTo(this.title);
+ this.status = $('<p style="display: none"></p>').appendTo(this.out);
+ this.output = $('<ul class="search"/>').appendTo(this.out);
+
+ $('#search-progress').text(_('Preparing search...'));
+ this.startPulse();
+
+ // index already loaded, the browser was quick!
+ if (this.hasIndex()) {
+ this.query(query);
+ } else {
+ this.setQuery(query);
+ }
+ },
+
+ query : function(query) {
+ // stem the searchterms and add them to the
+ // correct list
+ var stemmer = new PorterStemmer();
+ var searchterms = [];
+ var excluded = [];
+ var hlterms = [];
+ var tmp = query.split(/\s+/);
+ var object = (tmp.length == 1) ? tmp[0].toLowerCase() : null;
+ for (var i = 0; i < tmp.length; i++) {
+ // stem the word
+ var word = stemmer.stemWord(tmp[i]).toLowerCase();
+ // select the correct list
+ if (word[0] == '-') {
+ var toAppend = excluded;
+ word = word.substr(1);
+ }
+ else {
+ var toAppend = searchterms;
+ hlterms.push(tmp[i].toLowerCase());
+ }
+ // only add if not already in the list
+ if (!$.contains(toAppend, word))
+ toAppend.push(word);
+ };
+ var highlightstring = '?highlight=' + $.urlencode(hlterms.join(" "));
+
+ //console.debug('SEARCH: searching for:');
+ //console.info('required: ', searchterms);
+ //console.info('excluded: ', excluded);
+
+ // prepare search
+ var filenames = this._index.filenames;
+ var titles = this._index.titles;
+ var terms = this._index.terms;
+ var descrefs = this._index.descrefs;
+ var modules = this._index.modules;
+ var desctypes = this._index.desctypes;
+ var fileMap = {};
+ var files = null;
+ var objectResults = [];
+ var regularResults = [];
+ $('#search-progress').empty();
+
+ var params = $.getQueryParameters();
+ var sections = params.sections || [""];
+
+ // lookup as object
+ if (object != null) {
+ for (var module in modules) {
+ if (module.indexOf(object) > -1) {
+ fn = modules[module];
+ if ( (sections.indexOf(filenames[fn].split('/')[0]) > -1) || (sections.indexOf("") > -1) ) {
+ descr = _('module, in ') + titles[fn];
+ objectResults.push([filenames[fn], module, '#module-'+module, descr]);
+ }
+ }
+ }
+ for (var prefix in descrefs) {
+ for (var name in descrefs[prefix]) {
+ if (name.toLowerCase().indexOf(object) > -1) {
+ match = descrefs[prefix][name];
+ if ( (sections.indexOf(match.split('/')[0]) > -1) || (sections.indexOf("") > -1) ) {
+ fullname = (prefix ? prefix + '.' : '') + name;
+ descr = desctypes[match[1]] + _(', in ') + titles[match[0]];
+ objectResults.push([filenames[match[0]], fullname, '#'+fullname, descr]);
+ }
+ }
+ }
+ }
+ }
+
+ // sort results descending
+ objectResults.sort(function(a, b) {
+ return (a[1] > b[1]) ? -1 : ((a[1] < b[1]) ? 1 : 0);
+ });
+
+
+ // perform the search on the required terms
+ for (var i = 0; i < searchterms.length; i++) {
+ var word = searchterms[i];
+ // no match but word was a required one
+ if ((files = terms[word]) == null)
+ break;
+ if (files.length == undefined) {
+ files = [files];
+ }
+ // create the mapping
+ for (var j = 0; j < files.length; j++) {
+ var file = files[j];
+ if (file in fileMap)
+ fileMap[file].push(word);
+ else
+ fileMap[file] = [word];
+ }
+ }
+
+ // now check if the files don't contain excluded terms
+ for (var file in fileMap) {
+ var valid = true;
+
+ // check if all requirements are matched
+ if (fileMap[file].length != searchterms.length)
+ continue;
+
+ // ensure that none of the excluded terms is in the
+ // search result.
+ for (var i = 0; i < excluded.length; i++) {
+ if (terms[excluded[i]] == file ||
+ $.contains(terms[excluded[i]] || [], file)) {
+ valid = false;
+ break;
+ }
+ }
+
+ // if we have still a valid result we can add it
+ // to the result list
+ var params = $.getQueryParameters();
+ var sections = params.sections || [""];
+ if (valid) {
+ if ( (sections.indexOf(filenames[file].split('/')[0]) > -1) || (sections.indexOf("") > -1) ) {
+ regularResults.push([filenames[file], titles[file], '', null]);
+ }
+ }
+ }
+
+ // delete unused variables in order to not waste
+ // memory until list is retrieved completely
+ delete filenames, titles, terms;
+
+ // now sort the regular results descending by title
+ regularResults.sort(function(a, b) {
+ var left = a[1].toLowerCase();
+ var right = b[1].toLowerCase();
+ return (left > right) ? -1 : ((left < right) ? 1 : 0);
+ });
+
+ // combine both
+ var results = regularResults.concat(objectResults);
+
+ // print the results
+ var resultCount = results.length;
+ function getSectionLabel(section) {
+ var labels = {
+ 'technical_guide': "Module Index",
+ 'contribute': "Community Book",
+ 'book': "Open ERP Book",
+ 'install': "Installation Manuals",
+ 'bi': "Business Intelligence",
+ 'features': "Open ERP Features",
+ 'developer': "Developer Book"
+ }
+ var label = labels[section];
+ return (label) ? label : section;
+ }
+
+ function setPreviousSearch() {
+ var section_field = $('#search_sections');
+ var section_field_options = section_field.children();
+ section_field_options.each(function(i){
+ var params = $.getQueryParameters();
+ if (params.sections) {
+ var current_option = $(section_field_options[i]);
+ if (params.sections.indexOf(current_option.val()) > -1) {
+ $(current_option).attr("selected", "selected");
+ }
+ }
+
+ $('input[name="q"]').attr('value', params.q[0]);
+
+ });
+ }
+
+ function displayNextItem() {
+ // results left, load the summary and display it
+ if (results.length) {
+ var item = results.pop();
+ var listItem = $('<li style="display:none"></li>');
+
+ listItem.append($('<span class="search-section-label"> (' + getSectionLabel(item[0].split('/')[0]) + ') </span>'));
+
+ listItem.append($('<a/>').attr(
+ 'href',
+ item[0] + DOCUMENTATION_OPTIONS.FILE_SUFFIX +
+ highlightstring + item[2]).html(item[1]));
+ if (item[3]) {
+ listItem.append($('<span> (' + item[3] + ')</span>'));
+ Search.output.append(listItem);
+ listItem.slideDown(5, function() {
+ displayNextItem();
+ });
+ } else if (DOCUMENTATION_OPTIONS.HAS_SOURCE) {
+ $.get('_sources/' + item[0] + '.txt', function(data) {
+ listItem.append($.makeSearchSummary(data, searchterms, hlterms));
+ Search.output.append(listItem);
+ listItem.slideDown(5, function() {
+ displayNextItem();
+ });
+ });
+ } else {
+ // no source available, just display title
+ Search.output.append(listItem);
+ listItem.slideDown(5, function() {
+ displayNextItem();
+ });
+ }
+ } else {
+ // search finished, update title and status message
+ Search.stopPulse();
+ Search.title.text(_('Search Results'));
+ if (!resultCount) {
+ Search.status.text(_('Your search did not match any documents. Please make sure that all words are spelled correctly and that you\'ve selected enough categories.'));
+ } else {
+ Search.status.text(_('Search finished, found %s page(s) matching the search query.').replace('%s', resultCount));
+ }
+ Search.status.fadeIn(500);
+ }
+ }
+ setPreviousSearch();
+ displayNextItem();
+ }
+}
+
+$(document).ready(function() {
+ Search.init();
+});
=== added file 'i18n/zh_CN/source/.static/tiny_language.js'
--- i18n/zh_CN/source/.static/tiny_language.js 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/.static/tiny_language.js 2012-12-04 03:46:24 +0000
@@ -0,0 +1,28 @@
+function setup_selection($selector, $options) {
+ $options.hide();
+ $selector.click(function() {
+ $options.toggle();
+ return false;
+ });
+ $(document).keyup(function(e) {
+ if (e.keyCode == 27) {
+ $options.hide();
+ }
+ });
+ $selector.add($options).mouseenter(function() {
+ $options.show();
+ clearTimeout($options.data('timeoutId'));
+ }).mouseleave(function() {
+ var timeoutId = setTimeout(function(){ $options.hide(); }, 500);
+ $options.data('timeoutId', timeoutId);
+ });
+}
+
+
+if (/openerp\.com$/.test(document.domain)) {
+ $(document).ready(function() {
+ $('.openerp_website').show();
+ setup_selection($('#change_language'),$('#language_links'))
+ setup_selection($('#change_version'),$('#version_links'))
+ });
+}
=== added file 'i18n/zh_CN/source/.static/tip.png'
Binary files i18n/zh_CN/source/.static/tip.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/tip.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/.static/top-bg-a.png'
Binary files i18n/zh_CN/source/.static/top-bg-a.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/.static/top-bg-a.png 2012-12-04 03:46:24 +0000 differ
=== added directory 'i18n/zh_CN/source/.templates'
=== added file 'i18n/zh_CN/source/.templates/layout.html'
--- i18n/zh_CN/source/.templates/layout.html 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/.templates/layout.html 2012-12-04 03:46:24 +0000
@@ -0,0 +1,165 @@
+{% extends "!layout.html" %}
+
+{#
+ Jinja2-based Template, see doc at: http://jinja.pocoo.org
+ For specific Sphinx templating, see also: http://sphinx.pocoo.org/templating.html
+ #}
+
+{% set languages = [
+ ['/v6.1/', 'en', 'English'],
+ ['/v6.1/es/', 'es', 'Español'],
+ ['/v6.1/fr/', 'fr', 'Français'],
+ ['/v6.1/it/', 'it', 'Italiano'],
+ ['/v6.1/ro/', 'ro', 'Română'],
+ ['/v6.1/ru/', 'ru', 'Русский'],
+ ['/v6.1/vi/', 'vi', 'Tiếng Việt'],
+] %}
+{% set versions = [
+ ['/v5.0/', '5.0'],
+ ['/v6.0/', '6.0'],
+ ['/v6.1/', '6.1'],
+] %}
+
+{% block extrahead %}
+ <link rel="stylesheet" href="{{ pathto('_static/openerp.css', 1) }}" type="text/css" />
+ <script src="{{ pathto('_static/tiny_language.js', 1) }}" type="text/javascript"></script>
+{% endblock %}
+
+{%- block content %}
+<div id="top">
+ <div class="topwrapit">
+ <h1 id="logo"><a title="" href="http://www.openerp.com/";><img alt="" src="{{ pathto('_static/logo.png', 1) }}" border="0"></a></h1>
+ <div id="nav">
+ <ul id="superfish-1" class="sf-menu sf-navbar sf-style-default">
+ <!--<li class="tta_999999999" id="menu-329-1"><a class="active" title="" href="http://www.openerp.com/products"; style="background-position: 4px 4px; color: rgb(238, 238, 238); padding: 0.4em 0em;"><span style="background-position: 100% 0pt; padding-top: 5px;">Products</span></a></li>-->
+ <li><a href="http://www.openerp.com/products";><span>Products</span></a></li>
+ <li><a href="http://www.openerp.com/catalog";><span>Buy</span></a></li>
+ <li><a href="http://www.openerp.com/partners";><span>Partners</span></a></li>
+ <li><a href="http://www.openerp.com/community";><span>Community</span></a></li>
+ <li><a href="http://www.openerp.com/about-us";><span>About Us</span></a></li>
+ </ul>
+ </div>
+ <span id="call"><a href="http://www.openerp.com/contact";>Contact Us</a><strong> +32 81813700</strong></span>
+ </div>
+</div>
+
+<div class="related-tiny">
+ <div class="topwrapit">
+ <ul>
+ {%- block rootrellink_new %}
+ <li class="docnav"><a href="{{ pathto(master_doc) }}">{{ shorttitle|e }}</a>{{ reldelim1 }}</li>
+ {%- endblock %}
+ {%- for parent in parents %}
+ <li class="docnav"><a href="{{ parent.link|e }}" accesskey="U">{{ parent.title }}</a>{{ reldelim1 }}</li>
+ {%- endfor %}
+ {%- block relbaritems %} {% endblock %}
+ </ul>
+ </div>
+</div>
+<div class="related-tiny">
+ <div class="topwrapit">
+ <ul>
+ <li class="right openerp_website" style="display: none">
+ {{ reldelim2 }}
+ {%- for lg in languages %}
+ <a href="{{ lg[0] + pagename + ".html" }}" title="{{ lg[2] }}">{{ lg[1] }}</a>
+ {%- endfor %}
+ </li>
+ <li class="right openerp_website" style="display:none">
+ {%- for version in versions %}
+ <a href="{{ version[0] + pagename + ".html" }}">{{ version[1] }}</a>
+ {%- endfor %}
+ <a href="/trunk/">trunk</a>
+ </li>
+ {%- for rellink in rellinks %}
+ <li class="right">
+ <a href="{{ pathto(rellink[0]) }}" title="{{ rellink[1]|striptags }}"
+ accesskey="{{ rellink[2] }}">{{ rellink[3] }}</a>
+ {{ reldelim2 }}</li>
+ {%- endfor %}
+ </ul>
+ </div>
+</div>
+
+<div id="content">
+ <div class="wrapit">
+ <div id="doc_content">
+ <!-- #Content -->
+ {{ super() }}
+ </div>
+ </div>
+</div>
+{% endblock %}
+
+{%- block document %}
+ <div class="document">
+ <div class="documentwrapper">
+ {%- if builder != 'htmlhelp' %}
+ <div class="bodywrapper">
+ {%- endif %}
+ <div class="body">
+ {% block body %} {% endblock %}
+ </div>
+ The documentation is editable by everyone on
+ <a href="http://code.launchpad.net/~openerp-community/openobject-doc/";>
+ Launchpad</a>.
+ {%- if builder != 'htmlhelp' %}
+ </div>
+ {%- endif %}
+ </div>
+
+{%- endblock %}
+
+{% block sidebarsearch %}
+ {{ super() }}
+<div>
+ <a href="http://www.openerp.com/online"; class="button-a"><span>Use Online</span></a>
+</div>
+<div>
+ <a class="button-a" href="http://www.openerp.com/download/ebook/";><span style="position: relative; top: 12px;">Download ebook</span></a>
+</div>
+{% endblock %}
+
+{%- block footer %}
+ <div id="footer">
+ <div class="wrapit">
+ <ul class="first">
+ <li><strong style="color: rgb(204, 204, 204);">Use Online</strong> <a href="http://www.openerp.com/online";>Subscribe</a></li>
+ <li><strong style="color: rgb(204, 204, 204);">Use On-Site</strong> <a href="http://www.openerp.com/services/subscribe-onsite";>Subscribe</a></li>
+ <li><strong style="color: rgb(204, 204, 204);">Learn</strong> <a href="http://www.openerp.com/services/trainings";>Training</a></li>
+ <li><strong style="color: rgb(204, 204, 204);">Read</strong> <a target="_blank" href="http://doc.openerp.com/";>Documentation</a></li>
+ </ul>
+ <ul>
+ <li><strong style="color: rgb(204, 204, 204);">Contribute</strong> <a target="_blank" href="http://www.launchpad.net/openobject";>Launchpad</a></li>
+ <li><strong style="color: rgb(204, 204, 204);">Discuss</strong> <a href="http://www.openerp.com/forum";>Forum</a></li>
+ <li><strong style="color: rgb(204, 204, 204);">Meet</strong> <a href="http://www.openerp.com/events";>Events</a></li>
+ <li><strong style="color: rgb(204, 204, 204);">Talk</strong> <a target="_blank" href="http://www.twitter.com/openerp";>Twitter</a><strong style="color: rgb(204, 204, 204);"><br /></strong></li>
+ </ul>
+ <ul>
+ <li><strong style="color: rgb(204, 204, 204);">Company</strong> <a href="http://www.openerp.com/about-us";>About Us<br /></a></li>
+ <li><strong style="color: rgb(204, 204, 204);">Philosophy</strong> <a href="http://www.openerp.com/products/vision";>Vision</a></li>
+ <li><strong style="color: rgb(204, 204, 204);">More </strong><a href="http://www.openerp.com/contact";>Contact Us</a></li>
+ </ul>
+ <p>© 2005-Today. All rights reserved.<br/>OpenERP is a trademark of OpenERP s.a. The software is released under AGPL.</p>
+ </div>
+ </div>
+ {#{super()}#}
+ <script type="text/javascript">
+
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-7333765-1']);
+ _gaq.push(['_setDomainName', '.openerp.com']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+
+ </script>
+{% endblock %}
+
+{#
+ vi: ft=htmljinja fileencoding=utf-8
+#}
=== added file 'i18n/zh_CN/source/.templates/search.html'
--- i18n/zh_CN/source/.templates/search.html 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/.templates/search.html 2012-12-04 03:46:24 +0000
@@ -0,0 +1,79 @@
+{% extends "layout.html" %}
+{% set title = _('Search') %}
+{% set script_files = script_files + ['_static/searchtools.js'] %}
+{% block body %}
+ <h1 id="search-documentation">{{ _('Search') }}</h1>
+ <p>
+ {% trans %}From here you can search these documents. Enter your search
+ words into the box below and click "search". Note that the search
+ function will automatically search for all of the words. Pages
+ containing fewer words won't appear in the result list.{% endtrans %}
+ </p>
+
+ <form action="" method="get">
+ <table border="0">
+ <tr>
+ <td class="search-type">
+ <span>Sections:</span>
+ </td>
+ <td>
+ <select id="search_sections" name="sections" multiple="1" size="5">
+ <option value="">All</option>
+ <option value="technical_guide">Module Index</option>
+ <option value="contribute">Community Book</option>
+ <option value="book">Open ERP Book</option>
+ <option value="install">Installation Manual</option>s
+ <option value="bi">Business Intelligence</option>
+ <option value="features">Open ERP Features</option>
+ <option value="developer">Developer Book</option>
+ </select>
+ </td>
+ <td>
+ </td>
+ </tr>
+ <tr>
+ <td class="search-type">
+ <span>Query:</span>
+ </td>
+ <td style="white-space: nowrap;">
+ <input type="text" name="q" value="" />
+ <input type="submit" value="search" />
+ </td>
+ <td class="search-exclude-tip">
+ <span>
+ If you want to exclude a word from the search results, prepend it with a dash. (eg.: -network)
+ </span>
+ </td>
+ </tr>
+ </table>
+
+ <span id="search-progress" style="padding-left: 10px"></span>
+ </form>
+
+ {% if search_performed %}
+ <h2>{{ _('Search Results') }}</h2>
+ {% if not search_results %}
+ <p>{{ _('Your search did not match any results.') }}</p>
+ {% endif %}
+ {% endif %}
+ <div id="search-results">
+ {% if search_results %}
+ <ul>
+ {% for href, caption, context in search_results %}
+ <li><a href="{{ pathto(item.href) }}">{{ caption }}</a>
+ <div class="context">{{ context|e }}</div>
+ </li>
+ {% endfor %}
+ </ul>
+ {% endif %}
+ </div>
+{% endblock %}
+{% block footer %}
+ {{ super() }}
+ <script type="text/javascript" src="searchindex.js"></script>
+{% endblock %}
+
+{#
+ vi: ft=htmljinja
+#}
+
=== added directory 'i18n/zh_CN/source/bi'
=== added directory 'i18n/zh_CN/source/bi/CubeBrowser'
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/CubeBrowser.rst'
--- i18n/zh_CN/source/bi/CubeBrowser/CubeBrowser.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeBrowser/CubeBrowser.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,40 @@
+
+.. i18n: Cube Browser
+.. i18n: ============
+..
+
+Cube Browser
+============
+
+.. i18n: Cube Browser of Open Object-BI Platform lets users design their own reports through a clean and effective Web-based environment.
+..
+
+Cube Browser of Open Object-BI Platform lets users design their own reports through a clean and effective Web-based environment.
+
+.. i18n: It provides users with a friendly layer to create MDX Query on previously designed OLAP Cubes with a few mouse clicks, and retrieve the desired information in a comprehensible tabular layout. They can reformat the layout, to drill to fetch further fine information and easily analyze it to understand business currents and causes.
+..
+
+It provides users with a friendly layer to create MDX Query on previously designed OLAP Cubes with a few mouse clicks, and retrieve the desired information in a comprehensible tabular layout. They can reformat the layout, to drill to fetch further fine information and easily analyze it to understand business currents and causes.
+
+.. i18n: If users don't need the full power of query capabilities they can simply explore information in existing reports—formatting and interacting with data to meet their reporting needs.
+..
+
+If users don't need the full power of query capabilities they can simply explore information in existing reports—formatting and interacting with data to meet their reporting needs.
+
+.. i18n: Goal behind Cube Browser
+.. i18n: ------------------------
+..
+
+Goal behind Cube Browser
+------------------------
+
+.. i18n: Provide user with a thin client to make reporting far more efficient.
+.. i18n: Let user use full power of MDXAlchemy engine.
+.. i18n: Wrapping the process of designing queries into simpler steps: clicks, drags and drops.
+.. i18n: Keeping the interface as simple yet powerful reporting tool.
+..
+
+Provide user with a thin client to make reporting far more efficient.
+Let user use full power of MDXAlchemy engine.
+Wrapping the process of designing queries into simpler steps: clicks, drags and drops.
+Keeping the interface as simple yet powerful reporting tool.
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserDaD.rst'
--- i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserDaD.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserDaD.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,64 @@
+
+.. i18n: Creating your report with drag and drop
+.. i18n: =======================================
+..
+
+Creating your report with drag and drop
+=======================================
+
+.. i18n: Cube Browser uses basic drag-and-drop operations to add data to a report.
+.. i18n: Measures represent categories of stored values; Dimensions represent categories of OLAP information
+..
+
+Cube Browser uses basic drag-and-drop operations to add data to a report.
+Measures represent categories of stored values; Dimensions represent categories of OLAP information
+
+.. i18n: All UI controls update their contents automatically, and the resulting query is displayed on the OLAP Grid.
+..
+
+All UI controls update their contents automatically, and the resulting query is displayed on the OLAP Grid.
+
+.. i18n: Queries can be created by Dragging a member on the on the Droppable Area marked with the box for the drop zone.
+..
+
+Queries can be created by Dragging a member on the on the Droppable Area marked with the box for the drop zone.
+
+.. i18n: Lets drop the All Product Category on the drop zone referred as grid afterward.
+.. i18n: As soon as the member is dropped the resultant query is formed and can be viewed using the toolbar.
+.. i18n: Query is then executed giving the first output on the grid. The first drop is always on the rows.
+..
+
+Lets drop the All Product Category on the drop zone referred as grid afterward.
+As soon as the member is dropped the resultant query is formed and can be viewed using the toolbar.
+Query is then executed giving the first output on the grid. The first drop is always on the rows.
+
+.. i18n: .. image:: images/d_browsr4.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/d_browsr4.png
+ :scale: 65
+
+.. i18n: The second axis can be added by dropping a member on blue zone. The output can be seen immediately. Each user action changes and executes the query and then shows the result. The cross or delete button beside each item in grid deletes the elements from the query and the resultant grid. On top we can see if any filters are applied on the query or not.
+..
+
+The second axis can be added by dropping a member on blue zone. The output can be seen immediately. Each user action changes and executes the query and then shows the result. The cross or delete button beside each item in grid deletes the elements from the query and the resultant grid. On top we can see if any filters are applied on the query or not.
+
+.. i18n: .. image:: images/d_browsr5.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/d_browsr5.png
+ :scale: 65
+
+.. i18n: We can see the query by selecting the MDX button on the toolbar. This will open the pop up to show the mdx query for the current grid.
+..
+
+We can see the query by selecting the MDX button on the toolbar. This will open the pop up to show the mdx query for the current grid.
+
+.. i18n: .. image:: images/data_browser11.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser11.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserDrill.rst'
--- i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserDrill.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserDrill.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,51 @@
+
+.. i18n: Drill Up/Down
+.. i18n: =============
+..
+
+Drill Up/Down
+=============
+
+.. i18n: Drill Down on a Member
+.. i18n: ----------------------
+..
+
+Drill Down on a Member
+----------------------
+
+.. i18n: Drilling down is the process of expanding a member to its child member for a purpose of broader analysis on data.
+.. i18n: User can locate the member he wants to drill down.
+.. i18n: Just a click on that member will expand the parent member to display its child members.
+..
+
+Drilling down is the process of expanding a member to its child member for a purpose of broader analysis on data.
+User can locate the member he wants to drill down.
+Just a click on that member will expand the parent member to display its child members.
+
+.. i18n: .. image:: images/data_browser15.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser15.png
+ :scale: 65
+
+.. i18n: Drill Up on a Member
+.. i18n: --------------------
+..
+
+Drill Up on a Member
+--------------------
+
+.. i18n: Drill up causes a member to wrap up all this children if displayed.
+.. i18n: Just a click on an expanded parent member will wrap all its child members.
+..
+
+Drill up causes a member to wrap up all this children if displayed.
+Just a click on an expanded parent member will wrap all its child members.
+
+.. i18n: .. image:: images/data_browser16.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser16.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserGraph.rst'
--- i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserGraph.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserGraph.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,48 @@
+
+.. i18n: Graphs
+.. i18n: ======
+..
+
+Graphs
+======
+
+.. i18n: Graphs presents the grid output on the graphs or graphical way by plotting on the axis.
+..
+
+Graphs presents the grid output on the graphs or graphical way by plotting on the axis.
+
+.. i18n: Lets take the case:
+..
+
+Lets take the case:
+
+.. i18n: .. image:: images/data_browser10.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser10.png
+ :scale: 65
+
+.. i18n: For the above grid when we will generate graph it will be:
+..
+
+For the above grid when we will generate graph it will be:
+
+.. i18n: .. image:: images/data_browser12.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser12.png
+ :scale: 65
+
+.. i18n: When we have children expanded for the one element on the axis and the other is not drilled. There will be two graph to show the same
+..
+
+When we have children expanded for the one element on the axis and the other is not drilled. There will be two graph to show the same
+
+.. i18n: .. image:: images/data_browser17.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser17.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSelect.rst'
--- i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSelect.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSelect.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,60 @@
+
+.. i18n: Loading the Cube
+.. i18n: ================
+..
+
+Loading the Cube
+================
+
+.. i18n: Cube Browser will provide the selection of the schema and cube. It comes with a toolbar that allows some common operations with one click.
+..
+
+Cube Browser will provide the selection of the schema and cube. It comes with a toolbar that allows some common operations with one click.
+
+.. i18n: .. image:: images/data_browser1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser1.png
+ :scale: 65
+
+.. i18n: With the help of toolbar we can undo redo the queries, we can switch between the graph and grid view, we can expand all or collapse all elements.
+..
+
+With the help of toolbar we can undo redo the queries, we can switch between the graph and grid view, we can expand all or collapse all elements.
+
+.. i18n: Schema combo box will show all the schema made.
+..
+
+Schema combo box will show all the schema made.
+
+.. i18n: .. image:: images/d_browser1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/d_browser1.png
+ :scale: 65
+
+.. i18n: Once we select the schema the next combo box will show all cubes that belong to that schema.
+..
+
+Once we select the schema the next combo box will show all cubes that belong to that schema.
+
+.. i18n: .. image:: images/d_browser2.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/d_browser2.png
+ :scale: 65
+
+.. i18n: Once we select the cube, the cube is loaded in the tree form in the space below. We can expand each node and it will display to the depth of the level configured.
+..
+
+Once we select the cube, the cube is loaded in the tree form in the space below. We can expand each node and it will display to the depth of the level configured.
+
+.. i18n: .. image:: images/d_browser3.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/d_browser3.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSlicer.rst'
--- i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSlicer.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSlicer.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,34 @@
+
+.. i18n: Adding Slicer
+.. i18n: =============
+..
+
+Adding Slicer
+=============
+
+.. i18n: A Slicer is filtering on the data fetched by a MDX Query.
+..
+
+A Slicer is filtering on the data fetched by a MDX Query.
+
+.. i18n: It can be added by clicking on filter images on right side on the members.
+..
+
+It can be added by clicking on filter images on right side on the members.
+
+.. i18n: Filtering gives users a powerful tool for slicing the multidimensional data for organizing and analyzing in more detail.
+..
+
+Filtering gives users a powerful tool for slicing the multidimensional data for organizing and analyzing in more detail.
+
+.. i18n: This filtering of the data allows user to get the required information to the lowest level and analyse it to get the best use from their cube's multidimensional data.
+..
+
+This filtering of the data allows user to get the required information to the lowest level and analyse it to get the best use from their cube's multidimensional data.
+
+.. i18n: .. image:: images/data_browser10.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/data_browser10.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSwap.rst'
--- i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSwap.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeBrowser/CubeBrowserSwap.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,42 @@
+
+.. i18n: Swapping Rows and Columns
+.. i18n: =========================
+..
+
+Swapping Rows and Columns
+=========================
+
+.. i18n: Once the report is generated in the cube browser we can swap it so rows move to the columns area and columns move to the rows area. This also swaps the query parts.
+..
+
+Once the report is generated in the cube browser we can swap it so rows move to the columns area and columns move to the rows area. This also swaps the query parts.
+
+.. i18n: We can form query by drag and drop which will form the report.
+..
+
+We can form query by drag and drop which will form the report.
+
+.. i18n: .. image:: images/data_browser8.png
+..
+
+.. image:: images/data_browser8.png
+
+.. i18n: ----
+..
+
+----
+
+.. i18n: Once the report is generated, we can swap which will form the report as shown below:
+..
+
+Once the report is generated, we can swap which will form the report as shown below:
+
+.. i18n: .. image:: images/data_browser9.png
+..
+
+.. image:: images/data_browser9.png
+
+.. i18n: **Now after swapping, we can move on with drag and drop to form queries and generate report.**
+..
+
+**Now after swapping, we can move on with drag and drop to form queries and generate report.**
=== added directory 'i18n/zh_CN/source/bi/CubeBrowser/images'
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/d_browser1.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/d_browser1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/d_browser1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/d_browser2.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/d_browser2.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/d_browser2.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/d_browser3.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/d_browser3.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/d_browser3.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/d_browser4.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/d_browser4.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/d_browser4.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/d_browser5.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/d_browser5.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/d_browser5.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/d_browsr4.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/d_browsr4.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/d_browsr4.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/d_browsr5.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/d_browsr5.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/d_browsr5.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser1.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser10.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser10.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser10.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser11.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser11.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser11.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser12.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser12.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser12.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser13.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser13.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser13.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser14.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser14.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser14.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser15.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser15.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser15.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser16.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser16.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser16.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser17.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser17.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser17.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser2.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser2.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser2.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser3.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser3.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser3.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser4.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser4.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser4.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser5.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser5.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser5.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser6.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser6.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser6.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser7.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser7.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser7.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser8.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser8.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser8.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeBrowser/images/data_browser9.png'
Binary files i18n/zh_CN/source/bi/CubeBrowser/images/data_browser9.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeBrowser/images/data_browser9.png 2012-12-04 03:46:24 +0000 differ
=== added directory 'i18n/zh_CN/source/bi/CubeCli'
=== added file 'i18n/zh_CN/source/bi/CubeCli/CubeCliExample.rst'
--- i18n/zh_CN/source/bi/CubeCli/CubeCliExample.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeCli/CubeCliExample.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,43 @@
+
+.. i18n: Reports
+.. i18n: -------
+..
+
+Reports
+-------
+
+.. i18n: The report generated for the *test_query* file is::
+.. i18n:
+.. i18n: credit_limit count
+.. i18n: All user [66700.0] [21.0]
+..
+
+The report generated for the *test_query* file is::
+
+ credit_limit count
+ All user [66700.0] [21.0]
+
+.. i18n: ..
+..
+
+..
+
+.. i18n: ::
+.. i18n:
+.. i18n: All user
+.. i18n: Root Administrator Demo User
+.. i18n: credit_limit [66700.0] [2700.0] [49000.0]
+.. i18n: count [21.0] [2.0] [6.0]
+..
+
+::
+
+ All user
+ Root Administrator Demo User
+ credit_limit [66700.0] [2700.0] [49000.0]
+ count [21.0] [2.0] [6.0]
+
+.. i18n: ..
+..
+
+..
=== added file 'i18n/zh_CN/source/bi/CubeCli/CubeCliIntro.rst'
--- i18n/zh_CN/source/bi/CubeCli/CubeCliIntro.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeCli/CubeCliIntro.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,182 @@
+
+.. i18n: .. _CLI-link:
+.. i18n:
+.. i18n: Command Line Interface
+.. i18n: ======================
+..
+
+.. _CLI-link:
+
+Command Line Interface
+======================
+
+.. i18n: Introduction to the cli
+.. i18n: -----------------------
+..
+
+Introduction to the cli
+-----------------------
+
+.. i18n: *The CLI - Command Line Interface*
+..
+
+*The CLI - Command Line Interface*
+
+.. i18n: Command Line Interface is similar to that of psql, but used for MDX queries on the cube.
+.. i18n: As
+..
+
+Command Line Interface is similar to that of psql, but used for MDX queries on the cube.
+As
+
+.. i18n: ::
+.. i18n:
+.. i18n: Welcome to OpenObject BI , the interactive terminal.
+.. i18n: Communication: XML-RPC.
+.. i18n: Type: \? for help with MDX commands
+.. i18n: \e for execute the MDX query
+.. i18n: \d for quit
+.. i18n: BI-terp=#
+..
+
+::
+
+ Welcome to OpenObject BI , the interactive terminal.
+ Communication: XML-RPC.
+ Type: \? for help with MDX commands
+ \e for execute the MDX query
+ \d for quit
+ BI-terp=#
+
+.. i18n: Currently we can use CLI to test different queries, it can also be used for running automated tests.
+..
+
+Currently we can use CLI to test different queries, it can also be used for running automated tests.
+
+.. i18n: The basic syntax for testing query is:
+..
+
+The basic syntax for testing query is:
+
+.. i18n: **./tinybi.py -d <<Database Name>> -H localhost -U <<User Name> -W <<Password>> -p <<Port Number>> -s <<Schema Name>> -c <<MDX Query>>**
+..
+
+**./tinybi.py -d <<Database Name>> -H localhost -U <<User Name> -W <<Password>> -p <<Port Number>> -s <<Schema Name>> -c <<MDX Query>>**
+
+.. i18n: One can check all these options by typing
+..
+
+One can check all these options by typing
+
+.. i18n: *$python tinybi.py --help*
+..
+
+*$python tinybi.py --help*
+
+.. i18n: Usage: tinybi.py [options]
+..
+
+Usage: tinybi.py [options]
+
+.. i18n: Options:
+..
+
+Options:
+
+.. i18n: ::
+.. i18n:
+.. i18n: --version show program's version number and exit
+.. i18n: -h, --help show this help message and exit
+..
+
+::
+
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+
+.. i18n: ..
+..
+
+..
+
+.. i18n: ::
+.. i18n:
+.. i18n: General options:
+.. i18n: -c COMMAND, --command=COMMAND
+.. i18n: The query to execute
+.. i18n: -s SCHEMA, --schema=SCHEMA
+.. i18n: The schema to use for the query
+..
+
+::
+
+ General options:
+ -c COMMAND, --command=COMMAND
+ The query to execute
+ -s SCHEMA, --schema=SCHEMA
+ The schema to use for the query
+
+.. i18n: ..
+..
+
+..
+
+.. i18n: ::
+.. i18n:
+.. i18n: Connection options:
+.. i18n: -d DATABASE, --database=DATABASE
+.. i18n: Database name
+.. i18n: -H HOSTNAME, --hostname=HOSTNAME
+.. i18n: Server hostname
+.. i18n: -U USERNAME, --username=USERNAME
+.. i18n: Username
+.. i18n: -W PASSWORD, --password=PASSWORD
+.. i18n: Password
+.. i18n: -p PORT, --port=PORT
+.. i18n: Server port
+..
+
+::
+
+ Connection options:
+ -d DATABASE, --database=DATABASE
+ Database name
+ -H HOSTNAME, --hostname=HOSTNAME
+ Server hostname
+ -U USERNAME, --username=USERNAME
+ Username
+ -W PASSWORD, --password=PASSWORD
+ Password
+ -p PORT, --port=PORT
+ Server port
+
+.. i18n: ..
+..
+
+..
+
+.. i18n: :Example:
+..
+
+:Example:
+
+.. i18n: ./tinybi.py -d "terp" -H localhost -U admin -W admin -p 8069 -s "tinyerp" -c "select {[user].[all]} on rows, {[measures].[credit_limit],[measures].[count]} on columns from res_partner"
+..
+
+./tinybi.py -d "terp" -H localhost -U admin -W admin -p 8069 -s "tinyerp" -c "select {[user].[all]} on rows, {[measures].[credit_limit],[measures].[count]} on columns from res_partner"
+
+.. i18n: This will give output on CLI as:
+..
+
+This will give output on CLI as:
+
+.. i18n: .. csv-table::
+.. i18n: :header: "\ ","credit_limit","count"
+.. i18n:
+.. i18n: "All user","[66700.0]","[21.0]"
+..
+
+.. csv-table::
+ :header: "\ ","credit_limit","count"
+
+ "All user","[66700.0]","[21.0]"
=== added file 'i18n/zh_CN/source/bi/CubeCli/CubeCliTests.rst'
--- i18n/zh_CN/source/bi/CubeCli/CubeCliTests.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeCli/CubeCliTests.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,69 @@
+
+.. i18n: Running Automated Test Cases
+.. i18n: ----------------------------
+..
+
+Running Automated Test Cases
+----------------------------
+
+.. i18n: We can check all the queries on :ref:`CLI <CLI-link>` by making a file with queries to be tested with the syntax given in :ref:`CLI <CLI-link>`
+..
+
+We can check all the queries on :ref:`CLI <CLI-link>` by making a file with queries to be tested with the syntax given in :ref:`CLI <CLI-link>`
+
+.. i18n: For example we can create *test_query* file with the content like
+..
+
+For example we can create *test_query* file with the content like
+
+.. i18n: .. :ref:`test_query <test_query-link>`
+..
+
+.. :ref:`test_query <test_query-link>`
+
+.. i18n: -------
+..
+
+-------
+
+.. i18n: ::
+.. i18n:
+.. i18n: DATABASE='terp'
+..
+
+::
+
+ DATABASE='terp'
+
+.. i18n: ::
+.. i18n:
+.. i18n: ./tinybi.py -d ${DATABASE} -H localhost -U admin -W admin -p 8069 -s "tinyerp" -c "select <br />{[user].[all]} on rows, {[measures].[credit_limit],[measures].[count]} <br />on columns from res_partner"
+..
+
+::
+
+ ./tinybi.py -d ${DATABASE} -H localhost -U admin -W admin -p 8069 -s "tinyerp" -c "select <br />{[user].[all]} on rows, {[measures].[credit_limit],[measures].[count]} <br />on columns from res_partner"
+
+.. i18n: ::
+.. i18n:
+.. i18n: ./tinybi.py -d ${DATABASE} -H localhost -U admin -W admin -p 8069 -s "tinyerp" -c "select <br /> {[measures].[credit_limit],[measures].[count]} on rows, {[user].[all],[user].children} <br /> on columns from res_partner"
+..
+
+::
+
+ ./tinybi.py -d ${DATABASE} -H localhost -U admin -W admin -p 8069 -s "tinyerp" -c "select <br /> {[measures].[credit_limit],[measures].[count]} on rows, {[user].[all],[user].children} <br /> on columns from res_partner"
+
+.. i18n: -------
+..
+
+-------
+
+.. i18n: The file can be run at the command prompt. It will give output on success or an error message on failure
+..
+
+The file can be run at the command prompt. It will give output on success or an error message on failure
+
+.. i18n: The output of this file can be viewed CubeCliExample test_query
+..
+
+The output of this file can be viewed CubeCliExample test_query
=== added file 'i18n/zh_CN/source/bi/CubeCli/CubeCliXMLRPC.rst'
--- i18n/zh_CN/source/bi/CubeCli/CubeCliXMLRPC.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeCli/CubeCliXMLRPC.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,22 @@
+
+.. i18n: WebService Interface
+.. i18n: --------------------
+..
+
+WebService Interface
+--------------------
+
+.. i18n: Another component of OpenObject - BI, allows applications to access dimensional data using Web Services. Applications issue XML-based queries across a Web-based connection using XML-RPC. Support is focused on XML query languages rather than on OLAP language.
+..
+
+Another component of OpenObject - BI, allows applications to access dimensional data using Web Services. Applications issue XML-based queries across a Web-based connection using XML-RPC. Support is focused on XML query languages rather than on OLAP language.
+
+.. i18n: By providing a flexible, platform-neutral method to render diverse data types, XML has become a standard for exchanging information across heterogeneous applications. Web services, a set of XML based protocols for finding and communicating between loosely-coupled, internet callable application "services" have therefore become the preferred mechanism for integrating heterogeneous applications and enabling service architectures.
+..
+
+By providing a flexible, platform-neutral method to render diverse data types, XML has become a standard for exchanging information across heterogeneous applications. Web services, a set of XML based protocols for finding and communicating between loosely-coupled, internet callable application "services" have therefore become the preferred mechanism for integrating heterogeneous applications and enabling service architectures.
+
+.. i18n: The use of XML and Web services for data exchange and integration provides significant IT benefits including flexibility, interoperability and reach.
+..
+
+The use of XML and Web services for data exchange and integration provides significant IT benefits including flexibility, interoperability and reach.
=== added directory 'i18n/zh_CN/source/bi/CubeDesigner'
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/CubeDesigner.rst'
--- i18n/zh_CN/source/bi/CubeDesigner/CubeDesigner.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeDesigner/CubeDesigner.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,191 @@
+
+.. i18n: Goal of Cube Designer
+.. i18n: =====================
+..
+
+Goal of Cube Designer
+=====================
+
+.. i18n: The goal is to develop a User Friendly Cube Designer for Open Object - BI that allows a user to define and / or modify an OLAP cube definition starting from any database. (Oracle, MySQL, PostgreSQL). This has to be user friendly so that a end-user can define his own cube on his own database without any development knowledge.
+..
+
+The goal is to develop a User Friendly Cube Designer for Open Object - BI that allows a user to define and / or modify an OLAP cube definition starting from any database. (Oracle, MySQL, PostgreSQL). This has to be user friendly so that a end-user can define his own cube on his own database without any development knowledge.
+
+.. i18n: Basic features
+.. i18n: --------------
+..
+
+Basic features
+--------------
+
+.. i18n: The cube designer of the OpenObject – BI Solutions helps users create new cubes and modify existing ones. Once the user is connected to the database they can create cubes in two ways
+.. i18n: #Wizard Flow
+.. i18n: #Generic Flow.
+..
+
+The cube designer of the OpenObject – BI Solutions helps users create new cubes and modify existing ones. Once the user is connected to the database they can create cubes in two ways
+#Wizard Flow
+#Generic Flow.
+
+.. i18n: Wizard Flow
+.. i18n: +++++++++++
+..
+
+Wizard Flow
++++++++++++
+
+.. i18n: In the wizard flow a wizard guides the user through the entire process of cube creation. Navigation can be done through Next and Previous button.
+..
+
+In the wizard flow a wizard guides the user through the entire process of cube creation. Navigation can be done through Next and Previous button.
+
+.. i18n: .. note::
+.. i18n: Clicking on the “Save” button on every form causes the data to be written in the database and simultaneously the “Next” button is activated and the user is navigated to the next form.
+.. i18n: Next button will not be activated until the data is “Saved”.
+..
+
+.. note::
+ Clicking on the “Save” button on every form causes the data to be written in the database and simultaneously the “Next” button is activated and the user is navigated to the next form.
+ Next button will not be activated until the data is “Saved”.
+
+.. i18n: Generic Flow
+.. i18n: ++++++++++++
+..
+
+Generic Flow
+++++++++++++
+
+.. i18n: The cube can be modified / created by the user in a normal way.
+..
+
+The cube can be modified / created by the user in a normal way.
+
+.. i18n: :Modify / Create A Schema:
+..
+
+:Modify / Create A Schema:
+
+.. i18n: The user specifies the desired schema name.
+.. i18n: They select the desired database or create it with the help of [new].
+.. i18n: They specify the schema description.
+.. i18n: They save the schema.
+..
+
+The user specifies the desired schema name.
+They select the desired database or create it with the help of [new].
+They specify the schema description.
+They save the schema.
+
+.. i18n: :Modify / Create A Fact Table:
+..
+
+:Modify / Create A Fact Table:
+
+.. i18n: User makes a particular Type for Fact table
+.. i18n: They select the desired database or Schema for a particular Fact Table, or create one using the [new] button.
+.. i18n:
+.. i18n: :Modify / Create A Database:
+..
+
+User makes a particular Type for Fact table
+They select the desired database or Schema for a particular Fact Table, or create one using the [new] button.
+
+:Modify / Create A Database:
+
+.. i18n: User specifies the “General Parameters”
+.. i18n: He specifies the “Connection Parameters” that specify which database and port number will be used for the connection.
+.. i18n: He tests the connection for error and the “Connection URL” is generated.
+.. i18n: On connection string being correct the new database is created.
+..
+
+User specifies the “General Parameters”
+He specifies the “Connection Parameters” that specify which database and port number will be used for the connection.
+He tests the connection for error and the “Connection URL” is generated.
+On connection string being correct the new database is created.
+
+.. i18n: :Modify / Create A Cube:
+..
+
+:Modify / Create A Cube:
+
+.. i18n: The user provides desired cube name along with the fact tables and schema name.
+.. i18n: The user can select previously created fact tables via a drop down box or can create a new fact table by clicking on [new].
+.. i18n: Same goes for schema too.
+.. i18n: The dimensions and measures will be empty as they have not yet been created.
+..
+
+The user provides desired cube name along with the fact tables and schema name.
+The user can select previously created fact tables via a drop down box or can create a new fact table by clicking on [new].
+Same goes for schema too.
+The dimensions and measures will be empty as they have not yet been created.
+
+.. i18n: :Modify / Create A Dimension:
+..
+
+:Modify / Create A Dimension:
+
+.. i18n: The user provides the dimension name.
+.. i18n: The given cube name will appear in the drop down box. They can select a cube name from the list or create a new cube by clicking on [new].
+.. i18n: Hierarchies are absent.
+..
+
+The user provides the dimension name.
+The given cube name will appear in the drop down box. They can select a cube name from the list or create a new cube by clicking on [new].
+Hierarchies are absent.
+
+.. i18n: :Modify / Create A Hierarchies:
+..
+
+:Modify / Create A Hierarchies:
+
+.. i18n: The user provides the hierarchy name.
+.. i18n: The dimension name will come in the dropdown box.
+.. i18n: User can create a new dimension by clicking on [new].
+.. i18n: User will provide the hierarchy field name, sequence, hierarchy type, all member and default member fields.
+.. i18n: User will give the fact table by selecting it from a drop down box or by creating a new fact table altogether by clicking on [new]
+..
+
+The user provides the hierarchy name.
+The dimension name will come in the dropdown box.
+User can create a new dimension by clicking on [new].
+User will provide the hierarchy field name, sequence, hierarchy type, all member and default member fields.
+User will give the fact table by selecting it from a drop down box or by creating a new fact table altogether by clicking on [new]
+
+.. i18n: :Modify / Create A Levels:
+..
+
+:Modify / Create A Levels:
+
+.. i18n: The user has to specify the level name, column name, column id, level class, table name, sequence and hierarchy.
+.. i18n: Hierarchy will appear in the drop down box.
+.. i18n: He can create a new hierarchy by clicking on [new].
+..
+
+The user has to specify the level name, column name, column id, level class, table name, sequence and hierarchy.
+Hierarchy will appear in the drop down box.
+He can create a new hierarchy by clicking on [new].
+
+.. i18n: .. note::
+.. i18n: Clicking on the "Save" button on every form causes the data to be written in the database.
+.. i18n: Double Click on row opens modification window of respective record.
+..
+
+.. note::
+ Clicking on the "Save" button on every form causes the data to be written in the database.
+ Double Click on row opens modification window of respective record.
+
+.. i18n: :Modify / Create A Measures:
+..
+
+:Modify / Create A Measures:
+
+.. i18n: The user provides the Measure name.
+.. i18n: The given cube name will appear in the drop down box. They can select a cube name from the list or create a new cube by clicking on the [new].
+.. i18n: It defines the all calculation / aggregation with fact column name.
+.. i18n: Here all calculation / aggregation are interdependent with the fields of fact column name, aggregator, data type and format of string.
+..
+
+The user provides the Measure name.
+The given cube name will appear in the drop down box. They can select a cube name from the list or create a new cube by clicking on the [new].
+It defines the all calculation / aggregation with fact column name.
+Here all calculation / aggregation are interdependent with the fields of fact column name, aggregator, data type and format of string.
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/DefinigDim.rst'
--- i18n/zh_CN/source/bi/CubeDesigner/DefinigDim.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeDesigner/DefinigDim.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,19 @@
+
+.. i18n: Defining Dimension
+.. i18n: ==================
+..
+
+Defining Dimension
+==================
+
+.. i18n: :ref:`Dimension <dimension-link>` need to name to be identified. Cube will be filled by default according to the schema opened.
+..
+
+:ref:`Dimension <dimension-link>` need to name to be identified. Cube will be filled by default according to the schema opened.
+
+.. i18n: .. image:: images/dimension.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/dimension.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/DefiningCube.rst'
--- i18n/zh_CN/source/bi/CubeDesigner/DefiningCube.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeDesigner/DefiningCube.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,97 @@
+
+.. i18n: Defining Cube
+.. i18n: =============
+..
+
+Defining Cube
+=============
+
+.. i18n: Cube as we discussed in :ref:`The Cube <cube-link>`
+..
+
+Cube as we discussed in :ref:`The Cube <cube-link>`
+
+.. i18n: For making the cube we need
+..
+
+For making the cube we need
+
+.. i18n: #. Cube Name : Meaningful name for the cube
+.. i18n: #. :ref:`Schema <schema-link>`: :ref:`Configuring Schema <schema_configuration-link>`
+.. i18n: #. Query Logging : It will decides whether the query will be logged or not.
+.. i18n: #. Fact Table : A table that contains the facts (measures) and the link to the other tables that in turn qualifies for the dimensions. The fact table can be a join of two or more tables.
+..
+
+#. Cube Name : Meaningful name for the cube
+#. :ref:`Schema <schema-link>`: :ref:`Configuring Schema <schema_configuration-link>`
+#. Query Logging : It will decides whether the query will be logged or not.
+#. Fact Table : A table that contains the facts (measures) and the link to the other tables that in turn qualifies for the dimensions. The fact table can be a join of two or more tables.
+
+.. i18n: For example :
+.. i18n: To analyse the sales data we will take join of sale_order and sale_order_line as a fact table.
+..
+
+For example :
+To analyse the sales data we will take join of sale_order and sale_order_line as a fact table.
+
+.. i18n: So we start making the cube. The screen shows the new cube window. The schema name will be filled by default depending on the schema we are browsing in the tree. The initial window will show the relational column for fact table which will open the search box of all the fact table created so far.
+..
+
+So we start making the cube. The screen shows the new cube window. The schema name will be filled by default depending on the schema we are browsing in the tree. The initial window will show the relational column for fact table which will open the search box of all the fact table created so far.
+
+.. i18n: .. image:: images/cube1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/cube1.png
+ :scale: 65
+
+.. i18n: We create the new fact table. In the relational column it will show all the primary keys for all tables loaded in the introspection.
+.. i18n: We select sale_order_line table with primary key id. Once we are done with the selection we will join the table.
+..
+
+We create the new fact table. In the relational column it will show all the primary keys for all tables loaded in the introspection.
+We select sale_order_line table with primary key id. Once we are done with the selection we will join the table.
+
+.. i18n: .. image:: images/cube2.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/cube2.png
+ :scale: 65
+
+.. i18n: Join Table will open all the tables that are referenced from the sale_order_line, according to the table name from the relational column. We select order_id as it is the field related to the sale_order. Hence, we made the join of the sale_order_line and sale_order
+..
+
+Join Table will open all the tables that are referenced from the sale_order_line, according to the table name from the relational column. We select order_id as it is the field related to the sale_order. Hence, we made the join of the sale_order_line and sale_order
+
+.. i18n: .. image:: images/cube3.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/cube3.png
+ :scale: 65
+
+.. i18n: If we want more tables to be joined we can do that by adding more on Join Tables. Now the search will be on all the reference from sale_order and sale_order_line
+..
+
+If we want more tables to be joined we can do that by adding more on Join Tables. Now the search will be on all the reference from sale_order and sale_order_line
+
+.. i18n: .. image:: images/cube4.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/cube4.png
+ :scale: 65
+
+.. i18n: Finally the cube page will look like
+..
+
+Finally the cube page will look like
+
+.. i18n: .. image:: images/cube5.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/cube5.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/DefiningHier.rst'
--- i18n/zh_CN/source/bi/CubeDesigner/DefiningHier.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeDesigner/DefiningHier.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,88 @@
+
+.. i18n: Defining Hierarchy
+.. i18n: ==================
+..
+
+Defining Hierarchy
+==================
+
+.. i18n: :ref:`Hierarchy <hierarchy-link>` is the arrangements of objects, peoples etc .. in a ranked or some series. The hierarchy are the way of arranging the dimensions.
+..
+
+:ref:`Hierarchy <hierarchy-link>` is the arrangements of objects, peoples etc .. in a ranked or some series. The hierarchy are the way of arranging the dimensions.
+
+.. i18n: It need the fact table.
+..
+
+It need the fact table.
+
+.. i18n: Lets take the Example of Products.
+..
+
+Lets take the Example of Products.
+
+.. i18n: We want our sales cube to work on the products - we want to see the products sold. We have divided the products into categories. So we will make the Product Hierarchy display products by category.
+..
+
+We want our sales cube to work on the products - we want to see the products sold. We have divided the products into categories. So we will make the Product Hierarchy display products by category.
+
+.. i18n: Lets see the new hierarchy. Some values, such as hierarchy name and dimension, may be set by default.
+..
+
+Lets see the new hierarchy. Some values, such as hierarchy name and dimension, may be set by default.
+
+.. i18n: .. image:: images/hier1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/hier1.png
+ :scale: 65
+
+.. i18n: We now define the fact table for the hierarchy. Relational column will show the all fields of the sale_order_line and sale_order as these are the fact tables for the cube. We select product_id from sale_order_line which is related to product_product
+..
+
+We now define the fact table for the hierarchy. Relational column will show the all fields of the sale_order_line and sale_order as these are the fact tables for the cube. We select product_id from sale_order_line which is related to product_product
+
+.. i18n: .. image:: images/hier2.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/hier2.png
+ :scale: 65
+
+.. i18n: We want to get both product name and category. We know the product_category will give category and product_template will give the name.
+.. i18n: Now the list is filtered accordingly for adding the join tables
+..
+
+We want to get both product name and category. We know the product_category will give category and product_template will give the name.
+Now the list is filtered accordingly for adding the join tables
+
+.. i18n: .. image:: images/hier3.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/hier3.png
+ :scale: 65
+
+.. i18n: After selecting the product_tmpl_id we select the category table.
+..
+
+After selecting the product_tmpl_id we select the category table.
+
+.. i18n: .. image:: images/hier4.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/hier4.png
+ :scale: 65
+
+.. i18n: So final fact table for the Product Category will be
+.. i18n:
+.. i18n: .. image:: images/hier5.png
+.. i18n: :scale: 65
+..
+
+So final fact table for the Product Category will be
+
+.. image:: images/hier5.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/DefiningLevel.rst'
--- i18n/zh_CN/source/bi/CubeDesigner/DefiningLevel.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeDesigner/DefiningLevel.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,61 @@
+
+.. i18n: Defining Level
+.. i18n: ==============
+..
+
+Defining Level
+==============
+
+.. i18n: :ref:`Level <level-link>` It specifies the actual data to be displayed. It
+.. i18n: specifies the depth for the hierarchy. Now taking the same example for the
+.. i18n: Products. We need it to be two level depth.
+..
+
+:ref:`Level <level-link>` It specifies the actual data to be displayed. It
+specifies the depth for the hierarchy. Now taking the same example for the
+Products. We need it to be two level depth.
+
+.. i18n: #. Product Category
+.. i18n: #. Product Name
+..
+
+ #. Product Category
+ #. Product Name
+
+.. i18n: Lets start with making the levels. Details like hierarchy name, level name
+.. i18n: filled by default according the schema we are in. We need to specify the column
+.. i18n: to be used for filling the level. We open the column name and it will show all
+.. i18n: the fields from tables defined in the hierarchy. We select name from the
+.. i18n: product category
+..
+
+Lets start with making the levels. Details like hierarchy name, level name
+filled by default according the schema we are in. We need to specify the column
+to be used for filling the level. We open the column name and it will show all
+the fields from tables defined in the hierarchy. We select name from the
+product category
+
+.. i18n: .. image:: images/level1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/level1.png
+ :scale: 65
+
+.. i18n: We want more level for displaying the name of the products. In the column name
+.. i18n: we will select the column name from the product_template. The main thing is to
+.. i18n: change the sequence to 2. This will show the products category wise on the
+.. i18n: browser.
+..
+
+We want more level for displaying the name of the products. In the column name
+we will select the column name from the product_template. The main thing is to
+change the sequence to 2. This will show the products category wise on the
+browser.
+
+.. i18n: .. image:: images/level1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/level1.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/DefiningMeas.rst'
--- i18n/zh_CN/source/bi/CubeDesigner/DefiningMeas.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeDesigner/DefiningMeas.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,65 @@
+
+.. i18n: Defining Measure
+.. i18n: ================
+..
+
+Defining Measure
+================
+
+.. i18n: :ref:`Measure <measure-link>` are the fact or quantitative values. It comes from the fact table configured in the cube.
+..
+
+:ref:`Measure <measure-link>` are the fact or quantitative values. It comes from the fact table configured in the cube.
+
+.. i18n: We will make the measure for the same example. Measure type specifies whether it will be column base or sql expression based.
+..
+
+We will make the measure for the same example. Measure type specifies whether it will be column base or sql expression based.
+
+.. i18n: Column Based:
+..
+
+Column Based:
+
+.. i18n: .. image:: images/measure1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/measure1.png
+ :scale: 65
+
+.. i18n: SQL Expression Based:
+..
+
+SQL Expression Based:
+
+.. i18n: .. image:: images/measure2.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/measure2.png
+ :scale: 65
+
+.. i18n: In the column based measure we will see select the fact table column from the columns of the fact table define in the cube i.e. sale_order and sale_order_line.
+..
+
+In the column based measure we will see select the fact table column from the columns of the fact table define in the cube i.e. sale_order and sale_order_line.
+
+.. i18n: .. image:: images/measure3.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/measure3.png
+ :scale: 65
+
+.. i18n: So finally measure will look like:
+..
+
+So finally measure will look like:
+
+.. i18n: .. image:: images/measure4.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/measure4.png
+ :scale: 65
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/LoadingDB.rst'
--- i18n/zh_CN/source/bi/CubeDesigner/LoadingDB.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeDesigner/LoadingDB.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,7 @@
+
+.. i18n: Database Introspection
+.. i18n: ======================
+..
+
+Database Introspection
+======================
=== added directory 'i18n/zh_CN/source/bi/CubeDesigner/images'
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/cube1.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/cube1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/cube1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/cube2.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/cube2.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/cube2.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/cube3.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/cube3.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/cube3.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/cube4.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/cube4.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/cube4.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/cube5.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/cube5.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/cube5.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/dimension.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/dimension.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/dimension.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/hier1.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/hier1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/hier1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/hier2.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/hier2.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/hier2.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/hier3.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/hier3.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/hier3.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/hier4.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/hier4.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/hier4.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/hier5.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/hier5.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/hier5.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/level1.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/level1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/level1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/level2.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/level2.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/level2.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/measure1.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/measure1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/measure1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/measure2.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/measure2.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/measure2.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/measure3.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/measure3.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/measure3.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/CubeDesigner/images/measure4.png'
Binary files i18n/zh_CN/source/bi/CubeDesigner/images/measure4.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeDesigner/images/measure4.png 2012-12-04 03:46:24 +0000 differ
=== added directory 'i18n/zh_CN/source/bi/CubeXML'
=== added file 'i18n/zh_CN/source/bi/CubeXML/CubeXML.rst'
--- i18n/zh_CN/source/bi/CubeXML/CubeXML.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeXML/CubeXML.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,42 @@
+
+.. i18n: Defining Schema in XML
+.. i18n: ======================
+..
+
+Defining Schema in XML
+======================
+
+.. i18n: .. describe:: Why XML for Schema?
+..
+
+.. describe:: Why XML for Schema?
+
+.. i18n: * XML is a meta language used to describe the structure and content of documents.
+.. i18n:
+.. i18n: * XML, although originally a document markup language, is increasingly used for data exchange on the Web.
+.. i18n:
+.. i18n: * The application of XML as a standard data exchange format makes it attractive to use in conjunction with OLAP tools.
+.. i18n:
+.. i18n: * An XML document has both structure and content, and XML provides a means for separating one from the other in the electronic document.
+.. i18n:
+.. i18n: * The structure of a document is through use of matching tag pairs (termed an element) and the information between matching tags is referred to as the content of the element. Furthermore, an element is permitted to have additional attributes, where values are assigned to the attributes in the start tag of the element.
+.. i18n:
+.. i18n: * XML documents can also contain a description of their logical structure, which is called a document type definition (DTD). A DTD is a context free grammar defining, in terms of element content specifications, all allowable elements, their attributes, and the elements nesting structure. Given a DTD it can be verified that an XML document conforms to the DTD, and if so, the XML document is said to be valid.
+..
+
+* XML is a meta language used to describe the structure and content of documents.
+
+* XML, although originally a document markup language, is increasingly used for data exchange on the Web.
+
+* The application of XML as a standard data exchange format makes it attractive to use in conjunction with OLAP tools.
+
+* An XML document has both structure and content, and XML provides a means for separating one from the other in the electronic document.
+
+* The structure of a document is through use of matching tag pairs (termed an element) and the information between matching tags is referred to as the content of the element. Furthermore, an element is permitted to have additional attributes, where values are assigned to the attributes in the start tag of the element.
+
+* XML documents can also contain a description of their logical structure, which is called a document type definition (DTD). A DTD is a context free grammar defining, in terms of element content specifications, all allowable elements, their attributes, and the elements nesting structure. Given a DTD it can be verified that an XML document conforms to the DTD, and if so, the XML document is said to be valid.
+
+.. i18n: All these features make XML attractive when making a schema.
+..
+
+All these features make XML attractive when making a schema.
=== added file 'i18n/zh_CN/source/bi/CubeXML/CubeXMLExample.rst'
--- i18n/zh_CN/source/bi/CubeXML/CubeXMLExample.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeXML/CubeXMLExample.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,697 @@
+
+.. i18n: Creating Cube Definition using XML file
+.. i18n: =======================================
+..
+
+Creating Cube Definition using XML file
+=======================================
+
+.. i18n: .. describe:: Things to know
+..
+
+.. describe:: Things to know
+
+.. i18n: Before going through XML details it is good to have an idea of all :ref:`Terminologies <terminologies-link>` of OLAP.
+..
+
+Before going through XML details it is good to have an idea of all :ref:`Terminologies <terminologies-link>` of OLAP.
+
+.. i18n: **Lets understand XML file in detail**
+..
+
+**Lets understand XML file in detail**
+
+.. i18n: **Step: 1. The first step is to specify the database to use with parameters such as name, database name , database login and database password**
+..
+
+**Step: 1. The first step is to specify the database to use with parameters such as name, database name , database login and database password**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.fact.database" id="fact_databases_BI">
+.. i18n: <field name="name">Tiny ERP databases</field>
+.. i18n: <field name="db_name">Sales</field>
+.. i18n: <field name="db_login">postgres</field>
+.. i18n: <field name="db_password">postgres</field>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.fact.database" id="fact_databases_BI">
+ <field name="name">Tiny ERP databases</field>
+ <field name="db_name">Sales</field>
+ <field name="db_login">postgres</field>
+ <field name="db_password">postgres</field>
+ </record>
+
+.. i18n: * This will create the parameters needed to connect to the database.
+..
+
+* This will create the parameters needed to connect to the database.
+
+.. i18n: **Step: 2. Defining Schema**
+..
+
+**Step: 2. Defining Schema**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.schema" id="schema_main_sales">
+.. i18n: <field name="name">tinysales</field>
+.. i18n: <field name="state">none</field>
+.. i18n: <field name="database_id" ref="fact_databases_BI"/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.schema" id="schema_main_sales">
+ <field name="name">tinysales</field>
+ <field name="state">none</field>
+ <field name="database_id" ref="fact_databases_BI"/>
+ </record>
+
+.. i18n: * This will create schema name tinysales for fact_database_BI made in step 1
+..
+
+* This will create schema name tinysales for fact_database_BI made in step 1
+
+.. i18n: **Step: 3. Defining fact table to be used (In this case, sale_order_line)**
+..
+
+**Step: 3. Defining fact table to be used (In this case, sale_order_line)**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_sales_order_line">
+.. i18n: <field name="name">sale_order_line</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.cube.table" id="table_sales_order_line">
+ <field name="name">sale_order_line</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+
+.. i18n: **Step: 4. Making Cube on fact_table**
+..
+
+**Step: 4. Making Cube on fact_table**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.cube" id="cube_sales_order_line">
+.. i18n: <field name="name">sale_order_line</field>
+.. i18n: <field name="table_id" ref="table_sales_order_line"/>
+.. i18n: <field name="schema_id" ref="schema_main_sales"/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.cube" id="cube_sales_order_line">
+ <field name="name">sale_order_line</field>
+ <field name="table_id" ref="table_sales_order_line"/>
+ <field name="schema_id" ref="schema_main_sales"/>
+ </record>
+
+.. i18n: * This will create the cube named sale_order_line
+..
+
+* This will create the cube named sale_order_line
+
+.. i18n: **Step: 5. Creating Dimension product**
+..
+
+**Step: 5. Creating Dimension product**
+
+.. i18n: * This will be used to fetch and make MDX Query on all the product
+..
+
+* This will be used to fetch and make MDX Query on all the product
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.dimension" id="dimension_product_template">
+.. i18n: <field name="name">Products</field>
+.. i18n: <field name="cube_id" ref="cube_sales_order_line"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_product_template">
+.. i18n: <field name="name">product_product</field>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.dimension" id="dimension_product_template">
+ <field name="name">Products</field>
+ <field name="cube_id" ref="cube_sales_order_line"/>
+ </record>
+
+ <record model="olap.cube.table" id="table_product_template">
+ <field name="name">product_product</field>
+ </record>
+
+.. i18n: **Step: 5a. Creating Hierarchy for the Dimension Product**
+..
+
+**Step: 5a. Creating Hierarchy for the Dimension Product**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.hierarchy" id="hierarchy_product_template">
+.. i18n: <field name="name">All Products</field>
+.. i18n: <field name="dimension_id" ref="dimension_product_template"/>
+.. i18n: <field name="primary_key_table">product_product</field>
+.. i18n: <field name="table_id" ref="table_product_template"/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.hierarchy" id="hierarchy_product_template">
+ <field name="name">All Products</field>
+ <field name="dimension_id" ref="dimension_product_template"/>
+ <field name="primary_key_table">product_product</field>
+ <field name="table_id" ref="table_product_template"/>
+ </record>
+
+.. i18n: **Step: 5b Creating Level for the Dimension Product**
+..
+
+**Step: 5b Creating Level for the Dimension Product**
+
+.. i18n: First, we create column.
+..
+
+First, we create column.
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.database.columns" id="columns_product_product_default_code">
+.. i18n: <field name="name">default_code</field>
+.. i18n: <field name="column_db_name">default_code</field>
+.. i18n: <field name="type">varchar</field>
+.. i18n: <field name="table_id" ref="table_product_template>
+.. i18n: <field name="active">True</field>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.database.columns" id="columns_product_product_default_code">
+ <field name="name">default_code</field>
+ <field name="column_db_name">default_code</field>
+ <field name="type">varchar</field>
+ <field name="table_id" ref="table_product_template>
+ <field name="active">True</field>
+ </record>
+
+.. i18n: Now, level.
+..
+
+Now, level.
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.level" id="level_product_template">
+.. i18n: <field name="name">default_code</field>
+.. i18n: <field name="column_name" ref="columns_product_product_default_code"></field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_product_template"/>
+.. i18n: <field name="table_name">res_partner</field>
+.. i18n: <field name="column_id_name">name</field>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.level" id="level_product_template">
+ <field name="name">default_code</field>
+ <field name="column_name" ref="columns_product_product_default_code"></field>
+ <field name="hierarchy_id" ref="hierarchy_product_template"/>
+ <field name="table_name">res_partner</field>
+ <field name="column_id_name">name</field>
+ </record>
+
+.. i18n: **Step: 6 Creating Dimension date_order up to the quarters**
+..
+
+**Step: 6 Creating Dimension date_order up to the quarters**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.dimension" id="dimension_sales_order">
+.. i18n: <field name="name">Order Date</field>
+.. i18n: <field name="cube_id" ref="cube_sales_order_line"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_sales_order">
+.. i18n: <field name="name">sale_order</field>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.hierarchy" id="hierarchy_sales_order">
+.. i18n: <field name="name">Order Date</field>
+.. i18n: <field name="dimension_id" ref="dimension_sales_order"/>
+.. i18n: <field name="primary_key_table">sale_order</field>
+.. i18n: <field name="table_id" ref="table_sales_order"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.database.columns" id="columns_sale_order_date_order">
+.. i18n: <field name="name">date_order</field>
+.. i18n: <field name="column_db_name">date_order</field>
+.. i18n: <field name="type">date</field>
+.. i18n: <field name="table_id" ref="table_sale_order"/>
+.. i18n: <field name="active">True</field>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.dimension" id="dimension_sales_order">
+ <field name="name">Order Date</field>
+ <field name="cube_id" ref="cube_sales_order_line"/>
+ </record>
+
+ <record model="olap.cube.table" id="table_sales_order">
+ <field name="name">sale_order</field>
+ </record>
+
+ <record model="olap.hierarchy" id="hierarchy_sales_order">
+ <field name="name">Order Date</field>
+ <field name="dimension_id" ref="dimension_sales_order"/>
+ <field name="primary_key_table">sale_order</field>
+ <field name="table_id" ref="table_sales_order"/>
+ </record>
+
+ <record model="olap.database.columns" id="columns_sale_order_date_order">
+ <field name="name">date_order</field>
+ <field name="column_db_name">date_order</field>
+ <field name="type">date</field>
+ <field name="table_id" ref="table_sale_order"/>
+ <field name="active">True</field>
+ </record>
+
+.. i18n: Making levels in Order Date so to get details as per year, quarters and months.
+..
+
+Making levels in Order Date so to get details as per year, quarters and months.
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.level" id="level_sales_order">
+.. i18n: <field name="name">date_order</field>
+.. i18n: <field name="column_name" ref="columns_sale_order_date_order"></field>
+.. i18n: <field name="column_id_name">date_order</field>
+.. i18n: <field name="type">date_year</field>
+.. i18n: <field name="sequence">1</field>
+.. i18n: <field name="table_name">sale_order</field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_sales_order"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.level" id="level_sales_order_q">
+.. i18n: <field name="name">date_order</field>
+.. i18n: <field name="column_name" ref="columns_sale_order_date_order"></field>
+.. i18n: <field name="column_id_name">date_order</field>
+.. i18n: <field name="type">date_quarter</field>
+.. i18n: <field name="sequence">2</field>
+.. i18n: <field name="table_name">sale_order</field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_sales_order"/>
+.. i18n: </record>
+.. i18n: <record model="olap.level" id="level_sales_order_m">
+.. i18n: <field name="name">date_order</field>
+.. i18n: <field name="column_name" ref="columns_sale_order_date_order"></field>
+.. i18n: <field name="column_id_name">date_order</field>
+.. i18n: <field name="type">date_month</field>
+.. i18n: <field name="sequence">3</field>
+.. i18n: <field name="table_name">sale_order</field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_sales_order"/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.level" id="level_sales_order">
+ <field name="name">date_order</field>
+ <field name="column_name" ref="columns_sale_order_date_order"></field>
+ <field name="column_id_name">date_order</field>
+ <field name="type">date_year</field>
+ <field name="sequence">1</field>
+ <field name="table_name">sale_order</field>
+ <field name="hierarchy_id" ref="hierarchy_sales_order"/>
+ </record>
+
+ <record model="olap.level" id="level_sales_order_q">
+ <field name="name">date_order</field>
+ <field name="column_name" ref="columns_sale_order_date_order"></field>
+ <field name="column_id_name">date_order</field>
+ <field name="type">date_quarter</field>
+ <field name="sequence">2</field>
+ <field name="table_name">sale_order</field>
+ <field name="hierarchy_id" ref="hierarchy_sales_order"/>
+ </record>
+ <record model="olap.level" id="level_sales_order_m">
+ <field name="name">date_order</field>
+ <field name="column_name" ref="columns_sale_order_date_order"></field>
+ <field name="column_id_name">date_order</field>
+ <field name="type">date_month</field>
+ <field name="sequence">3</field>
+ <field name="table_name">sale_order</field>
+ <field name="hierarchy_id" ref="hierarchy_sales_order"/>
+ </record>
+
+.. i18n: **Step: 7 Creating Dimension res_country**
+..
+
+**Step: 7 Creating Dimension res_country**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_sale_order">
+.. i18n: <field name="name">sale_order</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_partner_address_0">
+.. i18n: <field name="name">res_partner_address</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+.. i18n: <record model="olap.cube.table" id="table_partner_address_1">
+.. i18n: <field name="name">res_country</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_partner_address">
+.. i18n: <field name="name">res_partner_address</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_partner_country">
+.. i18n: <field name="name">sale_order_country</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.dimension" id="dimension_partner_country">
+.. i18n: <field name="name">Sales From Partners</field>
+.. i18n: <field name="cube_id" ref="cube_sales_order_line"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.hierarchy" id="hierarchy_partner_country">
+.. i18n: <field name="name">partner_country</field>
+.. i18n: <field name="dimension_id" ref="dimension_partner_country"/>
+.. i18n: <field name="primary_key_table">sale_order</field>
+.. i18n: <field name="table_id" ref="table_partner_country"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.level" id="level_partner_country">
+.. i18n: <field name="name">country_id</field>
+.. i18n: <field name="column_name" ref="columns_sale_order_date_order"></field>
+.. i18n: <field name="column_id_name">name</field>
+.. i18n: <field name="table_name">res_country</field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_partner_country"/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.cube.table" id="table_sale_order">
+ <field name="name">sale_order</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+
+ <record model="olap.cube.table" id="table_partner_address_0">
+ <field name="name">res_partner_address</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+ <record model="olap.cube.table" id="table_partner_address_1">
+ <field name="name">res_country</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+
+ <record model="olap.cube.table" id="table_partner_address">
+ <field name="name">res_partner_address</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+
+ <record model="olap.cube.table" id="table_partner_country">
+ <field name="name">sale_order_country</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+
+ <record model="olap.dimension" id="dimension_partner_country">
+ <field name="name">Sales From Partners</field>
+ <field name="cube_id" ref="cube_sales_order_line"/>
+ </record>
+
+ <record model="olap.hierarchy" id="hierarchy_partner_country">
+ <field name="name">partner_country</field>
+ <field name="dimension_id" ref="dimension_partner_country"/>
+ <field name="primary_key_table">sale_order</field>
+ <field name="table_id" ref="table_partner_country"/>
+ </record>
+
+ <record model="olap.level" id="level_partner_country">
+ <field name="name">country_id</field>
+ <field name="column_name" ref="columns_sale_order_date_order"></field>
+ <field name="column_id_name">name</field>
+ <field name="table_name">res_country</field>
+ <field name="hierarchy_id" ref="hierarchy_partner_country"/>
+ </record>
+
+.. i18n: **Step: 8 Creating Dimension res_partner_address**
+..
+
+**Step: 8 Creating Dimension res_partner_address**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.database.columns" id="columns_res_partner_address">
+.. i18n: <field name="name">name</field>
+.. i18n: <field name="column_db_name">name</field>
+.. i18n: <field name="type">varchar</field>
+.. i18n: <field name="table_id" ref="table_sales_order"/>
+.. i18n: <field name="active">True</field>
+.. i18n: </record>
+.. i18n: <record model="olap.cube.table" id="table_address">
+.. i18n: <field name="name">res_partner_address</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_address_country">
+.. i18n: <field name="name">sale_order_country</field>
+.. i18n: <field name='schema_id' ref='schema_main_sales'/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.dimension" id="dimension_partner_address_country">
+.. i18n: <field name="name">Sales by Order Address</field>
+.. i18n: <field name="cube_id" ref="cube_sales_order_line"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.hierarchy" id="hierarchy_partner_address_country">
+.. i18n: <field name="name">address_country</field>
+.. i18n: <field name="dimension_id" ref="dimension_partner_address_country"/>
+.. i18n: <field name="primary_key_table">sale_order</field>
+.. i18n: <field name="table_id" ref="table_address_country"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.level" id="level_address_country">
+.. i18n: <field name="name">country_id</field>
+.. i18n: <field name="sequence">1</field>
+.. i18n: <field name="column_name" ref="columns_res_partner_address"></field>
+.. i18n: <field name="column_id_name">country_id</field>
+.. i18n: <field name="table_name">res_partner_address</field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_partner_address_country"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.level" id="level_address_partner">
+.. i18n: <field name="name">partner_id</field>
+.. i18n: <field name="sequence">2</field>
+.. i18n: <field name="column_name" ref="columns_res_partner_address"></field>
+.. i18n: <field name="column_id_name">partner_id</field>
+.. i18n: <field name="table_name">res_partner_address</field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_partner_address_country"/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.database.columns" id="columns_res_partner_address">
+ <field name="name">name</field>
+ <field name="column_db_name">name</field>
+ <field name="type">varchar</field>
+ <field name="table_id" ref="table_sales_order"/>
+ <field name="active">True</field>
+ </record>
+ <record model="olap.cube.table" id="table_address">
+ <field name="name">res_partner_address</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+
+ <record model="olap.cube.table" id="table_address_country">
+ <field name="name">sale_order_country</field>
+ <field name='schema_id' ref='schema_main_sales'/>
+ </record>
+
+ <record model="olap.dimension" id="dimension_partner_address_country">
+ <field name="name">Sales by Order Address</field>
+ <field name="cube_id" ref="cube_sales_order_line"/>
+ </record>
+
+ <record model="olap.hierarchy" id="hierarchy_partner_address_country">
+ <field name="name">address_country</field>
+ <field name="dimension_id" ref="dimension_partner_address_country"/>
+ <field name="primary_key_table">sale_order</field>
+ <field name="table_id" ref="table_address_country"/>
+ </record>
+
+ <record model="olap.level" id="level_address_country">
+ <field name="name">country_id</field>
+ <field name="sequence">1</field>
+ <field name="column_name" ref="columns_res_partner_address"></field>
+ <field name="column_id_name">country_id</field>
+ <field name="table_name">res_partner_address</field>
+ <field name="hierarchy_id" ref="hierarchy_partner_address_country"/>
+ </record>
+
+ <record model="olap.level" id="level_address_partner">
+ <field name="name">partner_id</field>
+ <field name="sequence">2</field>
+ <field name="column_name" ref="columns_res_partner_address"></field>
+ <field name="column_id_name">partner_id</field>
+ <field name="table_name">res_partner_address</field>
+ <field name="hierarchy_id" ref="hierarchy_partner_address_country"/>
+ </record>
+
+.. i18n: **Step: 9 Creating Dimension res_user**
+..
+
+**Step: 9 Creating Dimension res_user**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.database.columns" id="columns_res_user_name">
+.. i18n: <field name="name">name</field>
+.. i18n: <field name="column_db_name">name</field>
+.. i18n: <field name="type">varchar</field>
+.. i18n: <field name="table_id" ref="table_sales_order"/>
+.. i18n: <field name="active">True</field>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.dimension" id="dimension_sales_user">
+.. i18n: <field name="name">user</field>
+.. i18n: <field name="cube_id" ref="cube_sales_order_line"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.cube.table" id="table_sales_res_users">
+.. i18n: <field name="name">res_users</field>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.hierarchy" id="hierarchy_sales_user">
+.. i18n: <field name="name">user</field>
+.. i18n: <field name="dimension_id" ref="dimension_sales_user"/>
+.. i18n: <field name="primary_key_table">res_users</field>
+.. i18n: <field name="table_id" ref="table_sales_res_users"/>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.level" id="hierarchy_sales_user_level">
+.. i18n: <field name="name">name</field>
+.. i18n: <field name="column_name" ref="columns_res_user_name""></field>
+.. i18n: <field name="hierarchy_id" ref="hierarchy_sales_user"/>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.database.columns" id="columns_res_user_name">
+ <field name="name">name</field>
+ <field name="column_db_name">name</field>
+ <field name="type">varchar</field>
+ <field name="table_id" ref="table_sales_order"/>
+ <field name="active">True</field>
+ </record>
+
+ <record model="olap.dimension" id="dimension_sales_user">
+ <field name="name">user</field>
+ <field name="cube_id" ref="cube_sales_order_line"/>
+ </record>
+
+ <record model="olap.cube.table" id="table_sales_res_users">
+ <field name="name">res_users</field>
+ </record>
+
+ <record model="olap.hierarchy" id="hierarchy_sales_user">
+ <field name="name">user</field>
+ <field name="dimension_id" ref="dimension_sales_user"/>
+ <field name="primary_key_table">res_users</field>
+ <field name="table_id" ref="table_sales_res_users"/>
+ </record>
+
+ <record model="olap.level" id="hierarchy_sales_user_level">
+ <field name="name">name</field>
+ <field name="column_name" ref="columns_res_user_name""></field>
+ <field name="hierarchy_id" ref="hierarchy_sales_user"/>
+ </record>
+
+.. i18n: **Step: 10 Creating Measures Item Sold and Total Sold**
+..
+
+**Step: 10 Creating Measures Item Sold and Total Sold**
+
+.. i18n: .. code-block:: xml
+.. i18n:
+.. i18n: <record model="olap.database.columns" id="columns_sale_order_line_product_uom_qty">
+.. i18n: <field name="name">product_uom_qty</field>
+.. i18n: <field name="column_db_name">product_uom_qty</field>
+.. i18n: <field name="type">numeric</field>
+.. i18n: <field name="table_id" ref="table_sale_order_line"/>
+.. i18n: <field name="active">True</field>
+.. i18n: </record>
+.. i18n:
+.. i18n: <record model="olap.measure" id="measure_item_sold">
+.. i18n: <field name="name">Items Sold</field>
+.. i18n: <field name="cube_id" ref="cube_sales_order_line"/>
+.. i18n: <field name="value_column" ref="columns_sale_order_line_product_uom_qty"></field>
+.. i18n: <field name="value_column_id_name">product_uom_qty</field>
+.. i18n: <field name="table_name">sale_order_line</field>
+.. i18n: <field name="agregator">sum</field>
+.. i18n: </record>
+.. i18n: <record model="olap.measure" id="measure_total_sales">
+.. i18n: <field name="name">Total Sold</field>
+.. i18n: <field name="cube_id" ref="cube_sales_order_line"/>
+.. i18n: <field name="value_column" ref="columns_sale_order_line_price_unit"></field>
+.. i18n: <field name="value_column_id_name">price_unit</field>
+.. i18n: <field name="table_name">sale_order_line</field>
+.. i18n: <field name="agregator">sum</field>
+.. i18n: </record>
+..
+
+.. code-block:: xml
+
+ <record model="olap.database.columns" id="columns_sale_order_line_product_uom_qty">
+ <field name="name">product_uom_qty</field>
+ <field name="column_db_name">product_uom_qty</field>
+ <field name="type">numeric</field>
+ <field name="table_id" ref="table_sale_order_line"/>
+ <field name="active">True</field>
+ </record>
+
+ <record model="olap.measure" id="measure_item_sold">
+ <field name="name">Items Sold</field>
+ <field name="cube_id" ref="cube_sales_order_line"/>
+ <field name="value_column" ref="columns_sale_order_line_product_uom_qty"></field>
+ <field name="value_column_id_name">product_uom_qty</field>
+ <field name="table_name">sale_order_line</field>
+ <field name="agregator">sum</field>
+ </record>
+ <record model="olap.measure" id="measure_total_sales">
+ <field name="name">Total Sold</field>
+ <field name="cube_id" ref="cube_sales_order_line"/>
+ <field name="value_column" ref="columns_sale_order_line_price_unit"></field>
+ <field name="value_column_id_name">price_unit</field>
+ <field name="table_name">sale_order_line</field>
+ <field name="agregator">sum</field>
+ </record>
=== added file 'i18n/zh_CN/source/bi/CubeXML/CubeXMLIntro.rst'
--- i18n/zh_CN/source/bi/CubeXML/CubeXMLIntro.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/CubeXML/CubeXMLIntro.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,105 @@
+
+.. i18n: XML in open object
+.. i18n: ==================
+..
+
+XML in open object
+==================
+
+.. i18n: Introduction to the OpenObject Module
+.. i18n: -------------------------------------
+..
+
+Introduction to the OpenObject Module
+-------------------------------------
+
+.. i18n: The :ref:`OLAP <olap-link>` module is used to validate, run and format the output of *MDXExamples/MDX Queries*
+..
+
+The :ref:`OLAP <olap-link>` module is used to validate, run and format the output of *MDXExamples/MDX Queries*
+
+.. i18n: The general flow is of :ref:`OLAP <olap-link>` module is shown in following diagram:
+..
+
+The general flow is of :ref:`OLAP <olap-link>` module is shown in following diagram:
+
+.. i18n: .. image:: images/Cube_olap_schema.png
+..
+
+.. image:: images/Cube_olap_schema.png
+
+.. i18n: Explanation of the components
+.. i18n: -----------------------------
+..
+
+Explanation of the components
+-----------------------------
+
+.. i18n: :Web-Services:
+..
+
+:Web-Services:
+
+.. i18n: This is the layer provided by the base of OpenERP, protocols: NET-RPC (fast binary), XML-RPC, over HTTP or HTTPS
+..
+
+This is the layer provided by the base of OpenERP, protocols: NET-RPC (fast binary), XML-RPC, over HTTP or HTTPS
+
+.. i18n: :Services:
+..
+
+:Services:
+
+.. i18n: Layer provided by OpenERP that provides: authentication (normal/ldap), user management, access rights, workflows, module management, ...
+..
+
+Layer provided by OpenERP that provides: authentication (normal/ldap), user management, access rights, workflows, module management, ...
+
+.. i18n: :MDX Parser:
+..
+
+:MDX Parser:
+
+.. i18n: It parses the MDX query and converts it to the form of python objects. It uses Python's pyparsing module to do this. It splits the query into form of objects of axis, level, sub level, slicer (if any) and measures.
+..
+
+It parses the MDX query and converts it to the form of python objects. It uses Python's pyparsing module to do this. It splits the query into form of objects of axis, level, sub level, slicer (if any) and measures.
+
+.. i18n: :MDX Validator:
+..
+
+:MDX Validator:
+
+.. i18n: Parses all the objects created and maps it to the browse object of OpenERP resource. For example, the axis object will receive a link to the OpenERP browse record on the related olap.axis object.
+..
+
+Parses all the objects created and maps it to the browse object of OpenERP resource. For example, the axis object will receive a link to the OpenERP browse record on the related olap.axis object.
+
+.. i18n: :MDX Runner:
+..
+
+:MDX Runner:
+
+.. i18n: It will run the query on the basis of objects using SQLAlchemy and return different subsets.
+.. i18n: On the basis of it the cube is made in matrix form.
+.. i18n: And it fills the cube by values using axis mapping
+..
+
+It will run the query on the basis of objects using SQLAlchemy and return different subsets.
+On the basis of it the cube is made in matrix form.
+And it fills the cube by values using axis mapping
+
+.. i18n: :RDBMS connectors:
+..
+
+:RDBMS connectors:
+
+.. i18n: The layer provided by SQL Alchemy, it supports: mysql, postgresql, oracle, ...
+..
+
+The layer provided by SQL Alchemy, it supports: mysql, postgresql, oracle, ...
+
+.. i18n: The schema definition is in the OpenERP database.
+..
+
+The schema definition is in the OpenERP database.
=== added directory 'i18n/zh_CN/source/bi/CubeXML/images'
=== added file 'i18n/zh_CN/source/bi/CubeXML/images/Cube_olap_schema.png'
Binary files i18n/zh_CN/source/bi/CubeXML/images/Cube_olap_schema.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/CubeXML/images/Cube_olap_schema.png 2012-12-04 03:46:24 +0000 differ
=== added directory 'i18n/zh_CN/source/bi/MDXOverview'
=== added file 'i18n/zh_CN/source/bi/MDXOverview/MDXOverview.rst'
--- i18n/zh_CN/source/bi/MDXOverview/MDXOverview.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/MDXOverview/MDXOverview.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,151 @@
+
+.. i18n: MDXOverview
+.. i18n: ===========
+..
+
+MDXOverview
+===========
+
+.. i18n: MDX stands for Multidimensional Expressions. You use it to query OLAP databases. In a nutshell, MDX is to OLAP databases as SQL queries are to relational databases.
+..
+
+MDX stands for Multidimensional Expressions. You use it to query OLAP databases. In a nutshell, MDX is to OLAP databases as SQL queries are to relational databases.
+
+.. i18n: OLAP databases primarily consist of OLAP cubes, which store fact tables, measures (such as sales, purchase, etc.) and dimensions/hierarchies. An OLAP database is often an aggregation of a relational database; as a result, you can write MDX queries to retrieve key calculations that measure company performance, often with less code than standard SQL.
+..
+
+OLAP databases primarily consist of OLAP cubes, which store fact tables, measures (such as sales, purchase, etc.) and dimensions/hierarchies. An OLAP database is often an aggregation of a relational database; as a result, you can write MDX queries to retrieve key calculations that measure company performance, often with less code than standard SQL.
+
+.. i18n: Because of the nature of OLAP databases, we need to write MDX code to retrieve data in far fewer lines of code than would be required using SQL. This is a segue into the role that OLAP databases and MDX play in the world of business intelligence.
+..
+
+Because of the nature of OLAP databases, we need to write MDX code to retrieve data in far fewer lines of code than would be required using SQL. This is a segue into the role that OLAP databases and MDX play in the world of business intelligence.
+
+.. i18n: MDXAlchemy is developed taking care of all the aspects of becoming a complete OLAP Engine, to execute MDX query and fetch data efficiently. MDXAlchemy is a complete MDX engine that provides your database with full MDX capabilities.
+..
+
+MDXAlchemy is developed taking care of all the aspects of becoming a complete OLAP Engine, to execute MDX query and fetch data efficiently. MDXAlchemy is a complete MDX engine that provides your database with full MDX capabilities.
+
+.. i18n: MDXAlchemy use the services of SQLAlchemy to provide some of the important features that makes MDXAlchemy a fully capable MDX Engine. The major is removing the clause of database dependency.
+..
+
+MDXAlchemy use the services of SQLAlchemy to provide some of the important features that makes MDXAlchemy a fully capable MDX Engine. The major is removing the clause of database dependency.
+
+.. i18n: The dimensional meta data facility addresses the issue that although the application stores dimensional data in relational tables (usually in the form of fact and dimension tables), the user does not have to be aware of the dimensionality, or OLAP semantics, of this data. It provides a comprehensive meta data facility to define these semantics and an XML capability to enable meta data interchange with other external OLAP products.
+..
+
+The dimensional meta data facility addresses the issue that although the application stores dimensional data in relational tables (usually in the form of fact and dimension tables), the user does not have to be aware of the dimensionality, or OLAP semantics, of this data. It provides a comprehensive meta data facility to define these semantics and an XML capability to enable meta data interchange with other external OLAP products.
+
+.. i18n: Independent yet Integrated to OpenERP
+.. i18n: -------------------------------------
+..
+
+Independent yet Integrated to OpenERP
+-------------------------------------
+
+.. i18n: MDXAlchemy engine is totally independent of OpenERP and does not rely on OpenERP modules for its functionality.
+.. i18n: Yet being so diversified from OpenERP, it is fully integrated to OpenERP.
+..
+
+MDXAlchemy engine is totally independent of OpenERP and does not rely on OpenERP modules for its functionality.
+Yet being so diversified from OpenERP, it is fully integrated to OpenERP.
+
+.. i18n: MDXAlchemy can be installed/integrated as an internal module of OpenERP and make itself available to assist OpenERP.
+..
+
+MDXAlchemy can be installed/integrated as an internal module of OpenERP and make itself available to assist OpenERP.
+
+.. i18n: It is made of two major components, a cube engine and SQL Alchemy. It uses SQL Alchemy for connecting to the database while the cube engine processes the data to form the cube for the user.
+..
+
+It is made of two major components, a cube engine and SQL Alchemy. It uses SQL Alchemy for connecting to the database while the cube engine processes the data to form the cube for the user.
+
+.. i18n: Supported Databases
+.. i18n: -------------------
+..
+
+Supported Databases
+-------------------
+
+.. i18n: OpenObject BI takes care of independent database functionality.
+..
+
+OpenObject BI takes care of independent database functionality.
+
+.. i18n: It supports connectivity with most of the leading Database programs.
+..
+
+It supports connectivity with most of the leading Database programs.
+
+.. i18n: Just a compatible Dialect and valid connection parameters are all that is needed to use a database.
+..
+
+Just a compatible Dialect and valid connection parameters are all that is needed to use a database.
+
+.. i18n: The Dialect is used to describe how to talk to a specific kind of database. Dialects are included with SQLAlchemy for SQLite, Postgres, MySQL, MS-SQL, Firebird, Informix, and Oracle; these can be described as Python modules present in the sqlalchemy.databases package. Each dialect requires the appropriate DBAPI drivers to be installed separately.
+..
+
+The Dialect is used to describe how to talk to a specific kind of database. Dialects are included with SQLAlchemy for SQLite, Postgres, MySQL, MS-SQL, Firebird, Informix, and Oracle; these can be described as Python modules present in the sqlalchemy.databases package. Each dialect requires the appropriate DBAPI drivers to be installed separately.
+
+.. i18n: Downloads for each DBAPI to connect to supported Databases are as follows:
+..
+
+Downloads for each DBAPI to connect to supported Databases are as follows:
+
+.. i18n: * Postgres: psycopg2_
+.. i18n:
+.. i18n: * SQLite : pysqlite_
+.. i18n:
+.. i18n: * MySQL : MySQLDB_
+.. i18n:
+.. i18n: * Oracle : cx_Oracle_
+.. i18n:
+.. i18n: * MS-SQL : pyodbc_ (recommended) adodbapi pymssql
+.. i18n:
+.. i18n: * Firebird: kinterbasdb_
+.. i18n:
+.. i18n: * Informix: informixdb_
+..
+
+* Postgres: psycopg2_
+
+* SQLite : pysqlite_
+
+* MySQL : MySQLDB_
+
+* Oracle : cx_Oracle_
+
+* MS-SQL : pyodbc_ (recommended) adodbapi pymssql
+
+* Firebird: kinterbasdb_
+
+* Informix: informixdb_
+
+.. i18n: .. _psycopg2: http://www.initd.org/tracker/psycopg/wiki/PsycopgTwo
+.. i18n:
+.. i18n: .. _pysqlite: http://initd.org/tracker/pysqlite
+.. i18n:
+.. i18n: .. _MySQLDB: http://sourceforge.net/projects/mysql-python
+.. i18n:
+.. i18n: .. _cx_Oracle: http://www.cxtools.net/default.aspx?nav=home
+.. i18n:
+.. i18n: .. _pyodbc: http://pyodbc.sourceforge.net
+.. i18n:
+.. i18n: .. _kinterbasdb: http://kinterbasdb.sourceforge.net/
+.. i18n:
+.. i18n: .. _informixdb: http://informixdb.sourceforge.net/
+..
+
+.. _psycopg2: http://www.initd.org/tracker/psycopg/wiki/PsycopgTwo
+
+.. _pysqlite: http://initd.org/tracker/pysqlite
+
+.. _MySQLDB: http://sourceforge.net/projects/mysql-python
+
+.. _cx_Oracle: http://www.cxtools.net/default.aspx?nav=home
+
+.. _pyodbc: http://pyodbc.sourceforge.net
+
+.. _kinterbasdb: http://kinterbasdb.sourceforge.net/
+
+.. _informixdb: http://informixdb.sourceforge.net/
=== added file 'i18n/zh_CN/source/bi/MDXOverview/examples.rst'
--- i18n/zh_CN/source/bi/MDXOverview/examples.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/MDXOverview/examples.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,116 @@
+
+.. i18n: A look at few examples to write MDX Queries
+.. i18n: -------------------------------------------
+..
+
+A look at few examples to write MDX Queries
+-------------------------------------------
+
+.. i18n: Writing a simple MDX on a SALES Schema::
+.. i18n:
+.. i18n: select
+.. i18n: {[partner_country].[all]} on rows,
+.. i18n: {[measures].[Items Sold]} on columns
+.. i18n: from sale_order_line
+..
+
+Writing a simple MDX on a SALES Schema::
+
+ select
+ {[partner_country].[all]} on rows,
+ {[measures].[Items Sold]} on columns
+ from sale_order_line
+
+.. i18n: Gives results as,
+..
+
+Gives results as,
+
+.. i18n: ===================== ============
+.. i18n: / Items Sold
+.. i18n: ===================== ============
+.. i18n: All partner_country [43.0]
+.. i18n: ===================== ============
+..
+
+===================== ============
+ / Items Sold
+===================== ============
+ All partner_country [43.0]
+===================== ============
+
+.. i18n: Expanding the partner country to its children, we change the MDX as.::
+.. i18n:
+.. i18n: select
+.. i18n: {[partner_country].[all],[partner_country].children} on rows,
+.. i18n: {[measures].[Items Sold]} on columns
+.. i18n: from sale_order_line
+..
+
+Expanding the partner country to its children, we change the MDX as.::
+
+ select
+ {[partner_country].[all],[partner_country].children} on rows,
+ {[measures].[Items Sold]} on columns
+ from sale_order_line
+
+.. i18n: Gives result as,
+..
+
+Gives result as,
+
+.. i18n: ===================== ============
+.. i18n: / Items Sold
+.. i18n: ===================== ============
+.. i18n: All partner_country [43.0]
+.. i18n: Belgium [30.0]
+.. i18n: China [4.0]
+.. i18n: France [9.0]
+.. i18n: ===================== ============
+..
+
+===================== ============
+ / Items Sold
+===================== ============
+ All partner_country [43.0]
+ Belgium [30.0]
+ China [4.0]
+ France [9.0]
+===================== ============
+
+.. i18n: One more example bit complex with slicer::
+.. i18n:
+.. i18n: select
+.. i18n: {[date_order].children,[date_order].[2008].children,[date_order].[2008].[Q2].children},
+.. i18n: {[measures].[Items Sold]}
+.. i18n: from sale_order_line
+.. i18n: where ([date_order].[2008])
+..
+
+One more example bit complex with slicer::
+
+ select
+ {[date_order].children,[date_order].[2008].children,[date_order].[2008].[Q2].children},
+ {[measures].[Items Sold]}
+ from sale_order_line
+ where ([date_order].[2008])
+
+.. i18n: Gives results as:
+..
+
+Gives results as:
+
+.. i18n: ===================== ============
+.. i18n: / Items Sold
+.. i18n: ===================== ============
+.. i18n: 2008.0 [43.0]
+.. i18n: Q1 [43.0]
+.. i18n: ===================== ============
+..
+
+===================== ============
+ / Items Sold
+===================== ============
+ 2008.0 [43.0]
+ Q1 [43.0]
+===================== ============
=== added directory 'i18n/zh_CN/source/bi/architecture'
=== added file 'i18n/zh_CN/source/bi/architecture/architecture.rst'
--- i18n/zh_CN/source/bi/architecture/architecture.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/architecture/architecture.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,261 @@
+
+.. i18n: Schema
+.. i18n: ======
+..
+
+Schema
+======
+
+.. i18n: .. image:: images/Bi_arch.png
+..
+
+.. image:: images/Bi_arch.png
+
+.. i18n: Components
+.. i18n: ==========
+..
+
+Components
+==========
+
+.. i18n: The Cube
+.. i18n: --------
+..
+
+The Cube
+--------
+
+.. i18n: The cube is based of the following component:
+..
+
+The cube is based of the following component:
+
+.. i18n: * A MDX parser that will transform an MDX expression to RDBMs queries:
+.. i18n: - Computed using a mix of:
+.. i18n: + Using star flow snake as in mondrian (based on joins)
+.. i18n: + Using space hierarchy cutting like in cubulus
+.. i18n: * A memory cache system
+.. i18n: - On space hierarchies (dimensions with space cutting)
+.. i18n: * An aggregation system
+.. i18n: - Ability to create aggregated table to speed up all queries (automatic or user-defined)
+.. i18n: - Queries will be computed on fact tables or aggregated tables
+.. i18n: * A MDX Output (or several) to output the result
+..
+
+* A MDX parser that will transform an MDX expression to RDBMs queries:
+ - Computed using a mix of:
+ + Using star flow snake as in mondrian (based on joins)
+ + Using space hierarchy cutting like in cubulus
+* A memory cache system
+ - On space hierarchies (dimensions with space cutting)
+* An aggregation system
+ - Ability to create aggregated table to speed up all queries (automatic or user-defined)
+ - Queries will be computed on fact tables or aggregated tables
+* A MDX Output (or several) to output the result
+
+.. i18n: The cube will use:
+..
+
+The cube will use:
+
+.. i18n: * SQLAlchemy for all database communications
+.. i18n:
+.. i18n: * XML-RPC for his external interfaces
+.. i18n:
+.. i18n: * PyParser for MDX parsing
+..
+
+* SQLAlchemy for all database communications
+
+* XML-RPC for his external interfaces
+
+* PyParser for MDX parsing
+
+.. i18n: The CLI interface
+.. i18n: -----------------
+..
+
+The CLI interface
+-----------------
+
+.. i18n: Allows user to test MDX queries in this CLI command line interface. Simple script in python
+.. i18n: that will send XML-RPC queries and print the result.
+..
+
+Allows user to test MDX queries in this CLI command line interface. Simple script in python
+that will send XML-RPC queries and print the result.
+
+.. i18n: The Cube Definition
+.. i18n: -------------------
+..
+
+The Cube Definition
+-------------------
+
+.. i18n: The meta data of the cube definition will be stored in the OpenERP database. The user interface
+.. i18n: to edit cubes is in OpenERP. We will use the same concept of the one defined in the ... XML standard. So that we will be able, in a future phase, to import such files.
+..
+
+The meta data of the cube definition will be stored in the OpenERP database. The user interface
+to edit cubes is in OpenERP. We will use the same concept of the one defined in the ... XML standard. So that we will be able, in a future phase, to import such files.
+
+.. i18n: This must not depend on any module of OpenERP so that if you want to use the BI library independently, you may not use OpenERP if cubes are defined. If cubes are not defined, you just install the minimal version of OpenERP that includes: the olap module, user management, workflow managements, access rights management, ... (the base module)
+..
+
+This must not depend on any module of OpenERP so that if you want to use the BI library independently, you may not use OpenERP if cubes are defined. If cubes are not defined, you just install the minimal version of OpenERP that includes: the olap module, user management, workflow managements, access rights management, ... (the base module)
+
+.. i18n: The goal is that the user never have to create the cubes himself. We will create a wizard that
+.. i18n: will compute cubes based on introspection on the RDBM's. The steps of this wizard:
+..
+
+The goal is that the user never have to create the cubes himself. We will create a wizard that
+will compute cubes based on introspection on the RDBM's. The steps of this wizard:
+
+.. i18n: * Selection of the database (type of db, then selection box like in the login of OpenERP)
+.. i18n:
+.. i18n: * Selection of the factable (selection box)
+.. i18n:
+.. i18n: * Selection of the measures and their attributes (selection box, aggregation func)
+.. i18n:
+.. i18n: * Selection of the dimensions (click on a tree structure)
+..
+
+* Selection of the database (type of db, then selection box like in the login of OpenERP)
+
+* Selection of the factable (selection box)
+
+* Selection of the measures and their attributes (selection box, aggregation func)
+
+* Selection of the dimensions (click on a tree structure)
+
+.. i18n: Then it's done, the cube is computed. The aggregated table may be also automatically computed by OpenERP.
+..
+
+Then it's done, the cube is computed. The aggregated table may be also automatically computed by OpenERP.
+
+.. i18n: The goal is to create new cube on the fly from the OpenERP client on every object, on user demand. This will also server the online demo server.
+..
+
+The goal is to create new cube on the fly from the OpenERP client on every object, on user demand. This will also server the online demo server.
+
+.. i18n: The cube creation can be stored in the server of kept in memory for one time usage.
+..
+
+The cube creation can be stored in the server of kept in memory for one time usage.
+
+.. i18n: The Web Client
+.. i18n: --------------
+..
+
+The Web Client
+--------------
+
+.. i18n: The web client is a web-server that display cubes and provide tools to browse them, it must provide at least these operations:
+..
+
+The web client is a web-server that display cubes and provide tools to browse them, it must provide at least these operations:
+
+.. i18n: * switch view
+.. i18n:
+.. i18n: * different type of charts
+.. i18n:
+.. i18n: * drill up/down
+.. i18n:
+.. i18n: * slice
+.. i18n:
+.. i18n: * dice
+..
+
+* switch view
+
+* different type of charts
+
+* drill up/down
+
+* slice
+
+* dice
+
+.. i18n: The OpenOffice plugin
+.. i18n: ---------------------
+..
+
+The OpenOffice plugin
+---------------------
+
+.. i18n: Similar to Palo but all operation of construction and manipulation of cubes remains in OpenERP to limit development on OOo. The development on OOo just contains functions to:
+..
+
+Similar to Palo but all operation of construction and manipulation of cubes remains in OpenERP to limit development on OOo. The development on OOo just contains functions to:
+
+.. i18n: * Insert new data (based on selection of dimensions and filters)
+.. i18n:
+.. i18n: * Drill up/down functions
+.. i18n:
+.. i18n: * Slice function
+..
+
+* Insert new data (based on selection of dimensions and filters)
+
+* Drill up/down functions
+
+* Slice function
+
+.. i18n: The OpenERP interface
+.. i18n: -----------------------
+..
+
+The OpenERP interface
+-----------------------
+
+.. i18n: From OpenERP, you should be able to right click/drag and drop any field to trigger the cube definition wizard to create your own cube on demand. For this, we will use the web client of the bi system.
+..
+
+From OpenERP, you should be able to right click/drag and drop any field to trigger the cube definition wizard to create your own cube on demand. For this, we will use the web client of the bi system.
+
+.. i18n: We will integrate this on the gtk and web clients of OpenERP. The GTK client will open the browser to browse the cube.
+..
+
+We will integrate this on the gtk and web clients of OpenERP. The GTK client will open the browser to browse the cube.
+
+.. i18n: Extra libraries
+.. i18n: ===============
+..
+
+Extra libraries
+===============
+
+.. i18n: Libraries we will use:
+..
+
+Libraries we will use:
+
+.. i18n: * Turbogears for the web client to browse cube
+.. i18n:
+.. i18n: * Mathplotlib for rendering graphs
+.. i18n:
+.. i18n: * PyParsing to parse MDX Expressions
+.. i18n:
+.. i18n: * SQLAlchemy to construct SQL queries and RDBMS connections
+.. i18n:
+.. i18n: * XMLRPC lib for communication with the cube server
+.. i18n:
+.. i18n: * PÿUNO for the OOo integration
+..
+
+* Turbogears for the web client to browse cube
+
+* Mathplotlib for rendering graphs
+
+* PyParsing to parse MDX Expressions
+
+* SQLAlchemy to construct SQL queries and RDBMS connections
+
+* XMLRPC lib for communication with the cube server
+
+* PÿUNO for the OOo integration
+
+.. i18n: We will use an object relational mapping system on all objects: dimensions, ...
+..
+
+We will use an object relational mapping system on all objects: dimensions, ...
=== added directory 'i18n/zh_CN/source/bi/architecture/images'
=== added file 'i18n/zh_CN/source/bi/architecture/images/Bi_arch.png'
Binary files i18n/zh_CN/source/bi/architecture/images/Bi_arch.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/architecture/images/Bi_arch.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/architecture/images/Cube_olap_schema.png'
Binary files i18n/zh_CN/source/bi/architecture/images/Cube_olap_schema.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/architecture/images/Cube_olap_schema.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/architecture/openobject_module.rst'
--- i18n/zh_CN/source/bi/architecture/openobject_module.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/architecture/openobject_module.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,110 @@
+
+.. i18n: Introduction to the OpenObject Module
+.. i18n: =====================================
+..
+
+Introduction to the OpenObject Module
+=====================================
+
+.. i18n: The OLAP module is used to validate, run and format the output of MDXExamples
+..
+
+The OLAP module is used to validate, run and format the output of MDXExamples
+
+.. i18n: The following diagram shows the general flow of the OLAP module:
+..
+
+The following diagram shows the general flow of the OLAP module:
+
+.. i18n: .. image:: images/Cube_olap_schema.png
+..
+
+.. image:: images/Cube_olap_schema.png
+
+.. i18n: Explanation of the components
+.. i18n: -----------------------------
+..
+
+Explanation of the components
+-----------------------------
+
+.. i18n: Web-Services
+.. i18n: ++++++++++++
+..
+
+Web-Services
+++++++++++++
+
+.. i18n: This is the layer provided by the base of OpenERP, protocols: NET-RPC (fast binary), XML-RPC, over HTTP or HTTPS
+..
+
+This is the layer provided by the base of OpenERP, protocols: NET-RPC (fast binary), XML-RPC, over HTTP or HTTPS
+
+.. i18n: Services
+.. i18n: ++++++++
+..
+
+Services
+++++++++
+
+.. i18n: Layer provided by OpenERP that provides: authentication (normal/ldap), user management, access rights, workflows, module management, ...
+..
+
+Layer provided by OpenERP that provides: authentication (normal/ldap), user management, access rights, workflows, module management, ...
+
+.. i18n: MDX Parser
+.. i18n: ++++++++++
+..
+
+MDX Parser
+++++++++++
+
+.. i18n: It parses the MDX query and converts it to the form of python objects. It uses Python's pyparsing module to do this. It splits the query into form of objects of axis, level, sub level, slicer (if any) and measures.
+..
+
+It parses the MDX query and converts it to the form of python objects. It uses Python's pyparsing module to do this. It splits the query into form of objects of axis, level, sub level, slicer (if any) and measures.
+
+.. i18n: MDX Validator
+.. i18n: +++++++++++++
+..
+
+MDX Validator
++++++++++++++
+
+.. i18n: Parses all the objects created and maps it to the browse object of OpenERP resource. For example, the axis object will receive a link to the OpenERP browse record on the related olap.axis object.
+..
+
+Parses all the objects created and maps it to the browse object of OpenERP resource. For example, the axis object will receive a link to the OpenERP browse record on the related olap.axis object.
+
+.. i18n: MDX Runner
+.. i18n: ++++++++++
+..
+
+MDX Runner
+++++++++++
+
+.. i18n: It will run the query on the basis of objects using SQLAlchemy and return different subsets.
+.. i18n: On the basis of it the cube is made in matrix form.
+.. i18n: And it fills the cube by values using axis mapping
+..
+
+It will run the query on the basis of objects using SQLAlchemy and return different subsets.
+On the basis of it the cube is made in matrix form.
+And it fills the cube by values using axis mapping
+
+.. i18n: RDBMS connectors
+.. i18n: ++++++++++++++++
+..
+
+RDBMS connectors
+++++++++++++++++
+
+.. i18n: The layer provided by SQL Alchemy, it supports: mysql, postgresql, oracle, ...
+..
+
+The layer provided by SQL Alchemy, it supports: mysql, postgresql, oracle, ...
+
+.. i18n: The schema definition is in the OpenERP database.
+..
+
+The schema definition is in the OpenERP database.
=== added directory 'i18n/zh_CN/source/bi/config_interface'
=== added file 'i18n/zh_CN/source/bi/config_interface/config_interface.rst'
--- i18n/zh_CN/source/bi/config_interface/config_interface.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/config_interface/config_interface.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,362 @@
+
+.. i18n: Configuration Interface
+.. i18n: =======================
+..
+
+Configuration Interface
+=======================
+
+.. i18n: The main goal of any user connecting to OpenObject BI is to fetch the data from database using the powerful MDX queries.
+..
+
+The main goal of any user connecting to OpenObject BI is to fetch the data from database using the powerful MDX queries.
+
+.. i18n: To run any MDX Query there is a need to make a cube and the user can define / configure their own custom cube using two interface :
+..
+
+To run any MDX Query there is a need to make a cube and the user can define / configure their own custom cube using two interface :
+
+.. i18n: .. _schema_configuration-link:
+.. i18n:
+.. i18n: Introduction
+.. i18n: ----------------------------------
+..
+
+.. _schema_configuration-link:
+
+Introduction
+----------------------------------
+
+.. i18n: By default the Cube Designer displays all schema in the tree form and provide options to add new schema:
+..
+
+By default the Cube Designer displays all schema in the tree form and provide options to add new schema:
+
+.. i18n: .. image:: images/1.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/1.png
+ :scale: 65
+
+.. i18n: --------
+..
+
+--------
+
+.. i18n: Creating the Schema : Schema defines the database from where the data is to be fetched. It gives a meaningful name to the database connection:
+..
+
+Creating the Schema : Schema defines the database from where the data is to be fetched. It gives a meaningful name to the database connection:
+
+.. i18n: .. image:: images/2.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+.. i18n:
+.. i18n:
+.. i18n: Database Connection specifies the parameters for connecting to the database. It generally includes type of the database (postgres, oracle, mysql), username, password, database to use:
+..
+
+.. image:: images/2.png
+ :scale: 65
+
+--------
+
+
+Database Connection specifies the parameters for connecting to the database. It generally includes type of the database (postgres, oracle, mysql), username, password, database to use:
+
+.. i18n: .. image:: images/3.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+..
+
+.. image:: images/3.png
+ :scale: 65
+
+--------
+
+.. i18n: Once we configure the database connection the next step is to load the database using introspection. This will load the structure of the database. By structure we mean tables, columns and the relations. This will help in defining cube easily. As the structure is loaded there will be no query to the database again and again:
+..
+
+Once we configure the database connection the next step is to load the database using introspection. This will load the structure of the database. By structure we mean tables, columns and the relations. This will help in defining cube easily. As the structure is loaded there will be no query to the database again and again:
+
+.. i18n: .. image:: images/4.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+..
+
+.. image:: images/4.png
+ :scale: 65
+
+--------
+
+.. i18n: The next step is to configure the loaded database. This is useful to hide unnecessary table and columns. If database is from OpenERP it can be auto-configured:
+..
+
+The next step is to configure the loaded database. This is useful to hide unnecessary table and columns. If database is from OpenERP it can be auto-configured:
+
+.. i18n: .. image:: images/4a.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+.. i18n:
+.. i18n:
+.. i18n: Once the cube schema is created we can start creating the cube:
+..
+
+.. image:: images/4a.png
+ :scale: 65
+
+--------
+
+
+Once the cube schema is created we can start creating the cube:
+
+.. i18n: .. image:: images/5.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+.. i18n:
+.. i18n:
+.. i18n: Cube is the structure that is based on the schema (database), it will configure how to retrieve the data:
+..
+
+.. image:: images/5.png
+ :scale: 65
+
+--------
+
+
+Cube is the structure that is based on the schema (database), it will configure how to retrieve the data:
+
+.. i18n: .. image:: images/6.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+..
+
+.. image:: images/6.png
+ :scale: 65
+
+--------
+
+.. i18n: Cube requires the fact table to be defined. Fact tables are the key tables in which measures are stored and we can branch to other tables for other parameters. For example for sales we can define sale_order as our fact table as it will give the details of the sales. Fact table can be join of tables.
+.. i18n: The fact table is given a meaningful name:
+..
+
+Cube requires the fact table to be defined. Fact tables are the key tables in which measures are stored and we can branch to other tables for other parameters. For example for sales we can define sale_order as our fact table as it will give the details of the sales. Fact table can be join of tables.
+The fact table is given a meaningful name:
+
+.. i18n: .. image:: images/7.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+.. i18n:
+.. i18n:
+.. i18n: And the cube screen will be
+..
+
+.. image:: images/7.png
+ :scale: 65
+
+--------
+
+
+And the cube screen will be
+
+.. i18n: .. image:: images/8.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+..
+
+.. image:: images/8.png
+ :scale: 65
+
+--------
+
+.. i18n: After cube we can decide upon the dimensions to be used for the cube. For example we want to look on products sold, Dates, City etc. to analyse the sales accordingly.
+.. i18n: We decide the measures to be used, for example items sold. So we can decide the dimension and measures:
+..
+
+After cube we can decide upon the dimensions to be used for the cube. For example we want to look on products sold, Dates, City etc. to analyse the sales accordingly.
+We decide the measures to be used, for example items sold. So we can decide the dimension and measures:
+
+.. i18n: .. image:: images/9.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+..
+
+.. image:: images/9.png
+ :scale: 65
+
+--------
+
+.. i18n: Adding the dimension Products. So we will be able to see product wise item sold:
+..
+
+Adding the dimension Products. So we will be able to see product wise item sold:
+
+.. i18n: .. image:: images/10.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/10.png
+ :scale: 65
+
+.. i18n: After dimension we explain how to get the products details in the hierarchy. That requires configuring the fact table:
+..
+
+After dimension we explain how to get the products details in the hierarchy. That requires configuring the fact table:
+
+.. i18n: .. image:: images/12.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+..
+
+.. image:: images/12.png
+ :scale: 65
+
+--------
+
+.. i18n: After adding the hierarchy we decide from which field the product name will come:
+..
+
+After adding the hierarchy we decide from which field the product name will come:
+
+.. i18n: .. image:: images/14.png
+.. i18n: :scale: 65
+.. i18n:
+.. i18n: --------
+..
+
+.. image:: images/14.png
+ :scale: 65
+
+--------
+
+.. i18n: The fully configured cube tree will look like:
+..
+
+The fully configured cube tree will look like:
+
+.. i18n: .. image:: images/15.png
+.. i18n: :scale: 65
+..
+
+.. image:: images/15.png
+ :scale: 65
+
+.. i18n: Connecting to an Existing Database
+.. i18n: ----------------------------------
+..
+
+Connecting to an Existing Database
+----------------------------------
+
+.. i18n: One can very easily connect to an existing database. The details required are
+..
+
+One can very easily connect to an existing database. The details required are
+
+.. i18n: #. Fact Name : Logical Name of the database
+.. i18n:
+.. i18n: #. Database Name: Physical Database name to be used
+.. i18n:
+.. i18n: #. Database type : Type of the database it can be PostgreSQL, MySQL, Oracle etc.
+.. i18n:
+.. i18n: #. Connection type : Port or Socket
+.. i18n:
+.. i18n: #. Database Host : Server name like localhost
+.. i18n:
+.. i18n: #. Database Port : Port to be used for making connection to the database
+.. i18n:
+.. i18n: #. Database Login: Login name for accessing a database
+.. i18n:
+.. i18n: #. Database Password:Password for the user in login
+..
+
+#. Fact Name : Logical Name of the database
+
+#. Database Name: Physical Database name to be used
+
+#. Database type : Type of the database it can be PostgreSQL, MySQL, Oracle etc.
+
+#. Connection type : Port or Socket
+
+#. Database Host : Server name like localhost
+
+#. Database Port : Port to be used for making connection to the database
+
+#. Database Login: Login name for accessing a database
+
+#. Database Password:Password for the user in login
+
+.. i18n: ------
+..
+
+------
+
+.. i18n: Giving this detail will generate a string like ''postgres://postgres:postgres@localhost:5432/terp''
+..
+
+Giving this detail will generate a string like ''postgres://postgres:postgres@localhost:5432/terp''
+
+.. i18n: ------
+..
+
+------
+
+.. i18n: Strings so generated is a connection string for making connection to the database.
+..
+
+Strings so generated is a connection string for making connection to the database.
+
+.. i18n: Writing a Schema
+.. i18n: ----------------
+..
+
+Writing a Schema
+----------------
+
+.. i18n: .. describe:: What is Schema ?
+..
+
+.. describe:: What is Schema ?
+
+.. i18n: Schema means shape or, more generally, plan. In the context of OpenObject BI it defines the logical model, consisting of cubes, hierarchies, and members, and a mapping of this model onto a physical model.
+..
+
+Schema means shape or, more generally, plan. In the context of OpenObject BI it defines the logical model, consisting of cubes, hierarchies, and members, and a mapping of this model onto a physical model.
+
+.. i18n: The logical model consists of the constructs used to write queries in MDX language: cubes, dimensions, hierarchies, levels, and members.
+..
+
+The logical model consists of the constructs used to write queries in MDX language: cubes, dimensions, hierarchies, levels, and members.
+
+.. i18n: The physical model is the source of the data which is presented through the logical model. It is typically a star schema, which is a set of tables in a relational database; later, we shall see examples of other kinds of mappings.
+..
+
+The physical model is the source of the data which is presented through the logical model. It is typically a star schema, which is a set of tables in a relational database; later, we shall see examples of other kinds of mappings.
+
+.. i18n: Making Schema
+.. i18n: +++++++++++++
+..
+
+Making Schema
++++++++++++++
+
+.. i18n: In OpenObject BI schemas are represented in a XML file. It can be designed in the way OpenERP does. The details of XML file can be seen at *Creating XML*
+..
+
+In OpenObject BI schemas are represented in a XML file. It can be designed in the way OpenERP does. The details of XML file can be seen at *Creating XML*
+
+.. i18n:
+..
+
+
=== added directory 'i18n/zh_CN/source/bi/config_interface/images'
=== added file 'i18n/zh_CN/source/bi/config_interface/images/1.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/10.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/10.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/10.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/11.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/11.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/11.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/12.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/12.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/12.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/13.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/13.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/13.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/14.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/14.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/14.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/15.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/15.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/15.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/2.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/2.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/2.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/3.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/3.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/3.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/4.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/4.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/4.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/4a.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/4a.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/4a.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/5.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/5.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/5.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/6.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/6.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/6.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/7.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/7.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/7.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/8.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/8.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/8.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/config_interface/images/9.png'
Binary files i18n/zh_CN/source/bi/config_interface/images/9.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/bi/config_interface/images/9.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/bi/index.rst'
--- i18n/zh_CN/source/bi/index.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/index.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,218 @@
+
+.. i18n: .. _book-bi-link:
+.. i18n:
+.. i18n: Business Intelligence
+.. i18n: =====================
+..
+
+.. _book-bi-link:
+
+Business Intelligence
+=====================
+
+.. i18n: Part 1 : Introduction
+.. i18n: ---------------------
+..
+
+Part 1 : Introduction
+---------------------
+
+.. i18n: .. sidebar:: Experimental Application
+.. i18n:
+.. i18n: This chapter describes an experimental BI Application that is not part of the
+.. i18n: current quality-certified distribution of OpenERP.
+.. i18n: The BI modules can be found in `OpenERP Apps <http://apps.openerp.com>`_, but are
+.. i18n: not yet suitable for production use.
+..
+
+.. sidebar:: Experimental Application
+
+ This chapter describes an experimental BI Application that is not part of the
+ current quality-certified distribution of OpenERP.
+ The BI modules can be found in `OpenERP Apps <http://apps.openerp.com>`_, but are
+ not yet suitable for production use.
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: introduction/goals
+.. i18n: introduction/introduction
+.. i18n: introduction/olap
+.. i18n: introduction/terminologies
+.. i18n:
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ introduction/goals
+ introduction/introduction
+ introduction/olap
+ introduction/terminologies
+
+
+.. i18n: Part 2 : Architecture
+.. i18n: ---------------------
+..
+
+Part 2 : Architecture
+---------------------
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: architecture/architecture
+.. i18n: architecture/openobject_module
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ architecture/architecture
+ architecture/openobject_module
+
+.. i18n: Part 3 : MDXAlchemy
+.. i18n: ---------------------
+..
+
+Part 3 : MDXAlchemy
+---------------------
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: MDXOverview/MDXOverview
+.. i18n: MDXOverview/examples
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ MDXOverview/MDXOverview
+ MDXOverview/examples
+
+.. i18n: Part 4 : Installing
+.. i18n: ---------------------
+..
+
+Part 4 : Installing
+---------------------
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: installation/installation
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ installation/installation
+
+.. i18n: Part 5 : Configuration
+.. i18n: ----------------------
+..
+
+Part 5 : Configuration
+----------------------
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: config_interface/config_interface
+.. i18n: CubeXML/CubeXML
+.. i18n: CubeXML/CubeXMLIntro
+.. i18n: CubeXML/CubeXMLExample
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ config_interface/config_interface
+ CubeXML/CubeXML
+ CubeXML/CubeXMLIntro
+ CubeXML/CubeXMLExample
+
+.. i18n: Part 6 : Using CommandLine Interface (CLI)
+.. i18n: ------------------------------------------
+..
+
+Part 6 : Using CommandLine Interface (CLI)
+------------------------------------------
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: CubeCli/CubeCliIntro
+.. i18n: CubeCli/CubeCliTests
+.. i18n: CubeCli/CubeCliExample
+.. i18n: CubeCli/CubeCliXMLRPC
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ CubeCli/CubeCliIntro
+ CubeCli/CubeCliTests
+ CubeCli/CubeCliExample
+ CubeCli/CubeCliXMLRPC
+
+.. i18n: Part 7 : Using Cube Browser
+.. i18n: ----------------------------
+..
+
+Part 7 : Using Cube Browser
+----------------------------
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: CubeBrowser/CubeBrowser
+.. i18n: CubeBrowser/CubeBrowserSelect
+.. i18n: CubeBrowser/CubeBrowserDaD
+.. i18n: CubeBrowser/CubeBrowserSwap
+.. i18n: CubeBrowser/CubeBrowserSlicer
+.. i18n: CubeBrowser/CubeBrowserDrill
+.. i18n: CubeBrowser/CubeBrowserGraph
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ CubeBrowser/CubeBrowser
+ CubeBrowser/CubeBrowserSelect
+ CubeBrowser/CubeBrowserDaD
+ CubeBrowser/CubeBrowserSwap
+ CubeBrowser/CubeBrowserSlicer
+ CubeBrowser/CubeBrowserDrill
+ CubeBrowser/CubeBrowserGraph
+
+.. i18n: Part 8 : Using Cube Designer
+.. i18n: ----------------------------
+..
+
+Part 8 : Using Cube Designer
+----------------------------
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: CubeDesigner/CubeDesigner
+.. i18n: CubeDesigner/LoadingDB
+.. i18n: CubeDesigner/DefiningCube
+.. i18n: CubeDesigner/DefinigDim
+.. i18n: CubeDesigner/DefiningHier
+.. i18n: CubeDesigner/DefiningLevel
+.. i18n: CubeDesigner/DefiningMeas
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ CubeDesigner/CubeDesigner
+ CubeDesigner/LoadingDB
+ CubeDesigner/DefiningCube
+ CubeDesigner/DefinigDim
+ CubeDesigner/DefiningHier
+ CubeDesigner/DefiningLevel
+ CubeDesigner/DefiningMeas
=== added directory 'i18n/zh_CN/source/bi/installation'
=== added file 'i18n/zh_CN/source/bi/installation/install_olap.rst'
--- i18n/zh_CN/source/bi/installation/install_olap.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/installation/install_olap.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,119 @@
+
+.. i18n: .. _install-olap:
+.. i18n:
+.. i18n: Installation of Open Object
+.. i18n: ===========================
+..
+
+.. _install-olap:
+
+Installation of Open Object
+===========================
+
+.. i18n: To install BI we need to have :
+..
+
+To install BI we need to have :
+
+.. i18n: #. Getting and running `OpenERP Server`_
+.. i18n:
+.. i18n: #. Getting `SQLAlchemy-0.3.11`_
+..
+
+#. Getting and running `OpenERP Server`_
+
+#. Getting `SQLAlchemy-0.3.11`_
+
+.. i18n: Once everything is working i.e. OpenERP Server and OpenERP Client we need to add OLAP module in Server.
+..
+
+Once everything is working i.e. OpenERP Server and OpenERP Client we need to add OLAP module in Server.
+
+.. i18n: Steps to install OLAP modules.
+..
+
+Steps to install OLAP modules.
+
+.. i18n: For server module:
+..
+
+ For server module:
+
+.. i18n: * First install the Bazaar on your Linux box (apt-get install bzr) then “cd” to /usr/
+.. i18n: local/src folder or other, as you work usually.
+.. i18n: * Get the Launchpad’s BI branch with the command:
+.. i18n: From : https://code.launchpad.net/~openerp/openobject-addons/trunk bzr branch lp:openobject-addons This openobject-addons
+.. i18n: contain the bi in Olap modules
+..
+
+ * First install the Bazaar on your Linux box (apt-get install bzr) then “cd” to /usr/
+ local/src folder or other, as you work usually.
+ * Get the Launchpad’s BI branch with the command:
+ From : https://code.launchpad.net/~openerp/openobject-addons/trunk bzr branch lp:openobject-addons This openobject-addons
+ contain the bi in Olap modules
+
+.. i18n: For client-web-bi:
+.. i18n:
+.. i18n: * https://code.launchpad.net/~openerp-dev/openobject-client-web/trunk-dev-web-bi
+.. i18n: * bzr branch for client-web-bi lp:~openerp-dev/openobject-client-web/trunk-dev-web-bi
+.. i18n:
+.. i18n: * Get SQLAlchemy-x.x.x.tar.gz from sourceforge.net and untar (tar –xzvf file_name) it to
+.. i18n: the /usr/local/src folder then cd to /usr/local/src/ SQLAlchemy-x.x.x and run ‘’python
+.. i18n: setup.py install’’
+.. i18n:
+.. i18n: * The SQLAlchemy install will push all that we need to the /usr/lib/python2.5/site-
+.. i18n: packages/SQLAlchemy-0.5.2-py2.5.egg, ‘’cd’’ to this folder and do the “zip” like this:
+.. i18n:
+.. i18n: * zip /somewhere/sqlalchemy.zip -r sqlalchemy
+.. i18n:
+.. i18n: * Move or copy (mv or cp) the sqlachemy.zip to the openerp-server addons folder (/usr/lib
+.. i18n: /python2.5/site-packages/openerp -server/addons) and unzip the file within.
+.. i18n:
+.. i18n: * Check also the owner and the rights of ~/addons folder, as I run the openerp-server
+.. i18n: with postgres user I switched the ~/addons owner to ‘’chown -R postgres addons’’
+.. i18n:
+.. i18n: * Retrieve all the olap’s ‘’zip’’ files and import/install them to OpenERP v5.
+..
+
+ For client-web-bi:
+
+ * https://code.launchpad.net/~openerp-dev/openobject-client-web/trunk-dev-web-bi
+ * bzr branch for client-web-bi lp:~openerp-dev/openobject-client-web/trunk-dev-web-bi
+
+ * Get SQLAlchemy-x.x.x.tar.gz from sourceforge.net and untar (tar –xzvf file_name) it to
+ the /usr/local/src folder then cd to /usr/local/src/ SQLAlchemy-x.x.x and run ‘’python
+ setup.py install’’
+
+ * The SQLAlchemy install will push all that we need to the /usr/lib/python2.5/site-
+ packages/SQLAlchemy-0.5.2-py2.5.egg, ‘’cd’’ to this folder and do the “zip” like this:
+
+ * zip /somewhere/sqlalchemy.zip -r sqlalchemy
+
+ * Move or copy (mv or cp) the sqlachemy.zip to the openerp-server addons folder (/usr/lib
+ /python2.5/site-packages/openerp -server/addons) and unzip the file within.
+
+ * Check also the owner and the rights of ~/addons folder, as I run the openerp-server
+ with postgres user I switched the ~/addons owner to ‘’chown -R postgres addons’’
+
+ * Retrieve all the olap’s ‘’zip’’ files and import/install them to OpenERP v5.
+
+.. i18n: Setup install packages for Windows:
+.. i18n:
+.. i18n: * http://bazaar.launchpad.net/~openerp/openerp/win-installer-trunk/files/head%3A/dependencies/
+..
+
+ Setup install packages for Windows:
+
+ * http://bazaar.launchpad.net/~openerp/openerp/win-installer-trunk/files/head%3A/dependencies/
+
+.. i18n: =======
+..
+
+=======
+
+.. i18n: .. _OpenERP Server: http://openerp.com/wiki/index.php/InstallationManual/HomePage
+.. i18n: .. _SQLAlchemy-0.3.11: http://sourceforge.net/projects/sqlalchemy/ SQLAlchemy-0.3.11
+..
+
+.. _OpenERP Server: http://openerp.com/wiki/index.php/InstallationManual/HomePage
+.. _SQLAlchemy-0.3.11: http://sourceforge.net/projects/sqlalchemy/ SQLAlchemy-0.3.11
=== added file 'i18n/zh_CN/source/bi/installation/install_web.rst'
--- i18n/zh_CN/source/bi/installation/install_web.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/installation/install_web.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,35 @@
+
+.. i18n: .. _install-web-interface:
+.. i18n:
+.. i18n: Installing Web Interface
+.. i18n: ========================
+..
+
+.. _install-web-interface:
+
+Installing Web Interface
+========================
+
+.. i18n: To install the BI Web Interface you need:
+..
+
+To install the BI Web Interface you need:
+
+.. i18n: #. The latest version of Turbogears_
+.. i18n:
+.. i18n: #. The BI-web Client source code
+..
+
+#. The latest version of Turbogears_
+
+#. The BI-web Client source code
+
+.. i18n: To use the Web Client the server must be running.
+..
+
+To use the Web Client the server must be running.
+
+.. i18n: .. _Turbogears: http://www.turbogears.org/
+..
+
+.. _Turbogears: http://www.turbogears.org/
=== added file 'i18n/zh_CN/source/bi/installation/installation.rst'
--- i18n/zh_CN/source/bi/installation/installation.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/installation/installation.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,25 @@
+
+.. i18n: Installation of BI
+.. i18n: ==================
+..
+
+Installation of BI
+==================
+
+.. i18n: BI requires OpenERP Server and (preferably) OpenERP GTK client on the user system.
+..
+
+BI requires OpenERP Server and (preferably) OpenERP GTK client on the user system.
+
+.. i18n: .. toctree::
+.. i18n: :maxdepth: 2
+.. i18n:
+.. i18n: Installing OpenERP Server and OLAP module <install_olap>
+.. i18n: install_web
+..
+
+.. toctree::
+ :maxdepth: 2
+
+ Installing OpenERP Server and OLAP module <install_olap>
+ install_web
=== added directory 'i18n/zh_CN/source/bi/introduction'
=== added file 'i18n/zh_CN/source/bi/introduction/goals.rst'
--- i18n/zh_CN/source/bi/introduction/goals.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/introduction/goals.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,56 @@
+
+.. i18n: Goal of the project
+.. i18n: -------------------
+..
+
+Goal of the project
+-------------------
+
+.. i18n: In simple words Business Intelligence, or BI, is the act of capturing raw data, then transforming and combining that data into information that can be proactively used to improve business. So, the goal of BI is to empower decision-makers, allowing them to make better and faster decisions. After all **Better decisions make better business!**
+..
+
+In simple words Business Intelligence, or BI, is the act of capturing raw data, then transforming and combining that data into information that can be proactively used to improve business. So, the goal of BI is to empower decision-makers, allowing them to make better and faster decisions. After all **Better decisions make better business!**
+
+.. i18n: In general any Business Intelligence Solution must provide :
+..
+
+In general any Business Intelligence Solution must provide :
+
+.. i18n: #. The first challenge business intelligence faces is gathering the necessary data about the business. The key for gathering data is automating the process. Previously gathering data was costly and time consuming, but with modern computer systems it’s much easier to collect data from various sources.
+.. i18n:
+.. i18n: #. The second business intelligence task is to analyze the collected data and to extract information from it. The extracted information is then turned into business knowledge.
+.. i18n:
+.. i18n: #. The third and final business intelligence task is to use the newly gathered business knowledge to improve the business.
+..
+
+#. The first challenge business intelligence faces is gathering the necessary data about the business. The key for gathering data is automating the process. Previously gathering data was costly and time consuming, but with modern computer systems it’s much easier to collect data from various sources.
+
+#. The second business intelligence task is to analyze the collected data and to extract information from it. The extracted information is then turned into business knowledge.
+
+#. The third and final business intelligence task is to use the newly gathered business knowledge to improve the business.
+
+.. i18n: Our goal of OpenObject BI is to provide Python based BI solution that can :
+..
+
+Our goal of OpenObject BI is to provide Python based BI solution that can :
+
+.. i18n: #. Provide all BI functionality.
+.. i18n:
+.. i18n: #. Creating cube on the fly with minimum steps.
+.. i18n:
+.. i18n: #. Access any type of database to make Schema and Cube.
+.. i18n:
+.. i18n: #. Reports can be used directly in OpenOffice.
+.. i18n:
+.. i18n: #. Making everything as object for easy expandability.
+..
+
+#. Provide all BI functionality.
+
+#. Creating cube on the fly with minimum steps.
+
+#. Access any type of database to make Schema and Cube.
+
+#. Reports can be used directly in OpenOffice.
+
+#. Making everything as object for easy expandability.
=== added file 'i18n/zh_CN/source/bi/introduction/introduction.rst'
--- i18n/zh_CN/source/bi/introduction/introduction.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/introduction/introduction.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,128 @@
+
+.. i18n: What is for User?
+.. i18n: =================
+..
+
+What is for User?
+=================
+
+.. i18n: The Open Object Business Intelligence system aims to be a full featured open source Business Intelligence system written in Python. It implements a HOLAP (Hybrid OLAP = ROLAP + MOLAP) cube and a MDX query engine based on SQLAlchemy.
+..
+
+The Open Object Business Intelligence system aims to be a full featured open source Business Intelligence system written in Python. It implements a HOLAP (Hybrid OLAP = ROLAP + MOLAP) cube and a MDX query engine based on SQLAlchemy.
+
+.. i18n: Comparing to most current business intelligence software in the market, our goal is to produce a BI for the mid market. It has to be:
+..
+
+Comparing to most current business intelligence software in the market, our goal is to produce a BI for the mid market. It has to be:
+
+.. i18n: For the end-user:
+.. i18n: -----------------
+..
+
+For the end-user:
+-----------------
+
+.. i18n: * Easy and fast to use: a simple web-interface that has no dependencies and can be integrated in proprietary
+.. i18n: software. It should have an OpenOffice interface for complex dashboards creation.
+.. i18n: * Easy to install: auto-installation on Windows and Linux, with few dependencies.
+.. i18n: * Integrated and independent from OpenERP.
+..
+
+* Easy and fast to use: a simple web-interface that has no dependencies and can be integrated in proprietary
+ software. It should have an OpenOffice interface for complex dashboards creation.
+* Easy to install: auto-installation on Windows and Linux, with few dependencies.
+* Integrated and independent from OpenERP.
+
+.. i18n: For the administrator user:
+.. i18n: ---------------------------
+..
+
+For the administrator user:
+---------------------------
+
+.. i18n: * A cube designer within OpenERP
+.. i18n: * Easy to configure: Automatic cube definition (5 clicks, using introspection on database),
+.. i18n: * Easy to maintain: The application must be sufficiently intelligent that it requires no fine tuning in cube definition,
+.. i18n: runs well on bad indices, with no need for explicitly defined aggregated tables, or defined axes.
+.. i18n: * No intervention from developers: everything achievable through interfaces for end-user.
+..
+
+* A cube designer within OpenERP
+* Easy to configure: Automatic cube definition (5 clicks, using introspection on database),
+* Easy to maintain: The application must be sufficiently intelligent that it requires no fine tuning in cube definition,
+ runs well on bad indices, with no need for explicitly defined aggregated tables, or defined axes.
+* No intervention from developers: everything achievable through interfaces for end-user.
+
+.. i18n: For the developer:
+.. i18n: ------------------
+..
+
+For the developer:
+------------------
+
+.. i18n: * Everything (dimensions, ) must be object oriented with a module system to allow to add your own code to extend the software, like in OpenERP.
+.. i18n: * It must support main database engine and aggregation of multiple database: PostgreSQL, MySQL, Oracle, MSSQL etc... to do reporting for any application.
+..
+
+* Everything (dimensions, ) must be object oriented with a module system to allow to add your own code to extend the software, like in OpenERP.
+* It must support main database engine and aggregation of multiple database: PostgreSQL, MySQL, Oracle, MSSQL etc... to do reporting for any application.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Open SPRL (representing Open Object Presses) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Open SPRL (representing Open Object Presses) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and OpenERP Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and OpenERP Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by OpenERP Press, Grand Rosière, Belgium
+..
+
+.. Published by OpenERP Press, Grand Rosière, Belgium
=== added file 'i18n/zh_CN/source/bi/introduction/olap.rst'
--- i18n/zh_CN/source/bi/introduction/olap.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/introduction/olap.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,167 @@
+
+.. i18n: .. _olap-link:
+.. i18n:
+.. i18n: OLAP
+.. i18n: ====
+..
+
+.. _olap-link:
+
+OLAP
+====
+
+.. i18n: Online Analytical Processing (OLAP) means analysing large quantities of data in real-time. Unlike Online Transaction Processing (OLTP), where typical operations read and modify individual and small numbers of records, OLAP deals with data in bulk, and operations are generally read-only. The term 'online' implies that even though huge quantities of data are involved — typically many millions of records, occupying several gigabytes — the system must respond to queries fast enough to allow an interactive exploration of the data. As we shall see, that presents considerable technical challenges.
+..
+
+Online Analytical Processing (OLAP) means analysing large quantities of data in real-time. Unlike Online Transaction Processing (OLTP), where typical operations read and modify individual and small numbers of records, OLAP deals with data in bulk, and operations are generally read-only. The term 'online' implies that even though huge quantities of data are involved — typically many millions of records, occupying several gigabytes — the system must respond to queries fast enough to allow an interactive exploration of the data. As we shall see, that presents considerable technical challenges.
+
+.. i18n: OLAP performs multidimensional analysis of business data and provides the capability for complex calculations, trend analysis, and sophisticated data modeling. Whereas a relational database stores all data in the form of rows and columns, a multidimensional dataset consists of axes and cells.
+.. i18n: Consider the dataset
+..
+
+OLAP performs multidimensional analysis of business data and provides the capability for complex calculations, trend analysis, and sophisticated data modeling. Whereas a relational database stores all data in the form of rows and columns, a multidimensional dataset consists of axes and cells.
+Consider the dataset
+
+.. i18n: .. csv-table::
+.. i18n: :header: "Year",2000,,2001,,"Growth",
+.. i18n:
+.. i18n: "Product","Dollar sales","Unit sales","Dollar sales","Unit sales","Dollar sales","Unit sales"
+.. i18n: "Total","$7,073.00",2693,"$7,636.00",3008,8.00%,12.00%
+.. i18n: "Books","$2,753.00",824,"$3,331.00",966,21.00%,17.00%
+.. i18n: "Fiction","$1,341.00",424,"$1,202.00",380,-10.00%,-10.00%
+.. i18n: "Non-fiction","$1,412.00",400,"$2,129.00",586,51.00%,47.00%
+.. i18n: "Magazines","$2,753.00",824,"$2,426.00",766,-12.00%,-7.00%
+.. i18n: "Greetings cards","$1,567.00",1045,"$1,879.00",1276,20.00%,22.00%
+..
+
+.. csv-table::
+ :header: "Year",2000,,2001,,"Growth",
+
+ "Product","Dollar sales","Unit sales","Dollar sales","Unit sales","Dollar sales","Unit sales"
+ "Total","$7,073.00",2693,"$7,636.00",3008,8.00%,12.00%
+ "Books","$2,753.00",824,"$3,331.00",966,21.00%,17.00%
+ "Fiction","$1,341.00",424,"$1,202.00",380,-10.00%,-10.00%
+ "Non-fiction","$1,412.00",400,"$2,129.00",586,51.00%,47.00%
+ "Magazines","$2,753.00",824,"$2,426.00",766,-12.00%,-7.00%
+ "Greetings cards","$1,567.00",1045,"$1,879.00",1276,20.00%,22.00%
+
+.. i18n: The rows axis consists of the members 'All products', 'Books', 'Fiction', and so forth, and the columns axis consists of the cartesian product of the years '2000' and '2001', and the calculation 'Growth', and the measures 'Unit sales' and 'Dollar sales'. Each cell represents the sales of a product category in a particular year; for example, the dollar sales of Magazines in 2001 were $2,426.
+..
+
+The rows axis consists of the members 'All products', 'Books', 'Fiction', and so forth, and the columns axis consists of the cartesian product of the years '2000' and '2001', and the calculation 'Growth', and the measures 'Unit sales' and 'Dollar sales'. Each cell represents the sales of a product category in a particular year; for example, the dollar sales of Magazines in 2001 were $2,426.
+
+.. i18n: This is a richer view of the data than would be presented by a relational database. The members of a multidimensional dataset are not always values from a relational column. 'Total', 'Books' and 'Fiction' are members at successive levels in a hierarchy, each of which is rolled up to the next. And even though it is alongside the years '2000' and '2001', 'Growth' is a calculated member, which introduces a formula for computing cells from other cells.
+..
+
+This is a richer view of the data than would be presented by a relational database. The members of a multidimensional dataset are not always values from a relational column. 'Total', 'Books' and 'Fiction' are members at successive levels in a hierarchy, each of which is rolled up to the next. And even though it is alongside the years '2000' and '2001', 'Growth' is a calculated member, which introduces a formula for computing cells from other cells.
+
+.. i18n: The dimensions used here — products, time, and measures — are just three of many dimensions by which the dataset can be categorized and filtered. The collection of dimensions, hierarchies and measures is called a cube.
+..
+
+The dimensions used here — products, time, and measures — are just three of many dimensions by which the dataset can be categorized and filtered. The collection of dimensions, hierarchies and measures is called a cube.
+
+.. i18n: The above simple example or outlook shows how one can get the smallest details from the data stored for years in the database in form of relation. It helps in managing resources, forming policies , budgeting , Business Process Management, designing strategic marketing policies, forecasting and many more. The options are endless.
+..
+
+The above simple example or outlook shows how one can get the smallest details from the data stored for years in the database in form of relation. It helps in managing resources, forming policies , budgeting , Business Process Management, designing strategic marketing policies, forecasting and many more. The options are endless.
+
+.. i18n: The multidimensional is above all a way of presenting data. Although some multidimensional databases store the data in multidimensional format, I shall argue that it is simpler to store the data in relational format and manipulate it using OLAP.
+..
+
+The multidimensional is above all a way of presenting data. Although some multidimensional databases store the data in multidimensional format, I shall argue that it is simpler to store the data in relational format and manipulate it using OLAP.
+
+.. i18n: Who uses OLAP and Why?
+.. i18n: ----------------------
+..
+
+Who uses OLAP and Why?
+----------------------
+
+.. i18n: OLAP applications span a variety of organizational functions. Finance departments use OLAP for applications such as budgeting, activity-based costing (allocations), financial performance analysis, and financial modeling. Sales analysis and forecasting are two of the OLAP applications found in sales departments. Among other applications, marketing departments use OLAP for market research analysis, sales forecasting, promotions analysis, customer analysis, and market/customer segmentation. Typical manufacturing OLAP applications include production planning and defect analysis.
+..
+
+OLAP applications span a variety of organizational functions. Finance departments use OLAP for applications such as budgeting, activity-based costing (allocations), financial performance analysis, and financial modeling. Sales analysis and forecasting are two of the OLAP applications found in sales departments. Among other applications, marketing departments use OLAP for market research analysis, sales forecasting, promotions analysis, customer analysis, and market/customer segmentation. Typical manufacturing OLAP applications include production planning and defect analysis.
+
+.. i18n: Important to all of the above applications is the ability to provide managers with the information they need to make effective decisions about an organisation's strategic directions. The key indicator of a successful OLAP application is its ability to provide information as needed, i.e., its ability to provide "just-in-time" information for effective decision-making. This requires more than a base level of detailed data.
+..
+
+Important to all of the above applications is the ability to provide managers with the information they need to make effective decisions about an organisation's strategic directions. The key indicator of a successful OLAP application is its ability to provide information as needed, i.e., its ability to provide "just-in-time" information for effective decision-making. This requires more than a base level of detailed data.
+
+.. i18n: Just-in-time information is computed data that usually reflects complex relationships and is often calculated on the fly. Analyzing and modeling complex relationships are practical only if response times are consistently short. In addition, because the nature of data relationships may not be known in advance, the data model must be flexible. A truly flexible data model ensures that OLAP systems can respond to changing business requirements as needed for effective decision making. Although OLAP applications are found in widely divergent functional areas, they all require the following key features:
+..
+
+Just-in-time information is computed data that usually reflects complex relationships and is often calculated on the fly. Analyzing and modeling complex relationships are practical only if response times are consistently short. In addition, because the nature of data relationships may not be known in advance, the data model must be flexible. A truly flexible data model ensures that OLAP systems can respond to changing business requirements as needed for effective decision making. Although OLAP applications are found in widely divergent functional areas, they all require the following key features:
+
+.. i18n: #. Multidimensional views of data
+.. i18n:
+.. i18n: #. Calculation-intensive capabilities
+.. i18n:
+.. i18n: #. Time intelligence
+..
+
+#. Multidimensional views of data
+
+#. Calculation-intensive capabilities
+
+#. Time intelligence
+
+.. i18n: Multidimensional views of data
+.. i18n: ++++++++++++++++++++++++++++++
+..
+
+Multidimensional views of data
+++++++++++++++++++++++++++++++
+
+.. i18n: Multidimensional views are inherently representative of an actual business model. Rarely is a business model limited to fewer than three dimensions. Managers typically look at financial data by scenario (for example, actual vs. budget), organization, line items and at sales data by product, geography, channel, and time.
+..
+
+Multidimensional views are inherently representative of an actual business model. Rarely is a business model limited to fewer than three dimensions. Managers typically look at financial data by scenario (for example, actual vs. budget), organization, line items and at sales data by product, geography, channel, and time.
+
+.. i18n: A multidimensional view of data provides more than the ability to "slice and dice"; it provides the foundation for analytical processing through flexible access to information. Database design should not prejudice which operations can be performed on a dimension or how rapidly those operations are performed. Managers must be able to analyze data across any dimension, at any level of aggregation, with equal functionality and ease. OLAP software should support these views of data in a natural and responsive fashion, insulating users of the information from complex query syntax. After all, managers should not have to understand complex table layouts, elaborate table joins, and summary tables.
+..
+
+A multidimensional view of data provides more than the ability to "slice and dice"; it provides the foundation for analytical processing through flexible access to information. Database design should not prejudice which operations can be performed on a dimension or how rapidly those operations are performed. Managers must be able to analyze data across any dimension, at any level of aggregation, with equal functionality and ease. OLAP software should support these views of data in a natural and responsive fashion, insulating users of the information from complex query syntax. After all, managers should not have to understand complex table layouts, elaborate table joins, and summary tables.
+
+.. i18n: Whether a request is for the weekly sales of a product across all geographical areas or the year-to-date sales in a city across all products, an OLAP system must have consistent response times. Basic aggregation is performed on some of the dimensions (product, customer, and channel). More complex calculations are performed on other dimensions. The measure dimension computes ratios and averages. Variances are computed along the scenario dimension. A complex model based on historical performance is used to compute the forecast scenario. Consistently quick response times to these kinds of queries are key to establishing a server's ability to provide multidimensional views of information.
+..
+
+Whether a request is for the weekly sales of a product across all geographical areas or the year-to-date sales in a city across all products, an OLAP system must have consistent response times. Basic aggregation is performed on some of the dimensions (product, customer, and channel). More complex calculations are performed on other dimensions. The measure dimension computes ratios and averages. Variances are computed along the scenario dimension. A complex model based on historical performance is used to compute the forecast scenario. Consistently quick response times to these kinds of queries are key to establishing a server's ability to provide multidimensional views of information.
+
+.. i18n: Calculation-intensive capabilities
+.. i18n: ++++++++++++++++++++++++++++++++++
+..
+
+Calculation-intensive capabilities
+++++++++++++++++++++++++++++++++++
+
+.. i18n: The real test of an OLAP database is its ability to perform complex calculations. OLAP databases must be able to do more than simple aggregation. While aggregation along a hierarchy is important, there is more to analysis than simple data roll-ups. Examples of more complex calculations include share calculations (percentage of total) and allocations (which use hierarchies from a top-down perspective).
+..
+
+The real test of an OLAP database is its ability to perform complex calculations. OLAP databases must be able to do more than simple aggregation. While aggregation along a hierarchy is important, there is more to analysis than simple data roll-ups. Examples of more complex calculations include share calculations (percentage of total) and allocations (which use hierarchies from a top-down perspective).
+
+.. i18n: Key performance indicators often require involved algebraic equations. Sales forecasting uses trend algorithms such as moving averages and percentage growth. Analyzing the sales and promotions of a given company and its competitors requires modeling complex relationships among the players. The real world is complicated -- the ability to model complex relationships is key in analytical processing applications.
+..
+
+Key performance indicators often require involved algebraic equations. Sales forecasting uses trend algorithms such as moving averages and percentage growth. Analyzing the sales and promotions of a given company and its competitors requires modeling complex relationships among the players. The real world is complicated -- the ability to model complex relationships is key in analytical processing applications.
+
+.. i18n: Whereas transaction processing systems are judged on their ability to collect and manage data, analytical processing systems are judged on their ability to create information from data.
+..
+
+Whereas transaction processing systems are judged on their ability to collect and manage data, analytical processing systems are judged on their ability to create information from data.
+
+.. i18n: Time intelligence
+.. i18n: +++++++++++++++++
+..
+
+Time intelligence
++++++++++++++++++
+
+.. i18n: Time is an integral component of almost any analytical application. Time is a unique dimension because it is sequential in character (January always comes before February). True OLAP systems understand the sequential nature of time. Business performance is almost always judged over time, for example, this month vs. last month, this month vs. the same month last year. The time hierarchy is not always used in the same manner as other hierarchies. For example, a manager might ask to see the sales for May or the sales for the first five months of 1995. The same manager might also ask to see the sales for blue shirts but would never ask to see the sales for the first five shirts. Concepts such as year-to-date and period over period comparisons must be easily defined in an OLAP system.
+..
+
+Time is an integral component of almost any analytical application. Time is a unique dimension because it is sequential in character (January always comes before February). True OLAP systems understand the sequential nature of time. Business performance is almost always judged over time, for example, this month vs. last month, this month vs. the same month last year. The time hierarchy is not always used in the same manner as other hierarchies. For example, a manager might ask to see the sales for May or the sales for the first five months of 1995. The same manager might also ask to see the sales for blue shirts but would never ask to see the sales for the first five shirts. Concepts such as year-to-date and period over period comparisons must be easily defined in an OLAP system.
+
+.. i18n: In addition, OLAP systems must understand the concept of balances over time. For example, if a company sold 10 shirts in January, five shirts in February, and 10 shirts in March, then the total balance sold for the quarter would be 25 shirts. If, on the other hand, a company had a head count of 10 employees in January, only five employees in February, and 10 employees again in March, what was the company's employee head count for the quarter? Most companies would use an average balance. In the case of cash, most companies use an ending balance.
+..
+
+In addition, OLAP systems must understand the concept of balances over time. For example, if a company sold 10 shirts in January, five shirts in February, and 10 shirts in March, then the total balance sold for the quarter would be 25 shirts. If, on the other hand, a company had a head count of 10 employees in January, only five employees in February, and 10 employees again in March, what was the company's employee head count for the quarter? Most companies would use an average balance. In the case of cash, most companies use an ending balance.
=== added file 'i18n/zh_CN/source/bi/introduction/terminologies.rst'
--- i18n/zh_CN/source/bi/introduction/terminologies.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/bi/introduction/terminologies.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,159 @@
+
+.. i18n: .. _terminologies-link:
+.. i18n:
+.. i18n: Terminologies
+.. i18n: =============
+..
+
+.. _terminologies-link:
+
+Terminologies
+=============
+
+.. i18n: This page defines all terminologies. Objects in the OLAP cube use this convention.
+..
+
+This page defines all terminologies. Objects in the OLAP cube use this convention.
+
+.. i18n: .. _schema-link:
+.. i18n:
+.. i18n: .. topic:: Schema
+.. i18n:
+.. i18n: A schema is a collection of N dimensions. It's the meta description
+.. i18n: of cubes..
+..
+
+.. _schema-link:
+
+.. topic:: Schema
+
+ A schema is a collection of N dimensions. It's the meta description
+ of cubes..
+
+.. i18n: .. _hierarchy-link:
+.. i18n:
+.. i18n: .. topic:: Hierarchy
+.. i18n:
+.. i18n: A schema is divided in hierarchy, which are divided in dimensions.
+.. i18n: The main use of hierarchy is to check that different axis can not
+.. i18n: use dimensions of the same hierarchy.
+..
+
+.. _hierarchy-link:
+
+.. topic:: Hierarchy
+
+ A schema is divided in hierarchy, which are divided in dimensions.
+ The main use of hierarchy is to check that different axis can not
+ use dimensions of the same hierarchy.
+
+.. i18n: .. _dimension-link:
+.. i18n:
+.. i18n: .. topic:: Dimension
+.. i18n:
+.. i18n: A dimension is an attribute, or set of attributes, by which you can
+.. i18n: divide measures into sub-categories. It's a tree structure that
+.. i18n: define the axis of the cube. They can be explicitly defined:
+.. i18n: partner_id.country_id.state_ids or recursive 'parent_id'.
+.. i18n: A dimension is divided in levels.
+..
+
+.. _dimension-link:
+
+.. topic:: Dimension
+
+ A dimension is an attribute, or set of attributes, by which you can
+ divide measures into sub-categories. It's a tree structure that
+ define the axis of the cube. They can be explicitly defined:
+ partner_id.country_id.state_ids or recursive 'parent_id'.
+ A dimension is divided in levels.
+
+.. i18n: .. _level-link:
+.. i18n:
+.. i18n: .. topic:: Level
+.. i18n:
+.. i18n: One level of sub-categories defined by dimensions.
+..
+
+.. _level-link:
+
+.. topic:: Level
+
+ One level of sub-categories defined by dimensions.
+
+.. i18n: .. _measure-link:
+.. i18n:
+.. i18n: .. topic:: Measure
+.. i18n:
+.. i18n: Meta data of the quantity your are measuring. (value)
+.. i18n: A measure may be complex, ex: the tuple (quantity,uom)
+.. i18n: Attributes which are also objects:
+.. i18n:
+.. i18n: Agregator: an SQL function that define how we aggregate measures
+.. i18n: "sum", "count", "min", "max", "avg", and "distinct-count"
+.. i18n: FormatString
+.. i18n: DataType (the measure/value datatype)
+..
+
+.. _measure-link:
+
+.. topic:: Measure
+
+ Meta data of the quantity your are measuring. (value)
+ A measure may be complex, ex: the tuple (quantity,uom)
+ Attributes which are also objects:
+
+ Agregator: an SQL function that define how we aggregate measures
+ "sum", "count", "min", "max", "avg", and "distinct-count"
+ FormatString
+ DataType (the measure/value datatype)
+
+.. i18n: .. _cube-link:
+.. i18n:
+.. i18n: .. topic:: Cube
+.. i18n:
+.. i18n: A cube is a collection of N axis. A cube is an instance of a schema.
+.. i18n: A cube is mapped to a 'SQL' query through the use of his axis. (or several)
+..
+
+.. _cube-link:
+
+.. topic:: Cube
+
+ A cube is a collection of N axis. A cube is an instance of a schema.
+ A cube is mapped to a 'SQL' query through the use of his axis. (or several)
+
+.. i18n: .. topic:: Member
+.. i18n:
+.. i18n: A member is a point within a dimension determined by a particular set of
+.. i18n: attribute values. (instances) A member is able to compute a part of the
+.. i18n: SQL query.
+..
+
+.. topic:: Member
+
+ A member is a point within a dimension determined by a particular set of
+ attribute values. (instances) A member is able to compute a part of the
+ SQL query.
+
+.. i18n: .. topic:: Axis
+.. i18n:
+.. i18n: An axis is composed by one or a set of members. In others terms, the axis is
+.. i18n: defined by the part of the query preceding the "on rows", "on columns",
+.. i18n: "on pages"... The MDX result is also a cube composed of axis.
+..
+
+.. topic:: Axis
+
+ An axis is composed by one or a set of members. In others terms, the axis is
+ defined by the part of the query preceding the "on rows", "on columns",
+ "on pages"... The MDX result is also a cube composed of axis.
+
+.. i18n: .. topic:: Value
+.. i18n:
+.. i18n: A value is an instance of a measure. (one particular case of the cube).
+..
+
+.. topic:: Value
+
+ A value is an instance of a measure. (one particular case of the cube).
=== added directory 'i18n/zh_CN/source/book'
=== added directory 'i18n/zh_CN/source/book/0'
=== added file 'i18n/zh_CN/source/book/0/index.rst'
--- i18n/zh_CN/source/book/0/index.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/0/index.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,623 @@
+
+.. i18n: ########
+.. i18n: Foreword
+.. i18n: ########
+..
+
+########
+Foreword
+########
+
+.. i18n: Information Systems have played an increasingly visible role over the past several years in
+.. i18n: improving the competitiveness of business.
+.. i18n: More than just tools for handling repetitive tasks, they are used to guide and advance
+.. i18n: all of a company's' daily activities. Integrated management software is today very often a
+.. i18n: key source of significant competitive advantage.
+..
+
+Information Systems have played an increasingly visible role over the past several years in
+improving the competitiveness of business.
+More than just tools for handling repetitive tasks, they are used to guide and advance
+all of a company's' daily activities. Integrated management software is today very often a
+key source of significant competitive advantage.
+
+.. i18n: The standard response to a need for responsiveness, reliability, and rapidly
+.. i18n: increasing expectations is to create an organization based on departments with
+.. i18n: a clear linear structure, integrated around your operating processes. To
+.. i18n: increase efficiency amongst salespeople, accountants, logistics staff and
+.. i18n: everyone else you should have a common understanding of your problems.
+..
+
+The standard response to a need for responsiveness, reliability, and rapidly
+increasing expectations is to create an organization based on departments with
+a clear linear structure, integrated around your operating processes. To
+increase efficiency amongst salespeople, accountants, logistics staff and
+everyone else you should have a common understanding of your problems.
+
+.. i18n: For this you need a common language for shared references, policies and communication.
+.. i18n: An ERP (Enterprise Resource Planning) system provides the ideal platform for this common reference
+.. i18n: point.
+..
+
+For this you need a common language for shared references, policies and communication.
+An ERP (Enterprise Resource Planning) system provides the ideal platform for this common reference
+point.
+
+.. i18n: Open Source software at the Service of Management
+.. i18n: =================================================
+..
+
+Open Source software at the Service of Management
+=================================================
+
+.. i18n: Risks and integration costs are important barriers to all the advantages you gain from such systems.
+.. i18n: That is why, today, few small- and medium-sized companies use ERP.
+.. i18n: In addition, the larger ERP vendors such as SAP, Microsoft and Oracle have not been able
+.. i18n: to reconcile the power and comprehensive cover of an ERP system with the simplicity and flexibility
+.. i18n: wanted by the users.
+.. i18n: But this is exactly what small and medium enterprises are looking for.
+..
+
+Risks and integration costs are important barriers to all the advantages you gain from such systems.
+That is why, today, few small- and medium-sized companies use ERP.
+In addition, the larger ERP vendors such as SAP, Microsoft and Oracle have not been able
+to reconcile the power and comprehensive cover of an ERP system with the simplicity and flexibility
+wanted by the users.
+But this is exactly what small and medium enterprises are looking for.
+
+.. i18n: The development processes of Open Source Software, and the new business models adopted by their
+.. i18n: developers, provide a new way of resolving such cost and quality issues for this kind of enterprise
+.. i18n: software.
+..
+
+The development processes of Open Source Software, and the new business models adopted by their
+developers, provide a new way of resolving such cost and quality issues for this kind of enterprise
+software.
+
+.. i18n: To make an ERP system fully available to small and medium enterprises, cost reduction is the first
+.. i18n: priority.
+.. i18n: Open source software makes it possible to greatly reduce development costs by
+.. i18n: aggressive reuse of open source software libraries; to eliminate intermediaries (the distributors),
+.. i18n: with all of their expensive sales overhead; to cut out selling costs by free publication of the
+.. i18n: software;
+.. i18n: and to considerably reduce the marketing overhead.
+..
+
+To make an ERP system fully available to small and medium enterprises, cost reduction is the first
+priority.
+Open source software makes it possible to greatly reduce development costs by
+aggressive reuse of open source software libraries; to eliminate intermediaries (the distributors),
+with all of their expensive sales overhead; to cut out selling costs by free publication of the
+software;
+and to considerably reduce the marketing overhead.
+
+.. i18n: Since there is open interaction among thousands of contributors and partners working on the same
+.. i18n: project, the quality of the resulting software greatly benefits from the scrutiny.
+.. i18n: And you cannot be everything at once: accountant, software developer, salesperson,
+.. i18n: ISO 9001 quality professional, specialist in agricultural products,
+.. i18n: expert in the customs and habits of pharmaceutical vendors, just as a start.
+..
+
+Since there is open interaction among thousands of contributors and partners working on the same
+project, the quality of the resulting software greatly benefits from the scrutiny.
+And you cannot be everything at once: accountant, software developer, salesperson,
+ISO 9001 quality professional, specialist in agricultural products,
+expert in the customs and habits of pharmaceutical vendors, just as a start.
+
+.. i18n: Faced with these wide-ranging requirements, what could be better than a worldwide network of
+.. i18n: partners and contributors?
+.. i18n: Every single person adds own contributions according to his or her professional competence.
+.. i18n: Throughout this book you will see that the results exceed any reasonable expectations when such work
+.. i18n: is well organized.
+..
+
+Faced with these wide-ranging requirements, what could be better than a worldwide network of
+partners and contributors?
+Every single person adds own contributions according to his or her professional competence.
+Throughout this book you will see that the results exceed any reasonable expectations when such work
+is well organized.
+
+.. i18n: But the real challenge of development is to make this solution simple and flexible, as well as
+.. i18n: complete.
+.. i18n: And to reach this level of quality you need a leader and co-ordinator who can organize all of these
+.. i18n: activities.
+.. i18n: So the development team of Tiny ERP, today called OpenERP, is responsible for most of
+.. i18n: the organization, synchronization and coherence of the software.
+..
+
+But the real challenge of development is to make this solution simple and flexible, as well as
+complete.
+And to reach this level of quality you need a leader and co-ordinator who can organize all of these
+activities.
+So the development team of Tiny ERP, today called OpenERP, is responsible for most of
+the organization, synchronization and coherence of the software.
+
+.. i18n: And OpenERP offers great performance in all these areas!
+..
+
+And OpenERP offers great performance in all these areas!
+
+.. i18n: The OpenERP Solution
+.. i18n: ====================
+..
+
+The OpenERP Solution
+====================
+
+.. i18n: Because of its modularity, collaborative developments in OpenERP have been cleanly integrated,
+.. i18n: enabling any company to choose from a large list of available functions.
+.. i18n: As with most open source software, accessibility, flexibility and ease of use are important keywords
+.. i18n: for development.
+.. i18n: Experience has shown that there is no need to train users for several months on the system,
+.. i18n: because they can just download it and use it directly.
+..
+
+Because of its modularity, collaborative developments in OpenERP have been cleanly integrated,
+enabling any company to choose from a large list of available functions.
+As with most open source software, accessibility, flexibility and ease of use are important keywords
+for development.
+Experience has shown that there is no need to train users for several months on the system,
+because they can just download it and use it directly.
+
+.. i18n: So you will find modules to suit all kinds of needs, allowing your company to build its customized
+.. i18n: system
+.. i18n: by simply grouping and configuring the most suitable modules. Hundreds of modules are available.
+..
+
+So you will find modules to suit all kinds of needs, allowing your company to build its customized
+system
+by simply grouping and configuring the most suitable modules. Hundreds of modules are available.
+
+.. i18n: They range from specific modules like the EDI interface for agricultural products,
+.. i18n: which has been used to interface with Match and Leclerc stores, up to the generic demonstration
+.. i18n: automation module for ordering sandwiches, which can take care of the eating preferences of your staff.
+..
+
+They range from specific modules like the EDI interface for agricultural products,
+which has been used to interface with Match and Leclerc stores, up to the generic demonstration
+automation module for ordering sandwiches, which can take care of the eating preferences of your staff.
+
+.. i18n: The results are rather impressive. OpenERP (originally called Tiny ERP) is a Management
+.. i18n: Software that is downloaded more than any other in the world, with over 600 downloads per day.
+.. i18n: Today it is available in 18 languages and has a worldwide network of partners and contributors.
+.. i18n: Over 800 developers participate in the projects on the collaborative development system.
+..
+
+The results are rather impressive. OpenERP (originally called Tiny ERP) is a Management
+Software that is downloaded more than any other in the world, with over 600 downloads per day.
+Today it is available in 18 languages and has a worldwide network of partners and contributors.
+Over 800 developers participate in the projects on the collaborative development system.
+
+.. i18n: To our knowledge, OpenERP is the only management system which is routinely used not only by big
+.. i18n: companies but also by very small companies and independent companies. This diversity is an
+.. i18n: illustration of the software's flexibility: a rather elegant coordination between people's
+.. i18n: functional expectations of the software and great ease of use.
+..
+
+To our knowledge, OpenERP is the only management system which is routinely used not only by big
+companies but also by very small companies and independent companies. This diversity is an
+illustration of the software's flexibility: a rather elegant coordination between people's
+functional expectations of the software and great ease of use.
+
+.. i18n: And this diversity is also found in the various sectors and trades which use the software, including
+.. i18n: agricultural products, textiles, public auctions, IT, and trade associations.
+..
+
+And this diversity is also found in the various sectors and trades which use the software, including
+agricultural products, textiles, public auctions, IT, and trade associations.
+
+.. i18n: Last but not least, such software has arisen from the blend of high code quality, well-judged architecture and
+.. i18n: use of free technologies. In fact, you may be surprised (if you are an IT person) to find that the
+.. i18n: download size of OpenERP is only around 6 MB. When that is expanded during installation its size is mostly
+.. i18n: attributable to all the official translations that are packaged with it, not the operating code.
+.. i18n: We've moved a long way from
+.. i18n: the days when the only people who could be expected to benefit from ERP were the owners of a widget
+.. i18n: factory on some remote industrial estate.
+..
+
+Last but not least, such software has arisen from the blend of high code quality, well-judged architecture and
+use of free technologies. In fact, you may be surprised (if you are an IT person) to find that the
+download size of OpenERP is only around 6 MB. When that is expanded during installation its size is mostly
+attributable to all the official translations that are packaged with it, not the operating code.
+We've moved a long way from
+the days when the only people who could be expected to benefit from ERP were the owners of a widget
+factory on some remote industrial estate.
+
+.. i18n: Why this book?
+.. i18n: --------------
+..
+
+Why this book?
+--------------
+
+.. i18n: Many books set out to tell readers about the management of enterprise, and equally many aim to
+.. i18n: instruct the reader in the use of a piece of specialized software. We are not aiming to add to those
+.. i18n: lists because our approach is intended to be different.
+..
+
+Many books set out to tell readers about the management of enterprise, and equally many aim to
+instruct the reader in the use of a piece of specialized software. We are not aiming to add to those
+lists because our approach is intended to be different.
+
+.. i18n: Having restructured and reorganized many businesses, we wanted our management experience to generate
+.. i18n: a work that is both instructive and practical. It was important for us not to write a manual about
+.. i18n: OpenERP, but instead a work that deals with advanced management techniques realized through these
+.. i18n: IT tools. You will see what management practices might be useful, what is possible, and then how you
+.. i18n: could achieve that in OpenERP.
+..
+
+Having restructured and reorganized many businesses, we wanted our management experience to generate
+a work that is both instructive and practical. It was important for us not to write a manual about
+OpenERP, but instead a work that deals with advanced management techniques realized through these
+IT tools. You will see what management practices might be useful, what is possible, and then how you
+could achieve that in OpenERP.
+
+.. i18n: This is what we will consider OpenERP to be: not an end in itself but just the tool you use to put
+.. i18n: an advanced management system into place.
+..
+
+This is what we will consider OpenERP to be: not an end in itself but just the tool you use to put
+an advanced management system into place.
+
+.. i18n: Who is it for?
+.. i18n: --------------
+..
+
+Who is it for?
+--------------
+
+.. i18n: Written by two CEOs who have been successful with new technologies, this book is aimed at directors
+.. i18n: and managers who have an ambition to improve the performance of their whole company's management
+.. i18n: team. They are likely to already have significant responsibilities and possess the influence to get
+.. i18n: things done in their company.
+..
+
+Written by two CEOs who have been successful with new technologies, this book is aimed at directors
+and managers who have an ambition to improve the performance of their whole company's management
+team. They are likely to already have significant responsibilities and possess the influence to get
+things done in their company.
+
+.. i18n: It is likely that most readers will come from small- and medium-sized enterprises (up to a few
+.. i18n: hundred staff), and independent companies, because of the breadth of functions that need to be
+.. i18n: analyzed and involved in change. The same principles also apply to larger companies, however.
+..
+
+It is likely that most readers will come from small- and medium-sized enterprises (up to a few
+hundred staff), and independent companies, because of the breadth of functions that need to be
+analyzed and involved in change. The same principles also apply to larger companies, however.
+
+.. i18n: Structure of this book
+.. i18n: ======================
+..
+
+Structure of this book
+======================
+
+.. i18n: Part One, :ref:`part1-steps`, starts with the installation of OpenERP. If you have already installed OpenERP you
+.. i18n: can directly take your first steps on a guided tour in the :ref:`ch-guided` chapter. If you are already familiar
+.. i18n: with OpenERP or Tiny ERP you can use the :ref:`ch-real` chapter to find out how to create a new workflow from
+.. i18n: scratch in an empty database with nothing to distract you. Or you can skip directly to the :ref:`ch-crm` chapter in
+.. i18n: the :ref:`part2-crm` part, to start with details of OpenERP's functional modules.
+..
+
+Part One, :ref:`part1-steps`, starts with the installation of OpenERP. If you have already installed OpenERP you
+can directly take your first steps on a guided tour in the :ref:`ch-guided` chapter. If you are already familiar
+with OpenERP or Tiny ERP you can use the :ref:`ch-real` chapter to find out how to create a new workflow from
+scratch in an empty database with nothing to distract you. Or you can skip directly to the :ref:`ch-crm` chapter in
+the :ref:`part2-crm` part, to start with details of OpenERP's functional modules.
+
+.. i18n: Part Two, :ref:`part2-crm`, deals with Supplier and Customer Relationship Management (SRM & CRM). You will find the
+.. i18n: elements necessary for managing an efficient sales department there, and automating tasks to monitor
+.. i18n: performance.
+..
+
+Part Two, :ref:`part2-crm`, deals with Supplier and Customer Relationship Management (SRM & CRM). You will find the
+elements necessary for managing an efficient sales department there, and automating tasks to monitor
+performance.
+
+.. i18n: Part Three, :ref:`part-genacct`, is devoted to general accounting and its key role in the management of the whole
+.. i18n: enterprise.
+..
+
+Part Three, :ref:`part-genacct`, is devoted to general accounting and its key role in the management of the whole
+enterprise.
+
+.. i18n: Part Four, :ref:`part-ops`, handles all the operational functions of enterprise management:
+.. i18n: Human Resources for managing projects,
+.. i18n: through financial analyses supplied by analytic (or cost) accounts. You will see how using OpenERP
+.. i18n: can help you optimize your leadership of an enterprise.
+..
+
+Part Four, :ref:`part-ops`, handles all the operational functions of enterprise management:
+Human Resources for managing projects,
+through financial analyses supplied by analytic (or cost) accounts. You will see how using OpenERP
+can help you optimize your leadership of an enterprise.
+
+.. i18n: Part Five, :ref:`part-phys`, describes the physical movement of Stocks and their Manufacturing
+.. i18n: (the transformation or products and services into other products).
+..
+
+Part Five, :ref:`part-phys`, describes the physical movement of Stocks and their Manufacturing
+(the transformation or products and services into other products).
+
+.. i18n: Part Six, :ref:`part-trade`, deals with Purchasing and Selling goods and services.
+..
+
+Part Six, :ref:`part-trade`, deals with Purchasing and Selling goods and services.
+
+.. i18n: Part Seven, :ref:`part-qual`, is focused on the Process description and Documentation & Knowledge handling that OpenERP
+.. i18n: manages.
+..
+
+Part Seven, :ref:`part-qual`, is focused on the Process description and Documentation & Knowledge handling that OpenERP
+manages.
+
+.. i18n: Finally Part Eight, :ref:`part-config`, structured in two chapters, explains first how to administer and configure OpenERP, then provides a methodology for implementing OpenERP in your enterprise.
+..
+
+Finally Part Eight, :ref:`part-config`, structured in two chapters, explains first how to administer and configure OpenERP, then provides a methodology for implementing OpenERP in your enterprise.
+
+.. i18n: .. note:: *About the authors*
+.. i18n:
+.. i18n: **Fabien Pinckaers**
+.. i18n:
+.. i18n: Fabien Pinckaers was only eighteen years old when he started his first company.
+.. i18n: Today, over ten years later, he has founded and managed several new technology companies,
+.. i18n: all based on Free / Open Source software.
+.. i18n:
+.. i18n: He originated Tiny ERP, now OpenERP, and is the director of two companies including Tiny sprl,
+.. i18n: the editor of OpenERP. In three years he has grown the Tiny group from one to sixty-five
+.. i18n: employees
+.. i18n: without loans or external fund-raising, and while making a profit.
+.. i18n:
+.. i18n: He has also developed several large scale projects, such as Auction-in-Europe.com,
+.. i18n: which become the leader in the art market in Belgium.
+.. i18n: Even today people sell more art works there than on ebay.be.
+.. i18n:
+.. i18n: He is also the founder of the LUG (Linux User Group) of Louvain-la-Neuve,
+.. i18n: and of several free projects like OpenReport, OpenStuff and Tiny Report.
+.. i18n: Educated as a civil engineer (polytechnic), he has won several IT prizes in Europe such as Wired
+.. i18n: and l'Inscene.
+.. i18n:
+.. i18n: A fierce defender of free software in the enterprise,
+.. i18n: he is in constant demand as a conference speaker and
+.. i18n: he is the author of numerous articles dealing with free software in the management of the
+.. i18n: enterprise.
+.. i18n:
+.. i18n: Follow Fabien on his blog http://fptiny.blogspot.com/ or on twitter fpopenerp.
+.. i18n:
+.. i18n: **Geoff Gardiner**
+.. i18n:
+.. i18n: Geoff has held posts as director of services and of IT systems for
+.. i18n: international companies and in manufacturing.
+.. i18n: He was Senior Industrial Research Fellow at Cambridge University's Institute for Manufacturing
+.. i18n: where he focused on innovation processes.
+.. i18n:
+.. i18n: He founded Seath Solutions Ltd (http://www.seathsolutions.com/) to provide services
+.. i18n: in the use of Open Source software, particularly OpenERP, for business management.
+.. i18n:
+.. i18n: Author of articles and books focusing on the processes and technology of innovation,
+.. i18n: Geoff is also an active contributor to the OpenERP project.
+.. i18n: He holds an MBA from Cranfield School of Management and
+.. i18n: an MA in Engineering and Electrical Sciences from Trinity Hall, Cambridge.
+.. i18n: He is a member of the Institution of Engineering and Technology and of the Society of Authors.
+.. i18n:
+.. i18n: Having observed, suffered, and led process implementation projects in various organizations,
+.. i18n: he has many thoughts to share on the successful adoption of an effective management automation
+.. i18n: tool.
+.. i18n:
+.. i18n: **Els Van Vossel**
+.. i18n:
+.. i18n: Els Van Vossel always had a dedication to both written and spoken word.
+.. i18n: Clear and explicit communication is crucial.
+.. i18n:
+.. i18n: Educated as a Professional Translator in Antwerp, she worked as an independent translator
+.. i18n: on the localization of major ERP software. Els acquired ERP knowledge and decided
+.. i18n: to start working as a functional ERP consultant and a Technical Communicator for ERP software.
+.. i18n:
+.. i18n: As such, the world of OpenSource software became more and more attractive.
+.. i18n: She started working with OpenERP software in her free time and doing so, Els really wanted to
+.. i18n: meet Fabien Pinckaers to share thoughts about documentation and training strategy.
+.. i18n: At a Partner Meeting she heard Fabien was looking for someone to manage training & documentation.
+.. i18n: This was absolutely an opportunity to be qualified, and now Els is the OpenERP Training Program Manager
+.. i18n: and responsible for the worldwide training and certification program of OpenERP.
+.. i18n:
+.. i18n: Being an author of several Software Manuals, it is a great challenge to work on the
+.. i18n: OpenERP documentation and continuously take it to a higher level. Please note that this is a hell of a job,
+.. i18n: but Els finds great pleasure in doing it!
+.. i18n:
+.. i18n: Follow Els on her blog http://training-openerp.blogspot.com/ or on twitter elsvanvossel.
+..
+
+ .. note:: *About the authors*
+
+ **Fabien Pinckaers**
+
+ Fabien Pinckaers was only eighteen years old when he started his first company.
+ Today, over ten years later, he has founded and managed several new technology companies,
+ all based on Free / Open Source software.
+
+ He originated Tiny ERP, now OpenERP, and is the director of two companies including Tiny sprl,
+ the editor of OpenERP. In three years he has grown the Tiny group from one to sixty-five
+ employees
+ without loans or external fund-raising, and while making a profit.
+
+ He has also developed several large scale projects, such as Auction-in-Europe.com,
+ which become the leader in the art market in Belgium.
+ Even today people sell more art works there than on ebay.be.
+
+ He is also the founder of the LUG (Linux User Group) of Louvain-la-Neuve,
+ and of several free projects like OpenReport, OpenStuff and Tiny Report.
+ Educated as a civil engineer (polytechnic), he has won several IT prizes in Europe such as Wired
+ and l'Inscene.
+
+ A fierce defender of free software in the enterprise,
+ he is in constant demand as a conference speaker and
+ he is the author of numerous articles dealing with free software in the management of the
+ enterprise.
+
+ Follow Fabien on his blog http://fptiny.blogspot.com/ or on twitter fpopenerp.
+
+ **Geoff Gardiner**
+
+ Geoff has held posts as director of services and of IT systems for
+ international companies and in manufacturing.
+ He was Senior Industrial Research Fellow at Cambridge University's Institute for Manufacturing
+ where he focused on innovation processes.
+
+ He founded Seath Solutions Ltd (http://www.seathsolutions.com/) to provide services
+ in the use of Open Source software, particularly OpenERP, for business management.
+
+ Author of articles and books focusing on the processes and technology of innovation,
+ Geoff is also an active contributor to the OpenERP project.
+ He holds an MBA from Cranfield School of Management and
+ an MA in Engineering and Electrical Sciences from Trinity Hall, Cambridge.
+ He is a member of the Institution of Engineering and Technology and of the Society of Authors.
+
+ Having observed, suffered, and led process implementation projects in various organizations,
+ he has many thoughts to share on the successful adoption of an effective management automation
+ tool.
+
+ **Els Van Vossel**
+
+ Els Van Vossel always had a dedication to both written and spoken word.
+ Clear and explicit communication is crucial.
+
+ Educated as a Professional Translator in Antwerp, she worked as an independent translator
+ on the localization of major ERP software. Els acquired ERP knowledge and decided
+ to start working as a functional ERP consultant and a Technical Communicator for ERP software.
+
+ As such, the world of OpenSource software became more and more attractive.
+ She started working with OpenERP software in her free time and doing so, Els really wanted to
+ meet Fabien Pinckaers to share thoughts about documentation and training strategy.
+ At a Partner Meeting she heard Fabien was looking for someone to manage training & documentation.
+ This was absolutely an opportunity to be qualified, and now Els is the OpenERP Training Program Manager
+ and responsible for the worldwide training and certification program of OpenERP.
+
+ Being an author of several Software Manuals, it is a great challenge to work on the
+ OpenERP documentation and continuously take it to a higher level. Please note that this is a hell of a job,
+ but Els finds great pleasure in doing it!
+
+ Follow Els on her blog http://training-openerp.blogspot.com/ or on twitter elsvanvossel.
+
+.. i18n: Dedication
+.. i18n: ==========
+..
+
+Dedication
+==========
+
+.. i18n: *From Geoff Gardiner*
+..
+
+ *From Geoff Gardiner*
+
+.. i18n: My gratitude goes to my co-author, Fabien Pinckaers, for his vision and tenacity in
+.. i18n: developing Tiny ERP and OpenERP, and the team at OpenERP for its excellent work on this.
+..
+
+My gratitude goes to my co-author, Fabien Pinckaers, for his vision and tenacity in
+developing Tiny ERP and OpenERP, and the team at OpenERP for its excellent work on this.
+
+.. i18n: OpenERP relies on a philosophy of Open Source and on the technologies that have been
+.. i18n: developed and tuned over the years by numerous talented people. Their efforts are greatly
+.. i18n: appreciated.
+..
+
+OpenERP relies on a philosophy of Open Source and on the technologies that have been
+developed and tuned over the years by numerous talented people. Their efforts are greatly
+appreciated.
+
+.. i18n: Thanks also to my family for their encouragement, their tolerance and their constant presence.
+..
+
+Thanks also to my family for their encouragement, their tolerance and their constant presence.
+
+.. i18n: *From Els Van Vossel*
+..
+
+ *From Els Van Vossel*
+
+.. i18n: Thank you Fabien, for offering me the opportunity to work with OpenERP.
+.. i18n: Thanks to my documentation team for helping me to get a first V6.0.0 version of the documentation!
+.. i18n: In the near future, I dedicate myself to restructuring the documentation completely and manage to
+.. i18n: get a real Business-oriented version. For that, already in advance I thank the OpenERP team for their support.
+..
+
+Thank you Fabien, for offering me the opportunity to work with OpenERP.
+Thanks to my documentation team for helping me to get a first V6.0.0 version of the documentation!
+In the near future, I dedicate myself to restructuring the documentation completely and manage to
+get a real Business-oriented version. For that, already in advance I thank the OpenERP team for their support.
+
+.. i18n: *From Fabien Pinckaers*
+..
+
+ *From Fabien Pinckaers*
+
+.. i18n: I address my thanks to all of the team at OpenERP for their hard work in preparing, translating and
+.. i18n: re-reading the book in its various forms.
+.. i18n: My particular thanks to Laurence Henrion and my family for supporting me throughout all this effort.
+..
+
+I address my thanks to all of the team at OpenERP for their hard work in preparing, translating and
+re-reading the book in its various forms.
+My particular thanks to Laurence Henrion and my family for supporting me throughout all this effort.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added directory 'i18n/zh_CN/source/book/1'
=== added directory 'i18n/zh_CN/source/book/1/1_0_Subscribe_Start'
=== added directory 'i18n/zh_CN/source/book/1/1_0_Subscribe_Start/images'
=== added file 'i18n/zh_CN/source/book/1/1_0_Subscribe_Start/images/start_saas.jpeg'
Binary files i18n/zh_CN/source/book/1/1_0_Subscribe_Start/images/start_saas.jpeg 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_0_Subscribe_Start/images/start_saas.jpeg 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_0_Subscribe_Start/index.rst'
--- i18n/zh_CN/source/book/1/1_0_Subscribe_Start/index.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_0_Subscribe_Start/index.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,222 @@
+
+.. i18n: .. index::
+.. i18n: single: Subscribe Start
+..
+
+.. index::
+ single: Subscribe Start
+
+.. i18n: .. _ch-ss:
+.. i18n:
+.. i18n: *****************
+.. i18n: Subscribe & Start
+.. i18n: *****************
+..
+
+.. _ch-ss:
+
+*****************
+Subscribe & Start
+*****************
+
+.. i18n: Whether you want to test OpenERP or put it into full production, you have at least two possible starting
+.. i18n: points:
+..
+
+Whether you want to test OpenERP or put it into full production, you have at least two possible starting
+points:
+
+.. i18n: * you can use OpenERP Online by subscribing to http://www.openerp.com/online/;
+.. i18n:
+.. i18n: * you can install the solution on your own computers to test it in your company's system environment.
+..
+
+* you can use OpenERP Online by subscribing to http://www.openerp.com/online/;
+
+* you can install the solution on your own computers to test it in your company's system environment.
+
+.. i18n: In this chapter, the easy-to-use *OpenERP Online* solution will be briefly explained. For more information about installing OpenERP on your computer, please refer to the chapter :ref:`part5-crm-install`.
+..
+
+In this chapter, the easy-to-use *OpenERP Online* solution will be briefly explained. For more information about installing OpenERP on your computer, please refer to the chapter :ref:`part5-crm-install`.
+
+.. i18n: .. note:: Some Interesting Websites from OpenERP
+.. i18n:
+.. i18n: * Main Site: http://www.openerp.com,
+.. i18n:
+.. i18n: * OpenERP Online Site: http://www.openerp.com/online,
+.. i18n:
+.. i18n: * Online demo at http://demo.openerp.com,
+.. i18n:
+.. i18n: * Documentation site: http://doc.openerp.com/,
+.. i18n:
+.. i18n: * Community discussion forum where you can often receive assistance: http://www.openerp.com/forum/.
+..
+
+.. note:: Some Interesting Websites from OpenERP
+
+ * Main Site: http://www.openerp.com,
+
+ * OpenERP Online Site: http://www.openerp.com/online,
+
+ * Online demo at http://demo.openerp.com,
+
+ * Documentation site: http://doc.openerp.com/,
+
+ * Community discussion forum where you can often receive assistance: http://www.openerp.com/forum/.
+
+.. i18n: .. tip:: Current documentation
+.. i18n:
+.. i18n: The procedure for installing OpenERP will change and improve with
+.. i18n: each new version, so you should always check each release's documentation on the website for the latest installation procedures.
+..
+
+.. tip:: Current documentation
+
+ The procedure for installing OpenERP will change and improve with
+ each new version, so you should always check each release's documentation on the website for the latest installation procedures.
+
+.. i18n: Use OpenERP Online
+.. i18n: ------------------
+..
+
+Use OpenERP Online
+------------------
+
+.. i18n: .. index::
+.. i18n: single: OpenERP Online
+..
+
+.. index::
+ single: OpenERP Online
+
+.. i18n: Nothing is easier for you to discover OpenERP than subscribing to the OpenERP Online offer. You just need a web browser to get started.
+..
+
+Nothing is easier for you to discover OpenERP than subscribing to the OpenERP Online offer. You just need a web browser to get started.
+
+.. i18n: The Online service can be particularly useful to small companies, that just want to get going quickly at low cost.
+.. i18n: You have immediate access to OpenERP's Integrated Management System built on the type of enterprise architecture used in many organizations.
+..
+
+The Online service can be particularly useful to small companies, that just want to get going quickly at low cost.
+You have immediate access to OpenERP's Integrated Management System built on the type of enterprise architecture used in many organizations.
+
+.. i18n: OpenERP's Online offer includes several services: hosting at high bandwidth, database management, stable security update, backups, maintenance (24/7 server monitoring), bug fixing and migrations.
+..
+
+OpenERP's Online offer includes several services: hosting at high bandwidth, database management, stable security update, backups, maintenance (24/7 server monitoring), bug fixing and migrations.
+
+.. i18n: OpenERP guarantees that the software running on OpenERP Online is exactly the same as the Open Source official
+.. i18n: version of OpenERP. Any improvement made on OpenERP will be available online. This allows you to easily switch from the online version to the local version anytime.
+..
+
+OpenERP guarantees that the software running on OpenERP Online is exactly the same as the Open Source official
+version of OpenERP. Any improvement made on OpenERP will be available online. This allows you to easily switch from the online version to the local version anytime.
+
+.. i18n: So even if the OpenERP Online solution best suits your needs today, you can easily switch to an installation on your own servers according to your company's changing requirements or growth. You can also change your service provider
+.. i18n: anytime, while continuing to use the exact same system. Hence, you do not depend on your host. In addition, OpenERP works with standard and open formats and programming languages which allow
+.. i18n: you to export your data and use them in any other software.
+..
+
+So even if the OpenERP Online solution best suits your needs today, you can easily switch to an installation on your own servers according to your company's changing requirements or growth. You can also change your service provider
+anytime, while continuing to use the exact same system. Hence, you do not depend on your host. In addition, OpenERP works with standard and open formats and programming languages which allow
+you to export your data and use them in any other software.
+
+.. i18n: These advantages give you total control over your data, your software, your platform.
+..
+
+These advantages give you total control over your data, your software, your platform.
+
+.. i18n: .. figure:: images/start_saas.jpeg
+.. i18n: :align: center
+.. i18n: :scale: 90
+.. i18n:
+.. i18n: *Subscribe and Start with OpenERP Online*
+..
+
+.. figure:: images/start_saas.jpeg
+ :align: center
+ :scale: 90
+
+ *Subscribe and Start with OpenERP Online*
+
+.. i18n: If you want to start working with the online platform, you can navigate to http://www.openerp.com/online. After successful registration, you will be able to configure and use OpenERP online. To log in to your OpenERP Online account, you will receive a username and password. You can build the software to fit your needs, at your own pace!
+..
+
+If you want to start working with the online platform, you can navigate to http://www.openerp.com/online. After successful registration, you will be able to configure and use OpenERP online. To log in to your OpenERP Online account, you will receive a username and password. You can build the software to fit your needs, at your own pace!
+
+.. i18n: OpenERP Online - Software as a Service - is hosted by OpenERP and paid in the form of a monthly subscription. The pricing model is extremely simple. OpenERP charges a fixed fee per month per user. You will get an invoice each month according to the number of users registered in the system at that time. If you add new users during the next 30 days, they will only be charged with the next invoice.
+.. i18n: You can find the details of current pricing and payment options at http://www.openerp.com/online.
+..
+
+OpenERP Online - Software as a Service - is hosted by OpenERP and paid in the form of a monthly subscription. The pricing model is extremely simple. OpenERP charges a fixed fee per month per user. You will get an invoice each month according to the number of users registered in the system at that time. If you add new users during the next 30 days, they will only be charged with the next invoice.
+You can find the details of current pricing and payment options at http://www.openerp.com/online.
+
+.. i18n: .. tip:: Free Trial
+.. i18n:
+.. i18n: For a month's free trial, check out OpenERP's http://www.openerp.com/online, which enables you to get started quickly without incurring costs for integration or for buying computer systems. After the free trial expires, you can easily continue using OpenERP Online.
+..
+
+.. tip:: Free Trial
+
+ For a month's free trial, check out OpenERP's http://www.openerp.com/online, which enables you to get started quickly without incurring costs for integration or for buying computer systems. After the free trial expires, you can easily continue using OpenERP Online.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added directory 'i18n/zh_CN/source/book/1/1_1_Inst_Config'
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst'
--- i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,205 @@
+
+.. i18n: .. index::
+.. i18n: single: architecture; OpenERP
+..
+
+.. index::
+ single: architecture; OpenERP
+
+.. i18n: The Architecture of OpenERP
+.. i18n: ===========================
+..
+
+The Architecture of OpenERP
+===========================
+
+.. i18n: To access OpenERP you can:
+..
+
+To access OpenERP you can:
+
+.. i18n: * use a web browser pointed at the OpenERP server, or
+.. i18n:
+.. i18n: * use an application client (the GTK client) installed on each computer.
+..
+
+* use a web browser pointed at the OpenERP server, or
+
+* use an application client (the GTK client) installed on each computer.
+
+.. i18n: Both access methods give similar facilities, and you can use both on
+.. i18n: the same server at the same time. It is best to use the web browser if the
+.. i18n: OpenERP server is some distance away (such as on another continent) because
+.. i18n: it is more tolerant of time delays between the two than the GTK client is. The
+.. i18n: web client is also easier to maintain, because it is generally already installed
+.. i18n: on users' computers.
+..
+
+Both access methods give similar facilities, and you can use both on
+the same server at the same time. It is best to use the web browser if the
+OpenERP server is some distance away (such as on another continent) because
+it is more tolerant of time delays between the two than the GTK client is. The
+web client is also easier to maintain, because it is generally already installed
+on users' computers.
+
+.. i18n: Conversely you would be better off with the application client (called the GTK
+.. i18n: client because of the technology it is built with) if you are using a local
+.. i18n: server (such as in the same building). In this case the GTK client will be more
+.. i18n: responsive, so more satisfying to use.
+..
+
+Conversely you would be better off with the application client (called the GTK
+client because of the technology it is built with) if you are using a local
+server (such as in the same building). In this case the GTK client will be more
+responsive, so more satisfying to use.
+
+.. i18n: .. index::
+.. i18n: single: client; web (thin) and GTK (thick)
+.. i18n: single: client; caching
+..
+
+.. index::
+ single: client; web (thin) and GTK (thick)
+ single: client; caching
+
+.. i18n: .. note:: Web Client and GTK Client
+.. i18n:
+.. i18n: There is little functional difference between the two OpenERP clients - the
+.. i18n: web client and the GTK client at present.
+.. i18n: The web client offers more functionality, for instance, the Corporate Intelligence feature, and the Gantt view.
+.. i18n:
+.. i18n: The OpenERP company will continue to support two clients for the foreseeable
+.. i18n: future, so you can use whichever client you prefer.
+..
+
+.. note:: Web Client and GTK Client
+
+ There is little functional difference between the two OpenERP clients - the
+ web client and the GTK client at present.
+ The web client offers more functionality, for instance, the Corporate Intelligence feature, and the Gantt view.
+
+ The OpenERP company will continue to support two clients for the foreseeable
+ future, so you can use whichever client you prefer.
+
+.. i18n: An OpenERP system is formed from two components:
+..
+
+An OpenERP system is formed from two components:
+
+.. i18n: * the PostgreSQL database server, which contains all of the databases, each of which contains all
+.. i18n: data and most elements of the OpenERP system configuration,
+.. i18n:
+.. i18n: * the OpenERP application server, which contains all of the enterprise logic and ensures that
+.. i18n: OpenERP runs optimally. It also contains the web server.
+..
+
+* the PostgreSQL database server, which contains all of the databases, each of which contains all
+ data and most elements of the OpenERP system configuration,
+
+* the OpenERP application server, which contains all of the enterprise logic and ensures that
+ OpenERP runs optimally. It also contains the web server.
+
+.. i18n: .. figure:: images/terp_arch_1.png
+.. i18n: :align: center
+.. i18n: :scale: 90
+.. i18n:
+.. i18n: *The architecture of OpenERP*
+..
+
+.. figure:: images/terp_arch_1.png
+ :align: center
+ :scale: 90
+
+ *The architecture of OpenERP*
+
+.. i18n: .. index::
+.. i18n: single: PostgreSQL
+..
+
+.. index::
+ single: PostgreSQL
+
+.. i18n: .. note:: PostgreSQL, the relational and object database management system.
+.. i18n:
+.. i18n: It is a free and open-source high-performance system that compares well with other database
+.. i18n: management systems such as MySQL and FirebirdSQL (both free), Sybase, DB2
+.. i18n: and Microsoft SQL Server (all proprietary). It runs on all types of
+.. i18n: Operating System, from Unix/Linux to the various releases of Windows, via
+.. i18n: Mac OS X, Solaris, SunOS and BSD.
+..
+
+.. note:: PostgreSQL, the relational and object database management system.
+
+ It is a free and open-source high-performance system that compares well with other database
+ management systems such as MySQL and FirebirdSQL (both free), Sybase, DB2
+ and Microsoft SQL Server (all proprietary). It runs on all types of
+ Operating System, from Unix/Linux to the various releases of Windows, via
+ Mac OS X, Solaris, SunOS and BSD.
+
+.. i18n: Both components can be installed on the same server or
+.. i18n: distributed onto separate computer servers, if performance considerations
+.. i18n: require it.
+..
+
+Both components can be installed on the same server or
+distributed onto separate computer servers, if performance considerations
+require it.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_db_create.rst'
--- i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_db_create.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_db_create.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,651 @@
+
+.. i18n: .. index::
+.. i18n: single: database; create
+.. i18n: single: database
+..
+
+.. index::
+ single: database; create
+ single: database
+
+.. i18n: .. _sect-dbcreate:
+.. i18n:
+.. i18n: Database Creation
+.. i18n: =================
+..
+
+.. _sect-dbcreate:
+
+Database Creation
+=================
+
+.. i18n: Use the technique outlined in this section to create a new database, \ ``openerp_ch01`` \. This
+.. i18n: database will contain the demonstration data provided with OpenERP and a large proportion of the
+.. i18n: core OpenERP functionality. You will need to know your super administrator password for this – or
+.. i18n: you will have to find somebody who does have it to create this database.
+..
+
+Use the technique outlined in this section to create a new database, \ ``openerp_ch01`` \. This
+database will contain the demonstration data provided with OpenERP and a large proportion of the
+core OpenERP functionality. You will need to know your super administrator password for this – or
+you will have to find somebody who does have it to create this database.
+
+.. i18n: .. index::
+.. i18n: single: password; super-administrator
+.. i18n: single: password; superadmin
+..
+
+.. index::
+ single: password; super-administrator
+ single: password; superadmin
+
+.. i18n: .. note:: The Super-administrator Password
+.. i18n:
+.. i18n: Anyone who knows the super-administrator password has complete access to the data on the server
+.. i18n: – able to read, change and delete any of the data in any of the databases there.
+.. i18n:
+.. i18n: After first installation, the password is ``admin``. This is the hard-coded default, and
+.. i18n: is used if there is no accessible server configuration file. If your system has been
+.. i18n: set up so that the server configuration file can be written to by the server, then
+.. i18n: you can change the password through the client. Or you could deliberately make the
+.. i18n: configuration file read-only so that there is no prospect of changing it from the client.
+.. i18n: Either way, a server systems administrator can change it if you forget it.
+.. i18n:
+.. i18n: So if your system is set to allow it, you can change the superadmin password through the GTK client
+.. i18n: from the menu :menuselection:`File --> Databases --> Administrator Password`, or through the
+.. i18n: web client by logging out (click the :guilabel:`Logout` link), clicking :guilabel:`Databases` on the
+.. i18n: login screen, and then clicking the :guilabel:`Password` button on the Management screen.
+.. i18n:
+.. i18n: The location of the server configuration file is typically defined by starting the server with
+.. i18n: the ``--config`` command line option.
+..
+
+.. note:: The Super-administrator Password
+
+ Anyone who knows the super-administrator password has complete access to the data on the server
+ – able to read, change and delete any of the data in any of the databases there.
+
+ After first installation, the password is ``admin``. This is the hard-coded default, and
+ is used if there is no accessible server configuration file. If your system has been
+ set up so that the server configuration file can be written to by the server, then
+ you can change the password through the client. Or you could deliberately make the
+ configuration file read-only so that there is no prospect of changing it from the client.
+ Either way, a server systems administrator can change it if you forget it.
+
+ So if your system is set to allow it, you can change the superadmin password through the GTK client
+ from the menu :menuselection:`File --> Databases --> Administrator Password`, or through the
+ web client by logging out (click the :guilabel:`Logout` link), clicking :guilabel:`Databases` on the
+ login screen, and then clicking the :guilabel:`Password` button on the Management screen.
+
+ The location of the server configuration file is typically defined by starting the server with
+ the ``--config`` command line option.
+
+.. i18n: .. figure:: images/change_superadmin_pwd.png
+.. i18n: :scale: 65
+.. i18n: :align: center
+.. i18n:
+.. i18n: *Changing the super-administrator password through the web client*
+..
+
+.. figure:: images/change_superadmin_pwd.png
+ :scale: 65
+ :align: center
+
+ *Changing the super-administrator password through the web client*
+
+.. i18n: .. _sect-creatingdb:
+.. i18n:
+.. i18n: Creating the Database
+.. i18n: ---------------------
+..
+
+.. _sect-creatingdb:
+
+Creating the Database
+---------------------
+
+.. i18n: If you are using the GTK client, choose :menuselection:`File --> Databases --> New database` in
+.. i18n: the menu at the top left. Enter the super-administrator password, then the name of the new database
+.. i18n: you are creating.
+..
+
+If you are using the GTK client, choose :menuselection:`File --> Databases --> New database` in
+the menu at the top left. Enter the super-administrator password, then the name of the new database
+you are creating.
+
+.. i18n: .. figure:: images/create_new_db_GTK.png
+.. i18n: :scale: 75
+.. i18n: :align: center
+.. i18n:
+.. i18n: *Creating a new database through the GTK client*
+..
+
+.. figure:: images/create_new_db_GTK.png
+ :scale: 75
+ :align: center
+
+ *Creating a new database through the GTK client*
+
+.. i18n: If you are using the web client, click :guilabel:`Databases` on the login screen, then
+.. i18n: :guilabel:`Create` on the database management page. Enter the super-administrator password, and the
+.. i18n: name of the new database you are creating.
+.. i18n:
+.. i18n: In both cases, you will see a checkbox that determines whether you load demonstration data or not.
+.. i18n: The consequences of checking this box or not affect the **whole use** of this database.
+..
+
+If you are using the web client, click :guilabel:`Databases` on the login screen, then
+:guilabel:`Create` on the database management page. Enter the super-administrator password, and the
+name of the new database you are creating.
+
+In both cases, you will see a checkbox that determines whether you load demonstration data or not.
+The consequences of checking this box or not affect the **whole use** of this database.
+
+.. i18n: In both cases, you will also see that you can choose the Administrator password. This makes your
+.. i18n: database quite secure because you can ensure that it is unique from the outset.
+.. i18n: (In fact many people find it hard to resist ``admin`` as their password!)
+..
+
+In both cases, you will also see that you can choose the Administrator password. This makes your
+database quite secure because you can ensure that it is unique from the outset.
+(In fact many people find it hard to resist ``admin`` as their password!)
+
+.. i18n: Database openerp_ch01
+.. i18n: ---------------------
+..
+
+Database openerp_ch01
+---------------------
+
+.. i18n: .. index::
+.. i18n: pair: account; user
+..
+
+.. index::
+ pair: account; user
+
+.. i18n: Wait for the message showing that the database has been successfully created, along with the user
+.. i18n: accounts and passwords (\ ``admin/XXXX``\ and \ ``demo/demo``\ ). Now that you have created this
+.. i18n: database, you can extend it without having to know the super-administrator password.
+..
+
+Wait for the message showing that the database has been successfully created, along with the user
+accounts and passwords (\ ``admin/XXXX``\ and \ ``demo/demo``\ ). Now that you have created this
+database, you can extend it without having to know the super-administrator password.
+
+.. i18n: .. index::
+.. i18n: single: access; LDAP
+.. i18n: single: LDAP
+.. i18n: pair: password; username
+.. i18n: single: access; user
+..
+
+.. index::
+ single: access; LDAP
+ single: LDAP
+ pair: password; username
+ single: access; user
+
+.. i18n: .. tip:: User Access
+.. i18n:
+.. i18n: The combination of username/password is specific to a single database. If you have administrative
+.. i18n: rights to a database you can modify all users.
+.. i18n:
+.. i18n: .. index::
+.. i18n: single: module; users_ldap
+.. i18n:
+.. i18n: Alternatively, you can install the :mod:`users_ldap` module, which manages the authentication of users
+.. i18n: in LDAP (the Lightweight Directory Access Protocol, a standard system), and connect it to several
+.. i18n: OpenERP databases. Using this, many databases can share the same user account details.
+..
+
+.. tip:: User Access
+
+ The combination of username/password is specific to a single database. If you have administrative
+ rights to a database you can modify all users.
+
+ .. index::
+ single: module; users_ldap
+
+ Alternatively, you can install the :mod:`users_ldap` module, which manages the authentication of users
+ in LDAP (the Lightweight Directory Access Protocol, a standard system), and connect it to several
+ OpenERP databases. Using this, many databases can share the same user account details.
+
+.. i18n: .. note:: Failure to Create a Database
+.. i18n:
+.. i18n: How do you know if you have successfully created your new database?
+.. i18n: You are told if the database creation has been unsuccessful.
+.. i18n: If you have entered a database name using prohibited characters (or no name, or too short a name),
+.. i18n: you will be alerted by the dialog box :guilabel:`Bad database name!` explaining how to correct the error.
+.. i18n: If you have entered the wrong super-administrator password or a name already in use
+.. i18n: (some names can be reserved without your knowledge), you will be alerted by the dialog box
+.. i18n: :guilabel:`Error during database creation!`.
+..
+
+.. note:: Failure to Create a Database
+
+ How do you know if you have successfully created your new database?
+ You are told if the database creation has been unsuccessful.
+ If you have entered a database name using prohibited characters (or no name, or too short a name),
+ you will be alerted by the dialog box :guilabel:`Bad database name!` explaining how to correct the error.
+ If you have entered the wrong super-administrator password or a name already in use
+ (some names can be reserved without your knowledge), you will be alerted by the dialog box
+ :guilabel:`Error during database creation!`.
+
+.. i18n: Since this is the first time you have connected to this database, you will be asked a series of questions to
+.. i18n: define the database parameters. You may choose to :guilabel:`Skip Configuration Wizards` or
+.. i18n: :guilabel:`Start Configuration`. If you choose to configure your application, you may proceed with the
+.. i18n: following steps:
+..
+
+Since this is the first time you have connected to this database, you will be asked a series of questions to
+define the database parameters. You may choose to :guilabel:`Skip Configuration Wizards` or
+:guilabel:`Start Configuration`. If you choose to configure your application, you may proceed with the
+following steps:
+
+.. i18n: #. :guilabel:`Configure Your Interface` : select \ ``Simplified`` \ and click :guilabel:`Next`.
+.. i18n:
+.. i18n: #. :guilabel:`Configure Your Company Information` : replace the proposed default of \ ``OpenERP S.A.`` \
+.. i18n: by your own company name, complete as much of your address as you like. You can set the currency that
+.. i18n: your company uses or leave the default setting. You may also add your company logo which will
+.. i18n: be visible on reports and other documents. Click :guilabel:`Next`.
+.. i18n:
+.. i18n: #. :guilabel:`Install Applications` : check the applications you need and then click :guilabel:`Install`.
+.. i18n: For now, do not install any application.
+..
+
+ #. :guilabel:`Configure Your Interface` : select \ ``Simplified`` \ and click :guilabel:`Next`.
+
+ #. :guilabel:`Configure Your Company Information` : replace the proposed default of \ ``OpenERP S.A.`` \
+ by your own company name, complete as much of your address as you like. You can set the currency that
+ your company uses or leave the default setting. You may also add your company logo which will
+ be visible on reports and other documents. Click :guilabel:`Next`.
+
+ #. :guilabel:`Install Applications` : check the applications you need and then click :guilabel:`Install`.
+ For now, do not install any application.
+
+.. i18n: Once configuration is complete, you are connected to your OpenERP system. Its functionality is very
+.. i18n: limited because you have selected a :guilabel:`Simplified` interface with no application installed,
+.. i18n: but this is sufficient to demonstrate that your installation is working.
+..
+
+Once configuration is complete, you are connected to your OpenERP system. Its functionality is very
+limited because you have selected a :guilabel:`Simplified` interface with no application installed,
+but this is sufficient to demonstrate that your installation is working.
+
+.. i18n: .. figure:: images/define_main_co_dlg.png
+.. i18n: :align: center
+.. i18n: :scale: 80
+.. i18n:
+.. i18n: *Defining your company during initial database configuration*
+..
+
+.. figure:: images/define_main_co_dlg.png
+ :align: center
+ :scale: 80
+
+ *Defining your company during initial database configuration*
+
+.. i18n: .. index::
+.. i18n: single: database; manage
+..
+
+.. index::
+ single: database; manage
+
+.. i18n: .. _sect-dbmanage:
+.. i18n:
+.. i18n: Managing Databases
+.. i18n: ------------------
+..
+
+.. _sect-dbmanage:
+
+Managing Databases
+------------------
+
+.. i18n: As a super-administrator, you do not only have rights to create new databases, but also to:
+..
+
+As a super-administrator, you do not only have rights to create new databases, but also to:
+
+.. i18n: * backup databases,
+.. i18n:
+.. i18n: * delete databases,
+.. i18n:
+.. i18n: * restore databases.
+..
+
+* backup databases,
+
+* delete databases,
+
+* restore databases.
+
+.. i18n: All of these operations can be carried out from the menu :menuselection:`File --> Databases...`
+.. i18n: in the GTK client, or from the :guilabel:`Databases` button in the web client's
+.. i18n: :guilabel:`Login` screen.
+..
+
+All of these operations can be carried out from the menu :menuselection:`File --> Databases...`
+in the GTK client, or from the :guilabel:`Databases` button in the web client's
+:guilabel:`Login` screen.
+
+.. i18n: .. index::
+.. i18n: single: database; backup
+..
+
+.. index::
+ single: database; backup
+
+.. i18n: .. tip:: Backup (copy) a Database
+.. i18n:
+.. i18n: To make a copy of a database, go to the web :guilabel:`Login` screen and click the :guilabel:`Databases` button.
+.. i18n: Then click the :guilabel:`Backup` button, select the database you want to copy and enter the super-administrator
+.. i18n: password. Click the :guilabel:`Backup` button to confirm that you want to copy the database.
+..
+
+.. tip:: Backup (copy) a Database
+
+ To make a copy of a database, go to the web :guilabel:`Login` screen and click the :guilabel:`Databases` button.
+ Then click the :guilabel:`Backup` button, select the database you want to copy and enter the super-administrator
+ password. Click the :guilabel:`Backup` button to confirm that you want to copy the database.
+
+.. i18n: .. index::
+.. i18n: single: database; drop
+..
+
+.. index::
+ single: database; drop
+
+.. i18n: .. tip:: Drop (delete) a Database
+.. i18n:
+.. i18n: To delete a database, go to the web :guilabel:`Login` screen and click the :guilabel:`Databases` button.
+.. i18n: Then click the :guilabel:`Drop` button, select the database you want to delete and enter the super-administrator
+.. i18n: password. Click the :guilabel:`Drop` button to confirm that you want to delete the database.
+..
+
+.. tip:: Drop (delete) a Database
+
+ To delete a database, go to the web :guilabel:`Login` screen and click the :guilabel:`Databases` button.
+ Then click the :guilabel:`Drop` button, select the database you want to delete and enter the super-administrator
+ password. Click the :guilabel:`Drop` button to confirm that you want to delete the database.
+
+.. i18n: .. index::
+.. i18n: single: database; restore
+..
+
+.. index::
+ single: database; restore
+
+.. i18n: .. tip:: Restore a Database
+.. i18n:
+.. i18n: To restore a database, go to the web :guilabel:`Login` screen and click the :guilabel:`Databases` button.
+.. i18n: Then click the :guilabel:`Restore` button, click the :guilabel:`Choose File` button to select the database
+.. i18n: you want to restore. Give the database a name and enter the super-administrator password.
+.. i18n: Click the :guilabel:`Restore` button to confirm that you want to install a new copy of the selected database.
+.. i18n: To restore a database, you need to have an existing copy, of course.
+..
+
+.. tip:: Restore a Database
+
+ To restore a database, go to the web :guilabel:`Login` screen and click the :guilabel:`Databases` button.
+ Then click the :guilabel:`Restore` button, click the :guilabel:`Choose File` button to select the database
+ you want to restore. Give the database a name and enter the super-administrator password.
+ Click the :guilabel:`Restore` button to confirm that you want to install a new copy of the selected database.
+ To restore a database, you need to have an existing copy, of course.
+
+.. i18n: .. index::
+.. i18n: single: database; duplicate
+..
+
+.. index::
+ single: database; duplicate
+
+.. i18n: .. tip:: Duplicating a Database
+.. i18n:
+.. i18n: To duplicate a database, you can:
+.. i18n:
+.. i18n: #. make a backup file on your PC from this database.
+.. i18n:
+.. i18n: #. restore this database from the backup file on your PC, and give it a new name.
+.. i18n:
+.. i18n: This can be a useful way of making a test database from a production database. You can try out the
+.. i18n: operation of a new configuration, new modules, or just the import of new data.
+..
+
+.. tip:: Duplicating a Database
+
+ To duplicate a database, you can:
+
+ #. make a backup file on your PC from this database.
+
+ #. restore this database from the backup file on your PC, and give it a new name.
+
+ This can be a useful way of making a test database from a production database. You can try out the
+ operation of a new configuration, new modules, or just the import of new data.
+
+.. i18n: .. index::
+.. i18n: single: access
+..
+
+.. index::
+ single: access
+
+.. i18n: A system administrator can configure OpenERP to restrict access to some of these database functions
+.. i18n: so that your security is enhanced in normal production use.
+..
+
+A system administrator can configure OpenERP to restrict access to some of these database functions
+so that your security is enhanced in normal production use.
+
+.. i18n: You are now ready to use databases from your installation to familiarize yourself with the
+.. i18n: administration and use of OpenERP.
+..
+
+You are now ready to use databases from your installation to familiarize yourself with the
+administration and use of OpenERP.
+
+.. i18n: New OpenERP Functionality
+.. i18n: =========================
+..
+
+New OpenERP Functionality
+=========================
+
+.. i18n: The database you have created and managed so far is based on the core OpenERP functionality that you
+.. i18n: installed. The core system is installed in the file system of your OpenERP application server, but
+.. i18n: only installed into an OpenERP database as you require it, as is described in the next chapter, :ref:`ch-guided`.
+..
+
+The database you have created and managed so far is based on the core OpenERP functionality that you
+installed. The core system is installed in the file system of your OpenERP application server, but
+only installed into an OpenERP database as you require it, as is described in the next chapter, :ref:`ch-guided`.
+
+.. i18n: What if you want to update what is there, or extend what is there with additional modules?
+..
+
+What if you want to update what is there, or extend what is there with additional modules?
+
+.. i18n: * To update what you have, you would install a new instance of OpenERP using the same techniques as
+.. i18n: described earlier in this section, :ref:`sect-dbcreate`.
+.. i18n:
+.. i18n: * To extend what you have, you would install new modules in the ``addons`` directory of your current
+.. i18n: OpenERP installation. There are several ways of doing that.
+..
+
+* To update what you have, you would install a new instance of OpenERP using the same techniques as
+ described earlier in this section, :ref:`sect-dbcreate`.
+
+* To extend what you have, you would install new modules in the ``addons`` directory of your current
+ OpenERP installation. There are several ways of doing that.
+
+.. i18n: .. index::
+.. i18n: pair: system; administrator
+..
+
+.. index::
+ pair: system; administrator
+
+.. i18n: In both cases you will need to be a \ ``root`` \ user or \ ``Administrator`` \ of your
+.. i18n: OpenERP application server.
+..
+
+In both cases you will need to be a \ ``root`` \ user or \ ``Administrator`` \ of your
+OpenERP application server.
+
+.. i18n: Extending OpenERP
+.. i18n: -----------------
+..
+
+Extending OpenERP
+-----------------
+
+.. i18n: To extend OpenERP you will need to copy modules into the \ ``addons`` \ directory. That is in
+.. i18n: your server's \ ``openerp-server`` \ directory (which differs between Windows, Mac and some of the
+.. i18n: various Linux distributions and not available at all in the Windows all-in-one installer).
+..
+
+To extend OpenERP you will need to copy modules into the \ ``addons`` \ directory. That is in
+your server's \ ``openerp-server`` \ directory (which differs between Windows, Mac and some of the
+various Linux distributions and not available at all in the Windows all-in-one installer).
+
+.. i18n: .. index::
+.. i18n: single: module; product
+.. i18n: single: module; purchase
+..
+
+.. index::
+ single: module; product
+ single: module; purchase
+
+.. i18n: If you look there you will see existing modules such as :mod:`product` and :mod:`purchase`. A
+.. i18n: module can be provided in the form of files within a directory or a a zip-format file containing
+.. i18n: that same directory structure.
+..
+
+If you look there you will see existing modules such as :mod:`product` and :mod:`purchase`. A
+module can be provided in the form of files within a directory or a a zip-format file containing
+that same directory structure.
+
+.. i18n: You can add modules in two main ways – through the server, or through the client.
+..
+
+You can add modules in two main ways – through the server, or through the client.
+
+.. i18n: .. index::
+.. i18n: pair: system; administration
+..
+
+.. index::
+ pair: system; administration
+
+.. i18n: To add new modules through the server is a conventional system administration task. As \ ``root`` \
+.. i18n: user or another suitable user, you would put the module in the \ ``addons`` \ directory and change its
+.. i18n: permissions to match those of the other modules.
+..
+
+To add new modules through the server is a conventional system administration task. As \ ``root`` \
+user or another suitable user, you would put the module in the \ ``addons`` \ directory and change its
+permissions to match those of the other modules.
+
+.. i18n: To add new modules through the client you must first change the permissions of the \ ``addons`` \
+.. i18n: directory of the server, so that it is writeable by the server. That will enable you to install
+.. i18n: OpenERP modules using the OpenERP client (a task ultimately carried out on the application
+.. i18n: server by the server software).
+..
+
+To add new modules through the client you must first change the permissions of the \ ``addons`` \
+directory of the server, so that it is writeable by the server. That will enable you to install
+OpenERP modules using the OpenERP client (a task ultimately carried out on the application
+server by the server software).
+
+.. i18n: .. index::
+.. i18n: pair: filesystem; permissions
+..
+
+.. index::
+ pair: filesystem; permissions
+
+.. i18n: .. tip:: Changing Permissions
+.. i18n:
+.. i18n: A very simple way of changing permissions on the Linux system you are using to develop an OpenERP
+.. i18n: application is to execute the command sudo chmod 777 <path_to_addons> (where <path_to_addons> is
+.. i18n: the full path to the addons directory, a location like /usr/lib/python2.5/site-packages/openerp-
+.. i18n: server/addons).
+..
+
+.. tip:: Changing Permissions
+
+ A very simple way of changing permissions on the Linux system you are using to develop an OpenERP
+ application is to execute the command sudo chmod 777 <path_to_addons> (where <path_to_addons> is
+ the full path to the addons directory, a location like /usr/lib/python2.5/site-packages/openerp-
+ server/addons).
+
+.. i18n: Any user of OpenERP who has access to the relevant administration menus can then upload any new
+.. i18n: functionality, so you would certainly disable this capability for production use. You will see examples of
+.. i18n: this uploading as you make your way through this book.
+..
+
+Any user of OpenERP who has access to the relevant administration menus can then upload any new
+functionality, so you would certainly disable this capability for production use. You will see examples of
+this uploading as you make your way through this book.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_install.rst'
--- i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_install.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_1_Inst_Config/1_1_Inst_Config_install.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,1342 @@
+
+.. i18n: The Installation of OpenERP
+.. i18n: ===========================
+..
+
+The Installation of OpenERP
+===========================
+
+.. i18n: Whether you are from a small company investigating how OpenERP works, or you are part of the IT staff of a
+.. i18n: larger organization and have been asked to assess OpenERP's capabilities, your first requirement
+.. i18n: is to install it or to find a working installation.
+..
+
+Whether you are from a small company investigating how OpenERP works, or you are part of the IT staff of a
+larger organization and have been asked to assess OpenERP's capabilities, your first requirement
+is to install it or to find a working installation.
+
+.. i18n: The table below summarizes the various installation methods that will be described in the following
+.. i18n: sections.
+..
+
+The table below summarizes the various installation methods that will be described in the following
+sections.
+
+.. i18n: .. csv-table:: Comparison of the different methods of installation on Windows or Linux
+.. i18n: :header: "Method","Average Time","Level of Complexity","Notes"
+.. i18n: :widths: 20,15,15,30
+.. i18n:
+.. i18n: "OpenERP Demo","No installation","Simple","Very useful for quick evaluations because no need to install anything."
+.. i18n: "All-in-one Windows Installer","A few minutes","Simple","Very useful for quick evaluations because it installs all of the components pre-configured on one computer (using the GTK client)."
+.. i18n: "Independent installation on Windows","Half an hour","Medium","Enables you to install the components on different computers. Can be put into production use."
+.. i18n: "Ubuntu Linux packages","A few minutes","Simple","Simple and quick but the Ubuntu packages are not always up to date."
+.. i18n: "From source, for all Linux systems","More than half an hour","Medium to slightly difficult","This is the method recommended for production environments because it is easy to keep it up to date."
+..
+
+.. csv-table:: Comparison of the different methods of installation on Windows or Linux
+ :header: "Method","Average Time","Level of Complexity","Notes"
+ :widths: 20,15,15,30
+
+ "OpenERP Demo","No installation","Simple","Very useful for quick evaluations because no need to install anything."
+ "All-in-one Windows Installer","A few minutes","Simple","Very useful for quick evaluations because it installs all of the components pre-configured on one computer (using the GTK client)."
+ "Independent installation on Windows","Half an hour","Medium","Enables you to install the components on different computers. Can be put into production use."
+ "Ubuntu Linux packages","A few minutes","Simple","Simple and quick but the Ubuntu packages are not always up to date."
+ "From source, for all Linux systems","More than half an hour","Medium to slightly difficult","This is the method recommended for production environments because it is easy to keep it up to date."
+
+.. i18n: Each time a new release of OpenERP is made, OpenERP supplies a complete Windows auto-installer for
+.. i18n: it. This contains all of the components you need – the PostgreSQL database server, the OpenERP
+.. i18n: application server and the GTK application client.
+..
+
+Each time a new release of OpenERP is made, OpenERP supplies a complete Windows auto-installer for
+it. This contains all of the components you need – the PostgreSQL database server, the OpenERP
+application server and the GTK application client.
+
+.. i18n: This auto-installer enables you to install the whole system in just a few mouse clicks. The initial
+.. i18n: configuration is set up during installation, making it possible to start using it very quickly as
+.. i18n: long as you do not want to change the underlying code. It is aimed at the installation of everything
+.. i18n: on a single PC, but you can later connect GTK clients from other PCs, Macs and Linux boxes to it as
+.. i18n: well.
+..
+
+This auto-installer enables you to install the whole system in just a few mouse clicks. The initial
+configuration is set up during installation, making it possible to start using it very quickly as
+long as you do not want to change the underlying code. It is aimed at the installation of everything
+on a single PC, but you can later connect GTK clients from other PCs, Macs and Linux boxes to it as
+well.
+
+.. i18n: The first step is to download the OpenERP installer. At this stage you must choose which version
+.. i18n: to install – the stable version or the development version. If you are planning to put it straight
+.. i18n: into production we strongly advise you to choose the stable version.
+..
+
+The first step is to download the OpenERP installer. At this stage you must choose which version
+to install – the stable version or the development version. If you are planning to put it straight
+into production we strongly advise you to choose the stable version.
+
+.. i18n: .. index::
+.. i18n: single: stable versions
+..
+
+.. index::
+ single: stable versions
+
+.. i18n: .. note:: Stable Versions and Development Versions
+.. i18n:
+.. i18n: OpenERP development proceeds in two parallel tracks: stable versions and development versions.
+.. i18n:
+.. i18n: New functionality is integrated into the development branch. This branch is more advanced than the
+.. i18n: stable branch, but it can contain undiscovered and unfixed faults. A new development release is
+.. i18n: made every month or so, and OpenERP has made the code repository available so you can download the
+.. i18n: very latest revisions if you want.
+.. i18n:
+.. i18n: The stable branch is designed for production environments. Releases of new functionality there are
+.. i18n: made only about once a year after a long period of testing and validation. Only bug fixes are
+.. i18n: released through the year on the stable branch.
+..
+
+.. note:: Stable Versions and Development Versions
+
+ OpenERP development proceeds in two parallel tracks: stable versions and development versions.
+
+ New functionality is integrated into the development branch. This branch is more advanced than the
+ stable branch, but it can contain undiscovered and unfixed faults. A new development release is
+ made every month or so, and OpenERP has made the code repository available so you can download the
+ very latest revisions if you want.
+
+ The stable branch is designed for production environments. Releases of new functionality there are
+ made only about once a year after a long period of testing and validation. Only bug fixes are
+ released through the year on the stable branch.
+
+.. i18n: .. index::
+.. i18n: single: installation; Windows (all-in-one)
+..
+
+.. index::
+ single: installation; Windows (all-in-one)
+
+.. i18n: To download the version of OpenERP for Windows, follow these steps:
+..
+
+To download the version of OpenERP for Windows, follow these steps:
+
+.. i18n: #. Navigate to the site http://openerp.com.
+.. i18n:
+.. i18n: #. Click the :menuselection:`Downloads` button at the right, then, under :guilabel:`Windows Auto-Installer`, select
+.. i18n: :menuselection:`All-in-One`.
+.. i18n:
+.. i18n: #. This brings up the demonstration version Windows installer,
+.. i18n: currently :program:`openerp-allinone-setup-6.0.0`.
+.. i18n:
+.. i18n: #. Save the file on your PC - it is quite a substantial size because it downloads everything including
+.. i18n: the PostgreSQL database system, so it will take some time.
+..
+
+#. Navigate to the site http://openerp.com.
+
+#. Click the :menuselection:`Downloads` button at the right, then, under :guilabel:`Windows Auto-Installer`, select
+ :menuselection:`All-in-One`.
+
+#. This brings up the demonstration version Windows installer,
+ currently :program:`openerp-allinone-setup-6.0.0`.
+
+#. Save the file on your PC - it is quite a substantial size because it downloads everything including
+ the PostgreSQL database system, so it will take some time.
+
+.. i18n: .. index::
+.. i18n: single: installation; administrator
+..
+
+.. index::
+ single: installation; administrator
+
+.. i18n: To install OpenERP and its database, you must be signed in as an Administrator on your PC. Double-
+.. i18n: click the installer file to install it and accept the default parameters on each dialog box as you go.
+..
+
+To install OpenERP and its database, you must be signed in as an Administrator on your PC. Double-
+click the installer file to install it and accept the default parameters on each dialog box as you go.
+
+.. i18n: If you had previously tried to install the all-in-one version of OpenERP, you will have to uninstall
+.. i18n: that first, because various elements of a previous installation could interfere with your new installation.
+.. i18n: Make sure that all Tiny ERP, OpenERP and PostgreSQL applications are removed:
+.. i18n: you are likely to have to restart your PC to finish removing all traces of them.
+..
+
+If you had previously tried to install the all-in-one version of OpenERP, you will have to uninstall
+that first, because various elements of a previous installation could interfere with your new installation.
+Make sure that all Tiny ERP, OpenERP and PostgreSQL applications are removed:
+you are likely to have to restart your PC to finish removing all traces of them.
+
+.. i18n: The OpenERP client can be opened, ready to use the OpenERP system, once you have completed
+.. i18n: the all-in-one installation. The next step consists
+.. i18n: of setting up the database, and is covered in the final section of this chapter :ref:`sect-creatingdb`.
+..
+
+The OpenERP client can be opened, ready to use the OpenERP system, once you have completed
+the all-in-one installation. The next step consists
+of setting up the database, and is covered in the final section of this chapter :ref:`sect-creatingdb`.
+
+.. i18n: .. index::
+.. i18n: single: installation; Windows (independent)
+..
+
+.. index::
+ single: installation; Windows (independent)
+
+.. i18n: Independent Installation on Windows
+.. i18n: -----------------------------------
+..
+
+Independent Installation on Windows
+-----------------------------------
+
+.. i18n: System administrators can have very good reasons for wanting to install the various components of a
+.. i18n: Windows installation separately. For example, your company may not support the version of PostgreSQL
+.. i18n: or Python that is installed automatically, or you may already have PostgreSQL installed on the server
+.. i18n: you are using, or you may want to install the database server and application server on
+.. i18n: separate hardware units.
+..
+
+System administrators can have very good reasons for wanting to install the various components of a
+Windows installation separately. For example, your company may not support the version of PostgreSQL
+or Python that is installed automatically, or you may already have PostgreSQL installed on the server
+you are using, or you may want to install the database server and application server on
+separate hardware units.
+
+.. i18n: For this situation, you can get a separate installer for the OpenERP server from the same
+.. i18n: location as the all-in-one auto-installer. You will also have to download and install a suitable
+.. i18n: version of PostgreSQL independently.
+..
+
+For this situation, you can get a separate installer for the OpenERP server from the same
+location as the all-in-one auto-installer. You will also have to download and install a suitable
+version of PostgreSQL independently.
+
+.. i18n: You must install PostgreSQL before the OpenERP server, and you must also set it up with a user
+.. i18n: and password so that the OpenERP server can connect to it. OpenERP's web-based documentation gives
+.. i18n: full and current details.
+..
+
+You must install PostgreSQL before the OpenERP server, and you must also set it up with a user
+and password so that the OpenERP server can connect to it. OpenERP's web-based documentation gives
+full and current details.
+
+.. i18n: Connecting Users on Other PCs to the OpenERP Server
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+..
+
+Connecting Users on Other PCs to the OpenERP Server
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: To connect other computers to the OpenERP server, you must set the server up so that it is
+.. i18n: visible to the other PCs, and install a GTK client on each of those PCs:
+..
+
+To connect other computers to the OpenERP server, you must set the server up so that it is
+visible to the other PCs, and install a GTK client on each of those PCs:
+
+.. i18n: #. Make your OpenERP server visible to other PCs by opening the Windows Firewall in the Control
+.. i18n: Panel, then ask the firewall to make an exception of the OpenERP server. In the
+.. i18n: :guilabel:`Exceptions` tab of Windows Firewall click :guilabel:`Add a program...` and choose
+.. i18n: :guilabel:`OpenERP Server` in the list provided. This step enables other computers to see the
+.. i18n: OpenERP application on this server.
+.. i18n:
+.. i18n: #. Install the OpenERP client (:program:`openerp-client-6.X.exe`), which you can download in the
+.. i18n: same way as you downloaded the other OpenERP software, onto the other PCs.
+..
+
+#. Make your OpenERP server visible to other PCs by opening the Windows Firewall in the Control
+ Panel, then ask the firewall to make an exception of the OpenERP server. In the
+ :guilabel:`Exceptions` tab of Windows Firewall click :guilabel:`Add a program...` and choose
+ :guilabel:`OpenERP Server` in the list provided. This step enables other computers to see the
+ OpenERP application on this server.
+
+#. Install the OpenERP client (:program:`openerp-client-6.X.exe`), which you can download in the
+ same way as you downloaded the other OpenERP software, onto the other PCs.
+
+.. i18n: .. tip:: Version Matching
+.. i18n:
+.. i18n: You must make sure that the version of the client matches that of the server. The version number is
+.. i18n: given as part of the name of the downloaded file. Although it is possible that some different
+.. i18n: revisions of client and server will function together, there is no certainty about that.
+..
+
+.. tip:: Version Matching
+
+ You must make sure that the version of the client matches that of the server. The version number is
+ given as part of the name of the downloaded file. Although it is possible that some different
+ revisions of client and server will function together, there is no certainty about that.
+
+.. i18n: .. index::
+.. i18n: single: administrator
+..
+
+.. index::
+ single: administrator
+
+.. i18n: To run the client installer on every other PC you will need to have administrator rights there. The
+.. i18n: installation is automated, so you just need follow the different installation steps.
+..
+
+To run the client installer on every other PC you will need to have administrator rights there. The
+installation is automated, so you just need follow the different installation steps.
+
+.. i18n: To test your installation, start by connecting through the OpenERP client on the server machine
+.. i18n: while you are still logged in as administrator.
+..
+
+To test your installation, start by connecting through the OpenERP client on the server machine
+while you are still logged in as administrator.
+
+.. i18n: .. note:: Why sign in as a PC Administrator?
+.. i18n:
+.. i18n: You would not usually be signed in as a PC administrator when you are just running the OpenERP client,
+.. i18n: but if there have been problems in the installation it is easier to remain as an administrator after
+.. i18n: the installation so that you can make any necessary fixes than to switch users as you alternate
+.. i18n: between roles as a tester and a software installer.
+..
+
+.. note:: Why sign in as a PC Administrator?
+
+ You would not usually be signed in as a PC administrator when you are just running the OpenERP client,
+ but if there have been problems in the installation it is easier to remain as an administrator after
+ the installation so that you can make any necessary fixes than to switch users as you alternate
+ between roles as a tester and a software installer.
+
+.. i18n: Start the GTK client on the server through the Windows Start menu there. The main client window
+.. i18n: appears, identifying the server you are connected to (which is \ ``localhost``\ – your own server
+.. i18n: PC – by default). If the message :guilabel:`No database found, you must create one` appears then
+.. i18n: you have **successfully connected** to an OpenERP server containing, as yet, no databases.
+..
+
+Start the GTK client on the server through the Windows Start menu there. The main client window
+appears, identifying the server you are connected to (which is \ ``localhost``\ – your own server
+PC – by default). If the message :guilabel:`No database found, you must create one` appears then
+you have **successfully connected** to an OpenERP server containing, as yet, no databases.
+
+.. i18n: .. figure:: images/new_login_dlg.png
+.. i18n: :align: center
+.. i18n: :scale: 75
+.. i18n:
+.. i18n: *Dialog box on connecting a GTK client to a new OpenERP server*
+..
+
+.. figure:: images/new_login_dlg.png
+ :align: center
+ :scale: 75
+
+ *Dialog box on connecting a GTK client to a new OpenERP server*
+
+.. i18n: .. index::
+.. i18n: single: protocol; XML-RPC
+.. i18n: single: protocol; NET-RPC
+.. i18n: single: XML-RPC
+.. i18n: single: NET-RPC
+..
+
+.. index::
+ single: protocol; XML-RPC
+ single: protocol; NET-RPC
+ single: XML-RPC
+ single: NET-RPC
+
+.. i18n: .. note:: Connection Modes
+.. i18n:
+.. i18n: In its default configuration at the time of writing,
+.. i18n: the OpenERP client connects to port 8069 on the server using the
+.. i18n: XML-RPC protocol (from Linux) or port 8070 using the NET-RPC protocol instead (from Windows).
+.. i18n: You can use any protocol from either operating system.
+.. i18n: NET-RPC is quite a bit quicker, although you may not notice that on the GTK client in normal use.
+.. i18n: OpenERP can run XML-RPC, but not NET-RPC, as a secure connection.
+.. i18n:
+.. i18n: Resolving Errors with a Windows Installation
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+..
+
+.. note:: Connection Modes
+
+ In its default configuration at the time of writing,
+ the OpenERP client connects to port 8069 on the server using the
+ XML-RPC protocol (from Linux) or port 8070 using the NET-RPC protocol instead (from Windows).
+ You can use any protocol from either operating system.
+ NET-RPC is quite a bit quicker, although you may not notice that on the GTK client in normal use.
+ OpenERP can run XML-RPC, but not NET-RPC, as a secure connection.
+
+Resolving Errors with a Windows Installation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: If you cannot get OpenERP to work after installing your Windows system you will find some ideas for
+.. i18n: resolving this below:
+..
+
+If you cannot get OpenERP to work after installing your Windows system you will find some ideas for
+resolving this below:
+
+.. i18n: #. Is the OpenERP Server working? Signed in to the server as an administrator, stop and
+.. i18n: restart the service using :guilabel:`Stop Service` and :guilabel:`Start Service` from the menu
+.. i18n: :menuselection:`Start --> Programs --> OpenERP Server` .
+.. i18n:
+.. i18n: #. Is the OpenERP Server set up correctly? Signed in to the server as
+.. i18n: Administrator, open the file \ ``openerp-server.conf``\ in \
+.. i18n: ``C:\Program Files\OpenERP AllInOne``\ and check its content. This file is generated during
+.. i18n: installation with information derived from the database. If you see something strange it is best to
+.. i18n: entirely reinstall the server from the demonstration installer rather than try to work out what is
+.. i18n: happening.
+..
+
+#. Is the OpenERP Server working? Signed in to the server as an administrator, stop and
+ restart the service using :guilabel:`Stop Service` and :guilabel:`Start Service` from the menu
+ :menuselection:`Start --> Programs --> OpenERP Server` .
+
+#. Is the OpenERP Server set up correctly? Signed in to the server as
+ Administrator, open the file \ ``openerp-server.conf``\ in \
+ ``C:\Program Files\OpenERP AllInOne``\ and check its content. This file is generated during
+ installation with information derived from the database. If you see something strange it is best to
+ entirely reinstall the server from the demonstration installer rather than try to work out what is
+ happening.
+
+.. i18n: .. figure:: images/terp_server_conf.png
+.. i18n: :align: center
+.. i18n: :scale: 80
+.. i18n:
+.. i18n: *Typical OpenERP configuration file*
+..
+
+ .. figure:: images/terp_server_conf.png
+ :align: center
+ :scale: 80
+
+ *Typical OpenERP configuration file*
+
+.. i18n: #. Is your PostgreSQL running? Signed in as administrator, select :guilabel:`Stop Service`
+.. i18n: from the menu :menuselection:`Start --> Programs --> PostgreSQL`. If after a couple of seconds,
+.. i18n: you read :guilabel:`The PostgreSQL4OpenERP service has stopped` then you can be reasonably sure
+.. i18n: that the database server was working. Restart PostgreSQL.
+.. i18n:
+.. i18n: #. Is the database accessible? Still in the PostgreSQL menu, start
+.. i18n: the pgAdmin III application which you can use to explore the database. Double-click the \
+.. i18n: ``PostgreSQL4OpenERP``\ connection.
+.. i18n: You can find the password in the OpenERP server configuration file.
+.. i18n: If the database server is accessible
+.. i18n: you will be able to see some information about the empty database. If it is not, an error message
+.. i18n: will appear.
+.. i18n:
+.. i18n: #. Are your client programs correctly installed? If your OpenERP GTK clients have not started,
+.. i18n: the swiftest approach is to reinstall them.
+.. i18n:
+.. i18n: #. Can remote client computers see the server computer at all? Check this by opening a command prompt
+.. i18n: window (enter \ ``cmd``\ in the window :menuselection:`Start --> Run...` ) and enter \ ``ping
+.. i18n: <address of server>``\ there (where \ ``<address of server>``\ represents the IP address of the
+.. i18n: server). The server should respond with a reply.
+.. i18n:
+.. i18n: #. Have you changed any of the server's parameters? At this point in the installation the port
+.. i18n: number of the server must be 8069 using the protocol XML-RPC.
+.. i18n:
+.. i18n: #. Is there anything else in the server's history that can help you identify the problem? Open the file
+.. i18n: \ ``openerp-server.log``\ in \ ``C:\Program Files\OpenERP AllInOne``\
+.. i18n: (which you can only do when the server is stopped) and scan through the
+.. i18n: history for ideas. If something looks strange there, contributors to the OpenERP forums can often
+.. i18n: help identify the reason.
+..
+
+#. Is your PostgreSQL running? Signed in as administrator, select :guilabel:`Stop Service`
+ from the menu :menuselection:`Start --> Programs --> PostgreSQL`. If after a couple of seconds,
+ you read :guilabel:`The PostgreSQL4OpenERP service has stopped` then you can be reasonably sure
+ that the database server was working. Restart PostgreSQL.
+
+#. Is the database accessible? Still in the PostgreSQL menu, start
+ the pgAdmin III application which you can use to explore the database. Double-click the \
+ ``PostgreSQL4OpenERP``\ connection.
+ You can find the password in the OpenERP server configuration file.
+ If the database server is accessible
+ you will be able to see some information about the empty database. If it is not, an error message
+ will appear.
+
+#. Are your client programs correctly installed? If your OpenERP GTK clients have not started,
+ the swiftest approach is to reinstall them.
+
+#. Can remote client computers see the server computer at all? Check this by opening a command prompt
+ window (enter \ ``cmd``\ in the window :menuselection:`Start --> Run...` ) and enter \ ``ping
+ <address of server>``\ there (where \ ``<address of server>``\ represents the IP address of the
+ server). The server should respond with a reply.
+
+#. Have you changed any of the server's parameters? At this point in the installation the port
+ number of the server must be 8069 using the protocol XML-RPC.
+
+#. Is there anything else in the server's history that can help you identify the problem? Open the file
+ \ ``openerp-server.log``\ in \ ``C:\Program Files\OpenERP AllInOne``\
+ (which you can only do when the server is stopped) and scan through the
+ history for ideas. If something looks strange there, contributors to the OpenERP forums can often
+ help identify the reason.
+
+.. i18n: .. index::
+.. i18n: single: installation; Linux (Ubuntu)
+..
+
+.. index::
+ single: installation; Linux (Ubuntu)
+
+.. i18n: Installation on Linux (Ubuntu)
+.. i18n: ------------------------------
+..
+
+Installation on Linux (Ubuntu)
+------------------------------
+
+.. i18n: This section guides you through installing the OpenERP server and client on Ubuntu, one of the
+.. i18n: most popular Linux distributions. It assumes that you are using a recent release of Desktop Ubuntu
+.. i18n: with its graphical user interface on a desktop or laptop PC.
+..
+
+This section guides you through installing the OpenERP server and client on Ubuntu, one of the
+most popular Linux distributions. It assumes that you are using a recent release of Desktop Ubuntu
+with its graphical user interface on a desktop or laptop PC.
+
+.. i18n: .. note:: Other Linux Distributions
+.. i18n:
+.. i18n: Installation on other distributions of Linux is fairly similar to installation on Ubuntu. Read this
+.. i18n: section of the book so that you understand the principles, then use the online documentation and
+.. i18n: the forums for your specific needs on another distribution.
+..
+
+.. note:: Other Linux Distributions
+
+ Installation on other distributions of Linux is fairly similar to installation on Ubuntu. Read this
+ section of the book so that you understand the principles, then use the online documentation and
+ the forums for your specific needs on another distribution.
+
+.. i18n: For information about installation on other distributions, visit the documentation section by
+.. i18n: following :menuselection:`Services --> Documentation` on http://www.openerp.com. Detailed instructions
+.. i18n: are given there for different distributions and releases, and you should also check if there are
+.. i18n: more up to date instructions for the Ubuntu distribution as well.
+..
+
+For information about installation on other distributions, visit the documentation section by
+following :menuselection:`Services --> Documentation` on http://www.openerp.com. Detailed instructions
+are given there for different distributions and releases, and you should also check if there are
+more up to date instructions for the Ubuntu distribution as well.
+
+.. i18n: .. To Check
+..
+
+.. To Check
+
+.. i18n: .. _installation-ubuntu-9.04:
+..
+
+.. _installation-ubuntu-9.04:
+
+.. i18n: Technical Procedure: Initial Installation and Configuration
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+..
+
+Technical Procedure: Initial Installation and Configuration
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: Upgrade of Ubuntu packages and installation of OpenERP and pgadmin::
+.. i18n:
+.. i18n: $ sudo apt-get update
+.. i18n:
+.. i18n: $ sudo apt-get upgrade
+.. i18n:
+.. i18n: $ sudo apt-get install openerp-server openerp-client pgadmin3
+..
+
+Upgrade of Ubuntu packages and installation of OpenERP and pgadmin::
+
+ $ sudo apt-get update
+
+ $ sudo apt-get upgrade
+
+ $ sudo apt-get install openerp-server openerp-client pgadmin3
+
+.. i18n: To avoid having some of the labels untranslated in the GTK client, install the language-pack-gnome-YOURLANG-base package. The following command installs the Spanish language pack::
+.. i18n:
+.. i18n: $ sudo apt-get install language-pack-gnome-es-base
+..
+
+To avoid having some of the labels untranslated in the GTK client, install the language-pack-gnome-YOURLANG-base package. The following command installs the Spanish language pack::
+
+ $ sudo apt-get install language-pack-gnome-es-base
+
+.. i18n: PostgreSQL version 8.4 has been used at the time of writing. You may have to replace the version number in the
+.. i18n: commands below with your own PostgreSQL version number if it differs. Postgres Database configuration::
+.. i18n:
+.. i18n: $ sudo vi /etc/postgresql/8.4/main/pg_hba.conf
+..
+
+PostgreSQL version 8.4 has been used at the time of writing. You may have to replace the version number in the
+commands below with your own PostgreSQL version number if it differs. Postgres Database configuration::
+
+ $ sudo vi /etc/postgresql/8.4/main/pg_hba.conf
+
+.. i18n: Replace the following line::
+.. i18n:
+.. i18n: # “local” is for Unix domain socket connections only
+.. i18n: local all all ident
+..
+
+Replace the following line::
+
+ # “local” is for Unix domain socket connections only
+ local all all ident
+
+.. i18n: with::
+.. i18n:
+.. i18n: #”local” is for Unix domain socket connections only
+.. i18n: local all all md5
+..
+
+with::
+
+ #”local” is for Unix domain socket connections only
+ local all all md5
+
+.. i18n: Restart Postgres::
+.. i18n:
+.. i18n: $ sudo /etc/init.d/postgresql-8.4 restart
+.. i18n:
+.. i18n: * Restarting PostgreSQL 8.4 database server [ OK ]
+..
+
+Restart Postgres::
+
+ $ sudo /etc/init.d/postgresql-8.4 restart
+
+ * Restarting PostgreSQL 8.4 database server [ OK ]
+
+.. i18n: The following two commands will avoid problems with /etc/init.d/openerp-web INIT script::
+.. i18n:
+.. i18n: $ sudo mkdir /home/openerp
+.. i18n:
+.. i18n: $ sudo chown openerp.nogroup /home/openerp
+..
+
+The following two commands will avoid problems with /etc/init.d/openerp-web INIT script::
+
+ $ sudo mkdir /home/openerp
+
+ $ sudo chown openerp.nogroup /home/openerp
+
+.. i18n: Create a user account called openerp with password “openerp” and with privileges to create Postgres databases::
+.. i18n:
+.. i18n: $ sudo su postgres
+.. i18n:
+.. i18n: $ createuser openerp -P
+.. i18n:
+.. i18n: Enter password for new role: (openerp)
+.. i18n:
+.. i18n: Enter it again:
+.. i18n:
+.. i18n: Shall the new role be a superuser? (y/n) n
+.. i18n:
+.. i18n: Shall the new role be allowed to create databases? (y/n) y
+.. i18n:
+.. i18n: Shall the new role be allowed to create more new roles? (y/n) n
+..
+
+Create a user account called openerp with password “openerp” and with privileges to create Postgres databases::
+
+ $ sudo su postgres
+
+ $ createuser openerp -P
+
+ Enter password for new role: (openerp)
+
+ Enter it again:
+
+ Shall the new role be a superuser? (y/n) n
+
+ Shall the new role be allowed to create databases? (y/n) y
+
+ Shall the new role be allowed to create more new roles? (y/n) n
+
+.. i18n: Quit from user postgres::
+.. i18n:
+.. i18n: $ exit
+.. i18n:
+.. i18n: exit
+..
+
+Quit from user postgres::
+
+ $ exit
+
+ exit
+
+.. i18n: Edit OpenERP configuration file::
+.. i18n:
+.. i18n: $ sudo vi /etc/openerp-server.conf
+..
+
+Edit OpenERP configuration file::
+
+ $ sudo vi /etc/openerp-server.conf
+
+.. i18n: Replace the following two lines (we don’t force to use a specific database and we add the required password to gain access to postgres)::
+.. i18n:
+.. i18n: db_name =
+.. i18n:
+.. i18n: db_user = openerp
+.. i18n:
+.. i18n: db_password = openerp
+..
+
+Replace the following two lines (we don’t force to use a specific database and we add the required password to gain access to postgres)::
+
+ db_name =
+
+ db_user = openerp
+
+ db_password = openerp
+
+.. i18n: We can now restart openerp-server::
+.. i18n:
+.. i18n: $ sudo /etc/init.d/openerp-server restart
+.. i18n:
+.. i18n: Restarting openerp-server: openerp-server.
+..
+
+We can now restart openerp-server::
+
+ $ sudo /etc/init.d/openerp-server restart
+
+ Restarting openerp-server: openerp-server.
+
+.. i18n: Check out the logs::
+.. i18n:
+.. i18n: $ sudo cat /var/log/openerp.log
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,314] INFO:server:version – 6.0.0
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,314] INFO:server:addons_path – /usr/lib/openerp-server/addons
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,314] INFO:server:database hostname – localhost
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,315] INFO:server:database port – 5432
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,315] INFO:server:database user – openerp
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,315] INFO:objects:initialising distributed objects services
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,502] INFO:web-services:starting XML-RPC services, port 8069
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,502] INFO:web-services:starting NET-RPC service, port 8070
+.. i18n:
+.. i18n: [2009-06-14 21:06:39,502] INFO:web-services:the server is running, waiting for connections…
+..
+
+Check out the logs::
+
+ $ sudo cat /var/log/openerp.log
+
+ [2009-06-14 21:06:39,314] INFO:server:version – 6.0.0
+
+ [2009-06-14 21:06:39,314] INFO:server:addons_path – /usr/lib/openerp-server/addons
+
+ [2009-06-14 21:06:39,314] INFO:server:database hostname – localhost
+
+ [2009-06-14 21:06:39,315] INFO:server:database port – 5432
+
+ [2009-06-14 21:06:39,315] INFO:server:database user – openerp
+
+ [2009-06-14 21:06:39,315] INFO:objects:initialising distributed objects services
+
+ [2009-06-14 21:06:39,502] INFO:web-services:starting XML-RPC services, port 8069
+
+ [2009-06-14 21:06:39,502] INFO:web-services:starting NET-RPC service, port 8070
+
+ [2009-06-14 21:06:39,502] INFO:web-services:the server is running, waiting for connections…
+
+.. i18n: OpenERP is now up and running, connected to Postgres database on port 5432 and listening on ports 8069 and 8070
+..
+
+OpenERP is now up and running, connected to Postgres database on port 5432 and listening on ports 8069 and 8070
+
+.. i18n: ::
+.. i18n:
+.. i18n: $ ps uaxww | grep -i openerp
+.. i18n:
+.. i18n: openerp 5686 0.0 1.2 84688 26584 pts/7 Sl+ 12:36 0:03 /usr/bin/python ./openerp-server.py
+..
+
+::
+
+ $ ps uaxww | grep -i openerp
+
+ openerp 5686 0.0 1.2 84688 26584 pts/7 Sl+ 12:36 0:03 /usr/bin/python ./openerp-server.py
+
+.. i18n: ::
+.. i18n:
+.. i18n: $ sudo lsof -i :8069
+.. i18n:
+.. i18n: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
+.. i18n:
+.. i18n: python 5686 openerp 3u IPv4 116555 0t0 TCP *:8069 (LISTEN)
+..
+
+::
+
+ $ sudo lsof -i :8069
+
+ COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
+
+ python 5686 openerp 3u IPv4 116555 0t0 TCP *:8069 (LISTEN)
+
+.. i18n: ::
+.. i18n:
+.. i18n: $ sudo lsof -i :8070
+.. i18n:
+.. i18n: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
+.. i18n:
+.. i18n: python 5686 openerp 5u IPv4 116563 0t0 TCP *:8070 (LISTEN)
+..
+
+::
+
+ $ sudo lsof -i :8070
+
+ COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
+
+ python 5686 openerp 5u IPv4 116563 0t0 TCP *:8070 (LISTEN)
+
+.. i18n: Start the OpenERP GTK client by clicking its icon in the :menuselection:`Applications --> Internet
+.. i18n: --> OpenERP Client` menu,
+.. i18n: or by opening a terminal window and typing \ ``openerp-client``\ . The OpenERP login dialog box
+.. i18n: should open and show the message :guilabel:`No database found you must create one!`.
+..
+
+Start the OpenERP GTK client by clicking its icon in the :menuselection:`Applications --> Internet
+--> OpenERP Client` menu,
+or by opening a terminal window and typing \ ``openerp-client``\ . The OpenERP login dialog box
+should open and show the message :guilabel:`No database found you must create one!`.
+
+.. i18n: Although this installation method is simple and therefore an attractive option, it is better to
+.. i18n: install OpenERP using a version downloaded from http://openerp.com. The downloaded revision is
+.. i18n: likely to be far more up to date than that available from a Linux distribution.
+..
+
+Although this installation method is simple and therefore an attractive option, it is better to
+install OpenERP using a version downloaded from http://openerp.com. The downloaded revision is
+likely to be far more up to date than that available from a Linux distribution.
+
+.. i18n: .. note:: Package Versions
+.. i18n:
+.. i18n: Maintaining packages is a process of development, testing and publication that takes time. The
+.. i18n: releases in OpenERP packages are therefore not always the latest available. Check
+.. i18n: the version number from the information on the website before installing a package. If only the
+.. i18n: third digit group differs (for example 6.0.1 instead of 6.0.2) then you may decide to install it because
+.. i18n: the differences may be minor – bug fixes rather than functionality changes between the package
+.. i18n: and the latest version.
+.. i18n:
+.. i18n:
+.. i18n: Manual Installation of the OpenERP Server
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+..
+
+.. note:: Package Versions
+
+ Maintaining packages is a process of development, testing and publication that takes time. The
+ releases in OpenERP packages are therefore not always the latest available. Check
+ the version number from the information on the website before installing a package. If only the
+ third digit group differs (for example 6.0.1 instead of 6.0.2) then you may decide to install it because
+ the differences may be minor – bug fixes rather than functionality changes between the package
+ and the latest version.
+
+
+Manual Installation of the OpenERP Server
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: In this section you will see how to install OpenERP by downloading it from the site
+.. i18n: http://openerp.com, and how to install the libraries and packages that OpenERP depends on, onto a
+.. i18n: desktop version of Ubuntu. Here is a summary of the procedure:
+..
+
+In this section you will see how to install OpenERP by downloading it from the site
+http://openerp.com, and how to install the libraries and packages that OpenERP depends on, onto a
+desktop version of Ubuntu. Here is a summary of the procedure:
+
+.. i18n: #. Navigate to the page http://openerp.com with your web browser,
+.. i18n:
+.. i18n: #. Click the :menuselection:`Download` button on the right side,
+.. i18n:
+.. i18n: #. Download the client and server files from the *Sources* section into your home directory
+.. i18n: (or some other location if you have defined a different download area).
+..
+
+#. Navigate to the page http://openerp.com with your web browser,
+
+#. Click the :menuselection:`Download` button on the right side,
+
+#. Download the client and server files from the *Sources* section into your home directory
+ (or some other location if you have defined a different download area).
+
+.. i18n: To download the PostgreSQL database and all of the other dependencies for OpenERP from packages:
+..
+
+To download the PostgreSQL database and all of the other dependencies for OpenERP from packages:
+
+.. i18n: #. Start Synaptic Package Manager, and enter the root password as required.
+.. i18n:
+.. i18n: #. Check that the repositories \ ``main`` \, \ ``universe`` \ and \ ``restricted`` \ are enabled.
+.. i18n:
+.. i18n: #. Search for a recent version of PostgreSQL (such as \ ``postgresql-8.4``\ then select it for
+.. i18n: installation along with its dependencies.
+.. i18n:
+.. i18n: #. Select all of OpenERP's dependencies, an up-to-date list of which should be
+.. i18n: found in the installation documents on OpenERP's website,
+.. i18n: then click :guilabel:`Apply` to install them.
+..
+
+#. Start Synaptic Package Manager, and enter the root password as required.
+
+#. Check that the repositories \ ``main`` \, \ ``universe`` \ and \ ``restricted`` \ are enabled.
+
+#. Search for a recent version of PostgreSQL (such as \ ``postgresql-8.4``\ then select it for
+ installation along with its dependencies.
+
+#. Select all of OpenERP's dependencies, an up-to-date list of which should be
+ found in the installation documents on OpenERP's website,
+ then click :guilabel:`Apply` to install them.
+
+.. i18n: .. index::
+.. i18n: single: Python
+..
+
+.. index::
+ single: Python
+
+.. i18n: .. note:: Python Programming Language
+.. i18n:
+.. i18n: Python is the programming language that has been used to develop OpenERP. It is a dynamic, non-typed
+.. i18n: language that is object-oriented, procedural and functional. It comes with numerous libraries that
+.. i18n: provide interfaces to other languages and has the great advantage that it can be learnt in only a
+.. i18n: few days. It is the language of choice for large parts of NASA's, Google's and many other
+.. i18n: enterprises' code.
+.. i18n:
+.. i18n: For more information on Python, explore http://www.python.org.
+..
+
+.. note:: Python Programming Language
+
+ Python is the programming language that has been used to develop OpenERP. It is a dynamic, non-typed
+ language that is object-oriented, procedural and functional. It comes with numerous libraries that
+ provide interfaces to other languages and has the great advantage that it can be learnt in only a
+ few days. It is the language of choice for large parts of NASA's, Google's and many other
+ enterprises' code.
+
+ For more information on Python, explore http://www.python.org.
+
+.. i18n: Once all these dependencies and the database are installed, install the server itself using the
+.. i18n: instructions on the website.
+..
+
+Once all these dependencies and the database are installed, install the server itself using the
+instructions on the website.
+
+.. i18n: Open a terminal window to start the server with the command :command:`openerp-server`, which
+.. i18n: should result in a series of log messages as the server starts up. If the server
+.. i18n: is correctly installed, the message :guilabel:`[...] waiting for connections...` should show within 30
+.. i18n: seconds or so, which indicates that the server is waiting for a client to connect to it.
+..
+
+Open a terminal window to start the server with the command :command:`openerp-server`, which
+should result in a series of log messages as the server starts up. If the server
+is correctly installed, the message :guilabel:`[...] waiting for connections...` should show within 30
+seconds or so, which indicates that the server is waiting for a client to connect to it.
+
+.. i18n: .. figure:: images/terps_startup_log.png
+.. i18n: :align: center
+.. i18n: :scale: 75
+.. i18n:
+.. i18n: *OpenERP startup log in the console*
+..
+
+.. figure:: images/terps_startup_log.png
+ :align: center
+ :scale: 75
+
+ *OpenERP startup log in the console*
+
+.. i18n: .. index::
+.. i18n: single: client; GTK
+.. i18n: single: installation; GTK client
+..
+
+.. index::
+ single: client; GTK
+ single: installation; GTK client
+
+.. i18n: Manual Installation of OpenERP GTK Clients
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+..
+
+Manual Installation of OpenERP GTK Clients
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: To install an OpenERP GTK client, follow the steps outlined in the website installation document for
+.. i18n: your particular operating system.
+..
+
+To install an OpenERP GTK client, follow the steps outlined in the website installation document for
+your particular operating system.
+
+.. i18n: .. figure:: images/terp_client_startup.png
+.. i18n: :align: center
+.. i18n: :scale: 75
+.. i18n:
+.. i18n: *OpenERP client at startup*
+..
+
+.. figure:: images/terp_client_startup.png
+ :align: center
+ :scale: 75
+
+ *OpenERP client at startup*
+
+.. i18n: Open a terminal window to start the client using the command :command:`openerp-client`. When you start the
+.. i18n: client on the same Linux PC as the server you will find that the default connection parameters will
+.. i18n: just work without needing any change. The message :guilabel:`No database found, you must create
+.. i18n: one!` shows you that the connection to the server has been successful and you need to create a
+.. i18n: database on the server.
+..
+
+Open a terminal window to start the client using the command :command:`openerp-client`. When you start the
+client on the same Linux PC as the server you will find that the default connection parameters will
+just work without needing any change. The message :guilabel:`No database found, you must create
+one!` shows you that the connection to the server has been successful and you need to create a
+database on the server.
+
+.. i18n: Creating the Database
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^
+..
+
+Creating the Database
+^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: You can connect other GTK clients over the network to your Linux server. Before you leave your
+.. i18n: server, make sure you know its network address – either by its name (such as \
+.. i18n: ``mycomputer.mycompany.net``\ ) or its IP address (such as \ ``192.168.0.123``\ ).
+..
+
+You can connect other GTK clients over the network to your Linux server. Before you leave your
+server, make sure you know its network address – either by its name (such as \
+``mycomputer.mycompany.net``\ ) or its IP address (such as \ ``192.168.0.123``\ ).
+
+.. i18n: .. index::
+.. i18n: single: port (network)
+..
+
+.. index::
+ single: port (network)
+
+.. i18n: .. note:: Different Networks
+.. i18n:
+.. i18n: Communications between an OpenERP client and server are based on standard protocols. You can
+.. i18n: connect Windows clients to a Linux server, or vice versa, without problems. It is the same for Mac
+.. i18n: versions of OpenERP – you can connect Windows and Linux clients and servers to them.
+..
+
+.. note:: Different Networks
+
+ Communications between an OpenERP client and server are based on standard protocols. You can
+ connect Windows clients to a Linux server, or vice versa, without problems. It is the same for Mac
+ versions of OpenERP – you can connect Windows and Linux clients and servers to them.
+
+.. i18n: To install an OpenERP client on a computer under Linux, repeat the procedure shown earlier in this
+.. i18n: section. You can connect different clients to the OpenERP server by modifying the connection
+.. i18n: parameters on each client. To do that, click the :guilabel:`Change` button in the connection dialog
+.. i18n: and set the following fields as needed:
+..
+
+To install an OpenERP client on a computer under Linux, repeat the procedure shown earlier in this
+section. You can connect different clients to the OpenERP server by modifying the connection
+parameters on each client. To do that, click the :guilabel:`Change` button in the connection dialog
+and set the following fields as needed:
+
+.. i18n: * :guilabel:`Server` : \ ``name``\ or \ ``IP address``\ of the server over the network,
+.. i18n:
+.. i18n: * :guilabel:`Port` : the port, whose default is \ ``8069``\ or \ ``8070``\ ,
+.. i18n:
+.. i18n: * :guilabel:`Connection protocol` : \ ``XML-RPC``\ or \ ``NET-RPC``\ .
+..
+
+* :guilabel:`Server` : \ ``name``\ or \ ``IP address``\ of the server over the network,
+
+* :guilabel:`Port` : the port, whose default is \ ``8069``\ or \ ``8070``\ ,
+
+* :guilabel:`Connection protocol` : \ ``XML-RPC``\ or \ ``NET-RPC``\ .
+
+.. i18n: .. figure:: images/terp_client_server.png
+.. i18n: :align: center
+.. i18n: :scale: 75
+.. i18n:
+.. i18n: *Dialog box for defining connection parameters to the server*
+..
+
+.. figure:: images/terp_client_server.png
+ :align: center
+ :scale: 75
+
+ *Dialog box for defining connection parameters to the server*
+
+.. i18n: It is possible to connect the server to the client using a secure protocol to prevent other network
+.. i18n: users from listening in, but the installation described here is for direct unencrypted connection.
+..
+
+It is possible to connect the server to the client using a secure protocol to prevent other network
+users from listening in, but the installation described here is for direct unencrypted connection.
+
+.. i18n: If your Linux server is protected by a firewall you will have to provide access to port
+.. i18n: \ ``8069`` \ or \ ``8070`` \ for users on other computers with OpenERP GTK clients.
+..
+
+If your Linux server is protected by a firewall you will have to provide access to port
+ \ ``8069`` \ or \ ``8070`` \ for users on other computers with OpenERP GTK clients.
+
+.. i18n: .. _fig-webwel:
+.. i18n:
+.. i18n: .. figure:: images/web_welcome.png
+.. i18n: :scale: 70
+.. i18n: :align: center
+.. i18n:
+.. i18n: *OpenERP web client at startup*
+..
+
+.. _fig-webwel:
+
+.. figure:: images/web_welcome.png
+ :scale: 70
+ :align: center
+
+ *OpenERP web client at startup*
+
+.. i18n: You can verify the installation by opening a web browser on the server and navigating to
+.. i18n: http://localhost:8069 to connect to the OpenERP web version as shown in the figure :ref:`fig-webwel`.
+.. i18n: You can also test this from
+.. i18n: another computer connected to the same network if you know the name or IP address of the server over
+.. i18n: the network – your browser should be set to http://<server_address>:8069 for this.
+..
+
+You can verify the installation by opening a web browser on the server and navigating to
+http://localhost:8069 to connect to the OpenERP web version as shown in the figure :ref:`fig-webwel`.
+You can also test this from
+another computer connected to the same network if you know the name or IP address of the server over
+the network – your browser should be set to http://<server_address>:8069 for this.
+
+.. i18n: Verifying your Linux Installation
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+..
+
+Verifying your Linux Installation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: .. index::
+.. i18n: single: pgAdmin III
+..
+
+.. index::
+ single: pgAdmin III
+
+.. i18n: You have used default parameters so far during the installation of the various components.
+.. i18n: If you have had problems, or you just want to set this up differently,
+.. i18n: the following points provide some indicators about how you can set up your installation.
+..
+
+You have used default parameters so far during the installation of the various components.
+If you have had problems, or you just want to set this up differently,
+the following points provide some indicators about how you can set up your installation.
+
+.. i18n: .. tip:: **psql** and **pgAdmin** tools
+.. i18n:
+.. i18n: psql is a simple client, executed from the command line, that is delivered with PostgreSQL. It
+.. i18n: enables you to execute SQL commands on your OpenERP database.
+.. i18n:
+.. i18n: If you prefer a graphical utility to manipulate your database directly you can install pgAdmin III
+.. i18n: (it is commonly installed automatically with PostgreSQL on a windowing system, but can also be
+.. i18n: found at \ ``http://www.pgadmin.org/`` \ ).
+..
+
+.. tip:: **psql** and **pgAdmin** tools
+
+ psql is a simple client, executed from the command line, that is delivered with PostgreSQL. It
+ enables you to execute SQL commands on your OpenERP database.
+
+ If you prefer a graphical utility to manipulate your database directly you can install pgAdmin III
+ (it is commonly installed automatically with PostgreSQL on a windowing system, but can also be
+ found at \ ``http://www.pgadmin.org/`` \ ).
+
+.. i18n: .. To check pts 4 and 7
+..
+
+.. To check pts 4 and 7
+
+.. i18n: #. The PostgreSQL database starts automatically and listens locally on port 5432 as standard: check
+.. i18n: this by entering \ ``sudo netstat -anpt``\ at a terminal to see if port 5432 is visible there.
+.. i18n:
+.. i18n: #. The database system has a default role of \ ``postgres``\ accessible by running under the Linux
+.. i18n: postgres user: check this by entering \ ``sudo su postgres -c psql``\ at a terminal to see the psql
+.. i18n: startup message – then type \ ``\q``\ to quit the program.
+.. i18n:
+.. i18n: #. If you try to start the OpenERP server from a terminal but get the message ``socket.error: (98,
+.. i18n: 'Address already in use')`` then you might be trying to start OpenERP while an instance of
+.. i18n: OpenERP is already running and using the sockets that you have defined (by default 8069 and 8070).
+.. i18n: If that is a surprise to you then you may be coming up against a previous installation of OpenERP
+.. i18n: or Tiny ERP, or something else using one or both of those ports.
+.. i18n:
+.. i18n: Type \ ``sudo netstat -anpt``\ to
+.. i18n: discover what is running there, and record the PID. You can check that the PID corresponds to a
+.. i18n: program you can dispense with by typing \ ``ps aux | grep <PID>``\ and you can then stop the
+.. i18n: program from running by typing \ ``sudo kill <PID>``\ . You need additional measures to stop it from
+.. i18n: restarting when you restart the server.
+.. i18n:
+.. i18n: #. The OpenERP server has a large number of configuration options. You can see what they are by
+.. i18n: starting the server with the argument \ ``–help``\ . By default the server configuration is stored
+.. i18n: in the file \ ``.terp_serverrc``\ in the user's home directory (and for the postgres user that
+.. i18n: directory is \ ``/var/lib/postgresql``\ .
+.. i18n:
+.. i18n: #. You can delete the configuration file to be quite sure that the OpenERP server is starting with
+.. i18n: just the default options. It is quite common for an upgraded system to behave badly because a new
+.. i18n: version server cannot work with options from a previous version. When the server starts without a
+.. i18n: configuration file it will write a new one once there is something non-default to write to it – it
+.. i18n: will operate using defaults until then.
+.. i18n:
+.. i18n: #. To verify that the system works, without becoming entangled in firewall problems, you can start
+.. i18n: the OpenERP client from a second terminal window on the server computer (which does not pass
+.. i18n: through the firewall). Connect using the XML-RPC protocol on port 8069 or NET-RPC on port 8070. The
+.. i18n: server can use both ports simultaneously. The window displays the log file when the client is
+.. i18n: started this way.
+.. i18n:
+.. i18n: #. The client setup is stored in the file \ ``.terprc``\ in the user's home directory.
+.. i18n: Since a GTK client can be started by any user, each user would have their setup defined in a
+.. i18n: configuration file in their own home directory.
+.. i18n:
+.. i18n: #. You can delete the configuration file to be quite sure that the OpenERP client is starting with
+.. i18n: just the default options. When the client starts without a configuration file it will write a new
+.. i18n: one for itself.
+.. i18n:
+.. i18n: #. The web server uses the NET-RPC protocol. If a GTK client works but the web server does not, then the
+.. i18n: problem is either with the NET-RPC port or with the web server itself, and not with the OpenERP server.
+..
+
+#. The PostgreSQL database starts automatically and listens locally on port 5432 as standard: check
+ this by entering \ ``sudo netstat -anpt``\ at a terminal to see if port 5432 is visible there.
+
+#. The database system has a default role of \ ``postgres``\ accessible by running under the Linux
+ postgres user: check this by entering \ ``sudo su postgres -c psql``\ at a terminal to see the psql
+ startup message – then type \ ``\q``\ to quit the program.
+
+#. If you try to start the OpenERP server from a terminal but get the message ``socket.error: (98,
+ 'Address already in use')`` then you might be trying to start OpenERP while an instance of
+ OpenERP is already running and using the sockets that you have defined (by default 8069 and 8070).
+ If that is a surprise to you then you may be coming up against a previous installation of OpenERP
+ or Tiny ERP, or something else using one or both of those ports.
+
+ Type \ ``sudo netstat -anpt``\ to
+ discover what is running there, and record the PID. You can check that the PID corresponds to a
+ program you can dispense with by typing \ ``ps aux | grep <PID>``\ and you can then stop the
+ program from running by typing \ ``sudo kill <PID>``\ . You need additional measures to stop it from
+ restarting when you restart the server.
+
+#. The OpenERP server has a large number of configuration options. You can see what they are by
+ starting the server with the argument \ ``–help``\ . By default the server configuration is stored
+ in the file \ ``.terp_serverrc``\ in the user's home directory (and for the postgres user that
+ directory is \ ``/var/lib/postgresql``\ .
+
+#. You can delete the configuration file to be quite sure that the OpenERP server is starting with
+ just the default options. It is quite common for an upgraded system to behave badly because a new
+ version server cannot work with options from a previous version. When the server starts without a
+ configuration file it will write a new one once there is something non-default to write to it – it
+ will operate using defaults until then.
+
+#. To verify that the system works, without becoming entangled in firewall problems, you can start
+ the OpenERP client from a second terminal window on the server computer (which does not pass
+ through the firewall). Connect using the XML-RPC protocol on port 8069 or NET-RPC on port 8070. The
+ server can use both ports simultaneously. The window displays the log file when the client is
+ started this way.
+
+#. The client setup is stored in the file \ ``.terprc``\ in the user's home directory.
+ Since a GTK client can be started by any user, each user would have their setup defined in a
+ configuration file in their own home directory.
+
+#. You can delete the configuration file to be quite sure that the OpenERP client is starting with
+ just the default options. When the client starts without a configuration file it will write a new
+ one for itself.
+
+#. The web server uses the NET-RPC protocol. If a GTK client works but the web server does not, then the
+ problem is either with the NET-RPC port or with the web server itself, and not with the OpenERP server.
+
+.. i18n: .. hint:: One Server for Several Companies
+.. i18n:
+.. i18n: You can start several OpenERP application servers on one physical computer server by using
+.. i18n: different ports. If you have defined multiple database roles in PostgreSQL, each connected through
+.. i18n: an OpenERP instance to a different port, you can simultaneously serve many companies from one
+.. i18n: physical server at one time.
+..
+
+.. hint:: One Server for Several Companies
+
+ You can start several OpenERP application servers on one physical computer server by using
+ different ports. If you have defined multiple database roles in PostgreSQL, each connected through
+ an OpenERP instance to a different port, you can simultaneously serve many companies from one
+ physical server at one time.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added directory 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images'
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/change_superadmin_pwd.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/change_superadmin_pwd.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/change_superadmin_pwd.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/create_new_db_GTK.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/create_new_db_GTK.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/create_new_db_GTK.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/define_main_co_dlg.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/define_main_co_dlg.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/define_main_co_dlg.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/new_login_dlg.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/new_login_dlg.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/new_login_dlg.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_arch_1.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_arch_1.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_arch_1.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_arch_1_en.dia'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_arch_1_en.dia 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_arch_1_en.dia 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_client_server.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_client_server.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_client_server.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_client_startup.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_client_startup.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_client_startup.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_server_conf.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_server_conf.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terp_server_conf.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terps_startup_log.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terps_startup_log.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/terps_startup_log.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images/web_welcome.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images/web_welcome.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images/web_welcome.png 2012-12-04 03:46:24 +0000 differ
=== added directory 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig'
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/ch1_outline.dia'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/ch1_outline.dia 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/ch1_outline.dia 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/ch1_outline.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/ch1_outline.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/ch1_outline.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/change_superadmin_pwd.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/change_superadmin_pwd.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/change_superadmin_pwd.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/cmd_prompt_ping.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/cmd_prompt_ping.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/cmd_prompt_ping.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/create_new_db_GTK.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/create_new_db_GTK.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/create_new_db_GTK.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/create_new_db_web.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/create_new_db_web.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/create_new_db_web.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/define_main_co_dlg.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/define_main_co_dlg.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/define_main_co_dlg.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/new_login_dlg.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/new_login_dlg.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/new_login_dlg.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/pgadmin_window.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/pgadmin_window.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/pgadmin_window.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_arch_1_en.dia'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_arch_1_en.dia 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_arch_1_en.dia 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_arch_1_en.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_arch_1_en.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_arch_1_en.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_client_server.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_client_server.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_client_server.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_client_startup.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_client_startup.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_client_startup.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_server_conf.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_server_conf.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terp_server_conf.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terps_startup_log.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terps_startup_log.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/terps_startup_log.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/web_welcome.png'
Binary files i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/web_welcome.png 1970-01-01 00:00:00 +0000 and i18n/zh_CN/source/book/1/1_1_Inst_Config/images_orig/web_welcome.png 2012-12-04 03:46:24 +0000 differ
=== added file 'i18n/zh_CN/source/book/1/1_1_Inst_Config/index.rst'
--- i18n/zh_CN/source/book/1/1_1_Inst_Config/index.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_1_Inst_Config/index.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,294 @@
+
+.. i18n: .. index::
+.. i18n: single: Installation
+.. i18n: single: Initial Setup
+.. i18n: pair: configuration; setup
+..
+
+.. index::
+ single: Installation
+ single: Initial Setup
+ pair: configuration; setup
+
+.. i18n: .. _ch-inst:
+.. i18n:
+.. i18n: ******************************
+.. i18n: Installation and Initial Setup
+.. i18n: ******************************
+..
+
+.. _ch-inst:
+
+******************************
+Installation and Initial Setup
+******************************
+
+.. i18n: *Installing OpenERP under Windows or Linux to get familiar with the software should take you only half an
+.. i18n: hour or so and needs only a couple of operations.*
+.. i18n:
+.. i18n: *The first operation is to install the application and database server on a server PC (that is
+.. i18n: a Windows or Linux or Macintosh computer).*
+..
+
+ *Installing OpenERP under Windows or Linux to get familiar with the software should take you only half an
+ hour or so and needs only a couple of operations.*
+
+ *The first operation is to install the application and database server on a server PC (that is
+ a Windows or Linux or Macintosh computer).*
+
+.. i18n: *You have a choice of approaches for the second operation:
+.. i18n: either use standard web
+.. i18n: clients that can be found on anybody's PC, or install application clients on each intended user's PC.*
+.. i18n:
+.. i18n: When you first install OpenERP, you will set up a database containing a little functionality and
+.. i18n: some demonstration data to test the installation.
+.. i18n:
+.. i18n: .. index::
+.. i18n: single: Tiny ERP
+..
+
+ *You have a choice of approaches for the second operation:
+ either use standard web
+ clients that can be found on anybody's PC, or install application clients on each intended user's PC.*
+
+When you first install OpenERP, you will set up a database containing a little functionality and
+some demonstration data to test the installation.
+
+.. index::
+ single: Tiny ERP
+
+.. i18n: .. note:: Renaming from Tiny ERP to OpenERP
+.. i18n:
+.. i18n: Tiny ERP was renamed to OpenERP early in 2008, so anyone who has used Tiny ERP should be
+.. i18n: equally at home with OpenERP. Both names refer to the same software, so there is no
+.. i18n: functional difference between versions 4.2.X of OpenERP and 4.2.X of Tiny ERP. This book
+.. i18n: applies to versions of OpenERP from 6.1.0 onwards, with references to earlier versions from
+.. i18n: time to time.
+..
+
+.. note:: Renaming from Tiny ERP to OpenERP
+
+ Tiny ERP was renamed to OpenERP early in 2008, so anyone who has used Tiny ERP should be
+ equally at home with OpenERP. Both names refer to the same software, so there is no
+ functional difference between versions 4.2.X of OpenERP and 4.2.X of Tiny ERP. This book
+ applies to versions of OpenERP from 6.1.0 onwards, with references to earlier versions from
+ time to time.
+
+.. i18n: .. index::
+.. i18n: single:SaaS
+..
+
+.. index::
+ single:SaaS
+
+.. i18n: .. note:: The SaaS, or “on-demand”, offer
+.. i18n:
+.. i18n: SaaS (Software as a Service) is delivered by a hosting supplier and paid in the form of a monthly
+.. i18n: subscription that
+.. i18n: includes hardware (servers), system maintenance, provision of hosting services, and support.
+.. i18n:
+.. i18n: You can get a month's free trial on OpenERP's http://www.openerp.com/online, which enables you to get
+.. i18n: started quickly
+.. i18n: without incurring costs for integration or for buying computer systems.
+.. i18n: Many of OpenERP's partner companies will access this, and some may offer their own similar service.
+.. i18n:
+.. i18n: This service should be particularly useful to small companies that just want to get going quickly
+.. i18n: and at low cost.
+.. i18n: It gives you immediate access to an integrated management system that has been built on the type
+.. i18n: of enterprise architecture
+.. i18n: used in banks and other large organizations.
+.. i18n: OpenERP is that system, and is described in detail throughout this book.
+..
+
+.. note:: The SaaS, or “on-demand”, offer
+
+ SaaS (Software as a Service) is delivered by a hosting supplier and paid in the form of a monthly
+ subscription that
+ includes hardware (servers), system maintenance, provision of hosting services, and support.
+
+ You can get a month's free trial on OpenERP's http://www.openerp.com/online, which enables you to get
+ started quickly
+ without incurring costs for integration or for buying computer systems.
+ Many of OpenERP's partner companies will access this, and some may offer their own similar service.
+
+ This service should be particularly useful to small companies that just want to get going quickly
+ and at low cost.
+ It gives you immediate access to an integrated management system that has been built on the type
+ of enterprise architecture
+ used in banks and other large organizations.
+ OpenERP is that system, and is described in detail throughout this book.
+
+.. i18n: Whether you want to test OpenERP or to put it into full production, you have at least three starting
+.. i18n: points:
+..
+
+Whether you want to test OpenERP or to put it into full production, you have at least three starting
+points:
+
+.. i18n: * no need to install OpenERP, you can test it through http://demo.openerp.com,
+.. i18n:
+.. i18n: * evaluate it on line at http://www.openerp.com and ask OpenERP for a SaaS trial hosted at
+.. i18n: http://ondemand.openerp.com, or the equivalent service at any of OpenERP's partner companies,
+.. i18n:
+.. i18n: * install it on your own computers to test it in your company's system environment.
+..
+
+* no need to install OpenERP, you can test it through http://demo.openerp.com,
+
+* evaluate it on line at http://www.openerp.com and ask OpenERP for a SaaS trial hosted at
+ http://ondemand.openerp.com, or the equivalent service at any of OpenERP's partner companies,
+
+* install it on your own computers to test it in your company's system environment.
+
+.. i18n: There are some differences between installing OpenERP on Windows and on Linux systems, but once
+.. i18n: installed, both systems offer the same functionality so you will not generally be able to tell which type
+.. i18n: of server you are using.
+..
+
+There are some differences between installing OpenERP on Windows and on Linux systems, but once
+installed, both systems offer the same functionality so you will not generally be able to tell which type
+of server you are using.
+
+.. i18n: .. note:: Linux, Windows, Mac
+.. i18n:
+.. i18n: Although this book deals only with installation on Windows and Linux systems, the same versions
+.. i18n: are also available for Macintosh on the official website of OpenERP.
+..
+
+.. note:: Linux, Windows, Mac
+
+ Although this book deals only with installation on Windows and Linux systems, the same versions
+ are also available for Macintosh on the official website of OpenERP.
+
+.. i18n: .. note:: Websites for OpenERP
+.. i18n:
+.. i18n: * Main Site: http://www.openerp.com,
+.. i18n:
+.. i18n: * SaaS or OpenERP OnLine Site: http://www.openerp.com/online,
+.. i18n:
+.. i18n: * Documentation Site: http://doc.openerp.com/,
+.. i18n:
+.. i18n: * Community discussion forum where you can often receive informed assistance:
+.. i18n: http://www.openobject.com/forum.
+..
+
+.. note:: Websites for OpenERP
+
+ * Main Site: http://www.openerp.com,
+
+ * SaaS or OpenERP OnLine Site: http://www.openerp.com/online,
+
+ * Documentation Site: http://doc.openerp.com/,
+
+ * Community discussion forum where you can often receive informed assistance:
+ http://www.openobject.com/forum.
+
+.. i18n: .. tip:: Current documentation
+.. i18n:
+.. i18n: The procedure for installing OpenERP will change and improve with
+.. i18n: each new version, so you should always check each release's documentation – both packaged with
+.. i18n: the release and on the website – for exact installation procedures.
+..
+
+.. tip:: Current documentation
+
+ The procedure for installing OpenERP will change and improve with
+ each new version, so you should always check each release's documentation – both packaged with
+ the release and on the website – for exact installation procedures.
+
+.. i18n: Once you have completed this installation, create and set up a database to confirm that your
+.. i18n: OpenERP installation is working. You can follow earlier chapters in this part of the book to achieve this.
+..
+
+Once you have completed this installation, create and set up a database to confirm that your
+OpenERP installation is working. You can follow earlier chapters in this part of the book to achieve this.
+
+.. i18n: .. raw:: html
+.. i18n:
+.. i18n: <div class="all-toctree">
+..
+
+.. raw:: html
+
+ <div class="all-toctree">
+
+.. i18n: .. toctree::
+.. i18n:
+.. i18n: 1_1_Inst_Config_architecture
+.. i18n: 1_1_Inst_Config_install
+.. i18n: 1_1_Inst_Config_db_create
+..
+
+.. toctree::
+
+ 1_1_Inst_Config_architecture
+ 1_1_Inst_Config_install
+ 1_1_Inst_Config_db_create
+
+.. i18n: .. raw:: html
+.. i18n:
+.. i18n: </div>
+..
+
+.. raw:: html
+
+ </div>
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added directory 'i18n/zh_CN/source/book/1/1_2_Guided_Tour'
=== added file 'i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.rst'
--- i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_connect_openerp.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,858 @@
+
+.. i18n: To Connect to OpenERP
+.. i18n: =====================
+..
+
+To Connect to OpenERP
+=====================
+
+.. i18n: Since this is the first time you have connected to OpenERP, you will be given the opportunity
+.. i18n: to configure the system. You may choose to either :guilabel:`Skip Configuration Wizards`
+.. i18n: or :guilabel:`Start Configuration`. We shall proceed with system configuration by clicking
+.. i18n: :guilabel:`Start Configuration`.
+..
+
+Since this is the first time you have connected to OpenERP, you will be given the opportunity
+to configure the system. You may choose to either :guilabel:`Skip Configuration Wizards`
+or :guilabel:`Start Configuration`. We shall proceed with system configuration by clicking
+:guilabel:`Start Configuration`.
+
+.. i18n: Configuration consists of a set of wizards that help you through options for the installed modules.
+.. i18n: Hardly anything is installed, so this is a very simple process at the moment.
+.. i18n:
+.. i18n: #. :guilabel:`Configure Your Interface` : select ``Simplified`` and click :guilabel:`Next`.
+..
+
+Configuration consists of a set of wizards that help you through options for the installed modules.
+Hardly anything is installed, so this is a very simple process at the moment.
+
+ #. :guilabel:`Configure Your Interface` : select ``Simplified`` and click :guilabel:`Next`.
+
+.. i18n: #. At the :guilabel:`Company Configuration` step, you should select your own :guilabel:`Company Name` and
+.. i18n: :guilabel:`Currency`. You may add your company address, contact and other details and a logo,
+.. i18n: if you have one, that appears on reports. Then, click :guilabel:`Next`.
+.. i18n:
+.. i18n: #. The :guilabel:`Install Applications` section would enable you to add applications to
+.. i18n: your system. For now, click :guilabel:`Skip` to proceed without installing any applications.
+.. i18n: You are now connected to OpenERP and can start using the system as an Administrator.
+..
+
+ #. At the :guilabel:`Company Configuration` step, you should select your own :guilabel:`Company Name` and
+ :guilabel:`Currency`. You may add your company address, contact and other details and a logo,
+ if you have one, that appears on reports. Then, click :guilabel:`Next`.
+
+ #. The :guilabel:`Install Applications` section would enable you to add applications to
+ your system. For now, click :guilabel:`Skip` to proceed without installing any applications.
+ You are now connected to OpenERP and can start using the system as an Administrator.
+
+.. i18n: .. index::
+.. i18n: single: administrator
+..
+
+.. index::
+ single: administrator
+
+.. i18n: Once you are displaying the main menu, you are able to see the following screen items,
+.. i18n: as shown in screenshot :ref:`fig-oech2-main`:
+..
+
+Once you are displaying the main menu, you are able to see the following screen items,
+as shown in screenshot :ref:`fig-oech2-main`:
+
+.. i18n: * the name of the database you are logged into and, just below it, the current user name,
+.. i18n:
+.. i18n: * the :guilabel:`ONLINE SUPPORT` button, which gives you an overview of the support services provided by OpenERP
+.. i18n: which is available for subscription,
+.. i18n:
+.. i18n: * the :guilabel:`Preferences` toolbar to the top right, showing the links to the :guilabel:`HOME` page,
+.. i18n: :guilabel:`EDIT PREFERENCES` page, :guilabel:`ABOUT`, :guilabel:`HELP`
+.. i18n: and :guilabel:`LOGOUT` button,
+.. i18n:
+.. i18n: * just below, you will find shortcuts (which the user can customize) and links to the menu items of installed applications,
+.. i18n:
+.. i18n: * a collection of interesting and useful widgets are available on the right of the home page beside the main menu.
+..
+
+* the name of the database you are logged into and, just below it, the current user name,
+
+* the :guilabel:`ONLINE SUPPORT` button, which gives you an overview of the support services provided by OpenERP
+ which is available for subscription,
+
+* the :guilabel:`Preferences` toolbar to the top right, showing the links to the :guilabel:`HOME` page,
+ :guilabel:`EDIT PREFERENCES` page, :guilabel:`ABOUT`, :guilabel:`HELP`
+ and :guilabel:`LOGOUT` button,
+
+* just below, you will find shortcuts (which the user can customize) and links to the menu items of installed applications,
+
+* a collection of interesting and useful widgets are available on the right of the home page beside the main menu.
+
+.. i18n: .. _fig-oech2-main:
+.. i18n:
+.. i18n: .. figure:: images/main_window_openerp_ch02.png
+.. i18n: :scale: 65
+.. i18n: :align: center
+.. i18n:
+.. i18n: *The Main Menu of the openerp_ch02 database*
+..
+
+.. _fig-oech2-main:
+
+.. figure:: images/main_window_openerp_ch02.png
+ :scale: 65
+ :align: center
+
+ *The Main Menu of the openerp_ch02 database*
+
+.. i18n: Two menus are available at the moment:
+..
+
+Two menus are available at the moment:
+
+.. i18n: * :menuselection:`Sales`
+.. i18n:
+.. i18n: * :menuselection:`Administration`
+..
+
+* :menuselection:`Sales`
+
+* :menuselection:`Administration`
+
+.. i18n: .. index::
+.. i18n: single: Preferences
+..
+
+.. index::
+ single: Preferences
+
+.. i18n: Preferences Toolbar
+.. i18n: -------------------
+..
+
+Preferences Toolbar
+-------------------
+
+.. i18n: When you are connected to OpenERP, the topmost toolbar indicates which user you are connected as.
+.. i18n: So it should currently be showing :guilabel:`Administrator` (unless you logged in as another
+.. i18n: user and it is reflecting the name of that user instead).
+..
+
+When you are connected to OpenERP, the topmost toolbar indicates which user you are connected as.
+So it should currently be showing :guilabel:`Administrator` (unless you logged in as another
+user and it is reflecting the name of that user instead).
+
+.. i18n: You will find the Preferences toolbar to its right containing a set of useful links.
+.. i18n: First, you will find a link to the :guilabel:`HOME` page. This takes you to either the
+.. i18n: Home page containing links to the available menus or to another window or dashboard, depending on the
+.. i18n: user configuration. In the case of the \ ``openerp_ch02`` \ database, so far the Home page
+.. i18n: is the Main Menu. But in general each user of the
+.. i18n: system is presented with a dashboard that is designed to show performance indicators and urgent
+.. i18n: documents that are most useful to someone of the user's position in the company. You will see how to
+.. i18n: assign dashboards to different users in a later chapter, :ref:`ch-config`.
+..
+
+You will find the Preferences toolbar to its right containing a set of useful links.
+First, you will find a link to the :guilabel:`HOME` page. This takes you to either the
+Home page containing links to the available menus or to another window or dashboard, depending on the
+user configuration. In the case of the \ ``openerp_ch02`` \ database, so far the Home page
+is the Main Menu. But in general each user of the
+system is presented with a dashboard that is designed to show performance indicators and urgent
+documents that are most useful to someone of the user's position in the company. You will see how to
+assign dashboards to different users in a later chapter, :ref:`ch-config`.
+
+.. i18n: .. index::
+.. i18n: single: timezone
+..
+
+.. index::
+ single: timezone
+
+.. i18n: .. tip:: Multi-nationals and Time Zones
+.. i18n:
+.. i18n: If you have users in different countries, they can configure their own timezone. Timestamp displays
+.. i18n: are then adjusted by reference to the user's own localization setting.
+.. i18n:
+.. i18n: So if you have a team in India and a team in England, the times will automatically be converted. If
+.. i18n: an Indian employee sets her working hours from 9 to 6, that will be converted and saved in the
+.. i18n: server's timezone. When the English users want to set up a meeting with an Indian user, the Indian
+.. i18n: user's available time will be converted to English time.
+..
+
+.. tip:: Multi-nationals and Time Zones
+
+ If you have users in different countries, they can configure their own timezone. Timestamp displays
+ are then adjusted by reference to the user's own localization setting.
+
+ So if you have a team in India and a team in England, the times will automatically be converted. If
+ an Indian employee sets her working hours from 9 to 6, that will be converted and saved in the
+ server's timezone. When the English users want to set up a meeting with an Indian user, the Indian
+ user's available time will be converted to English time.
+
+.. i18n: The next element in the toolbar is a link to :guilabel:`EDIT PREFERENCES`. By clicking that link, you
+.. i18n: get a dialog box where the current user can set his interface in the :guilabel:`Current Activity` tab;
+.. i18n: and in the :guilabel:`Preferences` tab, set his password, a timezone, a working language,
+.. i18n: e-mail and a signature:
+..
+
+The next element in the toolbar is a link to :guilabel:`EDIT PREFERENCES`. By clicking that link, you
+get a dialog box where the current user can set his interface in the :guilabel:`Current Activity` tab;
+and in the :guilabel:`Preferences` tab, set his password, a timezone, a working language,
+e-mail and a signature:
+
+.. i18n: * The :guilabel:`Interface` field in the :guilabel:`Current Activity` tab allows the user to switch
+.. i18n: between the \ ``Simplified`` \ and \ ``Extended`` \ interfaces.
+.. i18n:
+.. i18n: * The :guilabel:`Language` field enables the user's working language to be changed. But first, the
+.. i18n: system must be loaded with other languages for the user to be able to choose an alternative, which
+.. i18n: is described in the next subsection of this chapter. This is a mandatory field.
+.. i18n:
+.. i18n: * The :guilabel:`Timezone` setting indicates the user's location to OpenERP. This can be different
+.. i18n: from that of the server. All of the dates in the system are converted to the user's timezone
+.. i18n: automatically.
+.. i18n:
+.. i18n: * The :guilabel:`Menu Tips` checkbox gives the user the choice to have tips displayed on each menu action.
+.. i18n:
+.. i18n: * The :guilabel:`Change Password` button gives users the opportunity to change their own password.
+.. i18n: It opens a new dialog box where users may change the password and must logout and login again after the change.
+.. i18n: You should take steps (perhaps written policies) to prevent users making these too trivial.
+.. i18n:
+.. i18n: * The :guilabel:`Email` field is for storing the current user's default e-mail address.
+.. i18n:
+.. i18n: * The :guilabel:`Signature` field gives the user a place for the signature attached to messages sent
+.. i18n: from within OpenERP.
+..
+
+* The :guilabel:`Interface` field in the :guilabel:`Current Activity` tab allows the user to switch
+ between the \ ``Simplified`` \ and \ ``Extended`` \ interfaces.
+
+* The :guilabel:`Language` field enables the user's working language to be changed. But first, the
+ system must be loaded with other languages for the user to be able to choose an alternative, which
+ is described in the next subsection of this chapter. This is a mandatory field.
+
+* The :guilabel:`Timezone` setting indicates the user's location to OpenERP. This can be different
+ from that of the server. All of the dates in the system are converted to the user's timezone
+ automatically.
+
+* The :guilabel:`Menu Tips` checkbox gives the user the choice to have tips displayed on each menu action.
+
+* The :guilabel:`Change Password` button gives users the opportunity to change their own password.
+ It opens a new dialog box where users may change the password and must logout and login again after the change.
+ You should take steps (perhaps written policies) to prevent users making these too trivial.
+
+* The :guilabel:`Email` field is for storing the current user's default e-mail address.
+
+* The :guilabel:`Signature` field gives the user a place for the signature attached to messages sent
+ from within OpenERP.
+
+.. i18n: The :guilabel:`ABOUT` link gives information about the development of the OpenERP software and
+.. i18n: various links to other information.
+..
+
+The :guilabel:`ABOUT` link gives information about the development of the OpenERP software and
+various links to other information.
+
+.. i18n: The :guilabel:`HELP` link directs the user to the online documentation of OpenERP, where extensive help is available on a host of topics.
+..
+
+The :guilabel:`HELP` link directs the user to the online documentation of OpenERP, where extensive help is available on a host of topics.
+
+.. i18n: The :guilabel:`LOGOUT` link enables you to logout and return to the original login page. You can
+.. i18n: then login to another database, or to the same database as another user. This page also gives you
+.. i18n: access to the super-administrator functions for managing databases on this server.
+..
+
+The :guilabel:`LOGOUT` link enables you to logout and return to the original login page. You can
+then login to another database, or to the same database as another user. This page also gives you
+access to the super-administrator functions for managing databases on this server.
+
+.. i18n: .. index::
+.. i18n: single: installation; language
+..
+
+.. index::
+ single: installation; language
+
+.. i18n: Installing a New Language
+.. i18n: ^^^^^^^^^^^^^^^^^^^^^^^^^
+..
+
+Installing a New Language
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. i18n: Each user of the system can work in his or her own language. More than twenty languages are
+.. i18n: currently available besides English. Users select their working language using the Preferences link.
+.. i18n: You can also assign a language to a partner (customer or supplier), in which case all the documents
+.. i18n: sent to that partner will be automatically translated into that language.
+..
+
+Each user of the system can work in his or her own language. More than twenty languages are
+currently available besides English. Users select their working language using the Preferences link.
+You can also assign a language to a partner (customer or supplier), in which case all the documents
+sent to that partner will be automatically translated into that language.
+
+.. i18n: .. attention:: More about Languages
+.. i18n:
+.. i18n: The base version of OpenERP is translated into the following languages: English, German, Chinese,
+.. i18n: Spanish, Italian, Hungarian, Dutch, Portuguese, Romanian, Swedish and Czech.
+.. i18n:
+.. i18n: But other languages are also available: Arabic, Afghan,
+.. i18n: Austrian, Bulgarian, Indonesian, Finnish, Thai, Turkish and Vietnamese..
+..
+
+.. attention:: More about Languages
+
+ The base version of OpenERP is translated into the following languages: English, German, Chinese,
+ Spanish, Italian, Hungarian, Dutch, Portuguese, Romanian, Swedish and Czech.
+
+ But other languages are also available: Arabic, Afghan,
+ Austrian, Bulgarian, Indonesian, Finnish, Thai, Turkish and Vietnamese..
+
+.. i18n: As administrator, you can install a new main working language into the system.
+..
+
+As administrator, you can install a new main working language into the system.
+
+.. i18n: #. Select :menuselection:`Administration` in the Menu Toolbar and click
+.. i18n: :menuselection:`Translations --> Load an Official Translation` in the main menu window,
+.. i18n:
+.. i18n: #. Select the language to install, \ ``French``\ for example, and click :guilabel:`Load`,
+.. i18n:
+.. i18n: #. The system will intimate you when the selected language has been successfully installed.
+.. i18n: Click :guilabel:`Close` to return to the menu.
+..
+
+ #. Select :menuselection:`Administration` in the Menu Toolbar and click
+ :menuselection:`Translations --> Load an Official Translation` in the main menu window,
+
+ #. Select the language to install, \ ``French``\ for example, and click :guilabel:`Load`,
+
+ #. The system will intimate you when the selected language has been successfully installed.
+ Click :guilabel:`Close` to return to the menu.
+
+.. i18n: To see the effects of this installation, change the preferences of your user to change the working
+.. i18n: language (you may first need to ensure that you have explicitly selected English as your language,
+.. i18n: rather than keep the default, before you are given the French option).
+.. i18n: You may have to reload the page to see the effects. The main menu is immediately translated in
+.. i18n: the selected language. If you are using the GTK
+.. i18n: client, you will first have to close the menu then open a new main menu to start seeing things in the
+.. i18n: new language.
+..
+
+To see the effects of this installation, change the preferences of your user to change the working
+language (you may first need to ensure that you have explicitly selected English as your language,
+rather than keep the default, before you are given the French option).
+You may have to reload the page to see the effects. The main menu is immediately translated in
+the selected language. If you are using the GTK
+client, you will first have to close the menu then open a new main menu to start seeing things in the
+new language.
+
+.. i18n: .. note:: Navigating the Menu
+.. i18n:
+.. i18n: From this point in the book navigation from the main menu is written as a series of menu entries
+.. i18n: connected by the :menuselection:`-->` character. Instead of seeing “Select Administration in
+.. i18n: the Menu toolbar then click Translations > Load an Official Translation” you will just get “use menu
+.. i18n: :menuselection:`Administration --> Translations --> Load an Official Translation`”.
+..
+
+.. note:: Navigating the Menu
+
+ From this point in the book navigation from the main menu is written as a series of menu entries
+ connected by the :menuselection:`-->` character. Instead of seeing “Select Administration in
+ the Menu toolbar then click Translations > Load an Official Translation” you will just get “use menu
+ :menuselection:`Administration --> Translations --> Load an Official Translation`”.
+
+.. i18n: .. index:: requests
+..
+
+.. index:: requests
+
+.. i18n: Requests
+.. i18n: ^^^^^^^^
+..
+
+Requests
+^^^^^^^^
+
+.. i18n: Requests have been removed in OpenERP 6.1 - a new internal communication system will be added in 7.0.
+..
+
+Requests have been removed in OpenERP 6.1 - a new internal communication system will be added in 7.0.
+
+.. i18n: .. index::
+.. i18n: single: user; configuration
+..
+
+.. index::
+ single: user; configuration
+
+.. i18n: Configuring Users
+.. i18n: -----------------
+..
+
+Configuring Users
+-----------------
+
+.. i18n: The database you created contains minimal functionality but can be extended to include all of the
+.. i18n: potential functionality available to OpenERP. About the only functions actually available in this
+.. i18n: minimal database are Customers and Currencies – and these only because the definition of your main
+.. i18n: company required this. And because you chose to include demonstration data, both Customers and
+.. i18n: Currencies were installed with some samples.
+..
+
+The database you created contains minimal functionality but can be extended to include all of the
+potential functionality available to OpenERP. About the only functions actually available in this
+minimal database are Customers and Currencies – and these only because the definition of your main
+company required this. And because you chose to include demonstration data, both Customers and
+Currencies were installed with some samples.
+
+.. i18n: .. index::
+.. i18n: single: administrator
+..
+
+.. index::
+ single: administrator
+
+.. i18n: Because you logged in as Administrator, you have all the access you need to configure users. Click
+.. i18n: :menuselection:`Administration --> Users --> Users` to display the list of users defined in the
+.. i18n: system. A second user, \ ``Demo User`` \, is also present in the system as part of the
+.. i18n: demonstration data. Click the \ ``Demo User`` \ name to open a non-editable form on that user.
+..
+
+Because you logged in as Administrator, you have all the access you need to configure users. Click
+:menuselection:`Administration --> Users --> Users` to display the list of users defined in the
+system. A second user, \ ``Demo User`` \, is also present in the system as part of the
+demonstration data. Click the \ ``Demo User`` \ name to open a non-editable form on that user.
+
+.. i18n: Click the :guilabel:`Groups` tab to see that the demo user is a member of only the ``Employee`` group,
+.. i18n: and is subject to no specialized rules.
+.. i18n: The user \ ``Administrator`` \ is different, as you can see if you
+.. i18n: follow the same sequence to review its definition. It is a member of the \ ``Administration / Configuration`` \
+.. i18n: and the \ ``Administration / Access Rights`` \ groups,
+.. i18n: which gives it more advanced rights to configure new users.
+..
+
+Click the :guilabel:`Groups` tab to see that the demo user is a member of only the ``Employee`` group,
+and is subject to no specialized rules.
+The user \ ``Administrator`` \ is different, as you can see if you
+follow the same sequence to review its definition. It is a member of the \ ``Administration / Configuration`` \
+and the \ ``Administration / Access Rights`` \ groups,
+which gives it more advanced rights to configure new users.
+
+.. i18n: .. index::
+.. i18n: single: user; access
+.. i18n: single: user; role
+.. i18n: single: user; group
+..
+
+.. index::
+ single: user; access
+ single: user; role
+ single: user; group
+
+.. i18n: .. tip:: Groups and Users
+.. i18n:
+.. i18n: Users and groups provide the structure for specifying access rights to different documents. Their
+.. i18n: setup answers the question “Who has access to what?”
+..
+
+.. tip:: Groups and Users
+
+ Users and groups provide the structure for specifying access rights to different documents. Their
+ setup answers the question “Who has access to what?”
+
+.. i18n: Click :menuselection:`Administration --> Users --> Groups` to open the list of
+.. i18n: groups defined in the system. If you open the form view of the \ ``Administration / Configuration`` \
+.. i18n: group by clicking its name in the list, the first tab :guilabel:`Users` gives you the list of
+.. i18n: all the users who belong to this group.
+..
+
+Click :menuselection:`Administration --> Users --> Groups` to open the list of
+groups defined in the system. If you open the form view of the \ ``Administration / Configuration`` \
+group by clicking its name in the list, the first tab :guilabel:`Users` gives you the list of
+all the users who belong to this group.
+
+.. i18n: You can also see in the :guilabel:`Menus` tab, the list of menus reserved for this group. By convention,
+.. i18n: the \ ``Administration / Configuration`` \ in OpenERP has rights of access to
+.. i18n: the :menuselection:`Configuration` menu in each section. So \ ``Sales / Configuration`` \ is
+.. i18n: found in the list of access rights but \ ``Sales`` \ is not found there because it is accessible
+.. i18n: to all users. Click the :guilabel:`Access Rights` tab and it gives you details of the access rights
+.. i18n: for that group. These are detailed later in :ref:`ch-config`.
+..
+
+You can also see in the :guilabel:`Menus` tab, the list of menus reserved for this group. By convention,
+the \ ``Administration / Configuration`` \ in OpenERP has rights of access to
+the :menuselection:`Configuration` menu in each section. So \ ``Sales / Configuration`` \ is
+found in the list of access rights but \ ``Sales`` \ is not found there because it is accessible
+to all users. Click the :guilabel:`Access Rights` tab and it gives you details of the access rights
+for that group. These are detailed later in :ref:`ch-config`.
+
+.. i18n: You can create some new users to integrate them into the system. Assign them to predefined groups to
+.. i18n: grant them certain access rights. Then try their access rights when you login as these users.
+.. i18n: Management defines these access rights as described in :ref:`ch-config`.
+..
+
+You can create some new users to integrate them into the system. Assign them to predefined groups to
+grant them certain access rights. Then try their access rights when you login as these users.
+Management defines these access rights as described in :ref:`ch-config`.
+
+.. i18n: .. note:: Changes to Default Access Rights
+.. i18n:
+.. i18n: New versions of OpenERP differ from earlier versions of OpenERP and Tiny ERP in this area:
+.. i18n: many groups have been predefined and access to many of the menus and objects are keyed to these
+.. i18n: groups by default.
+.. i18n: This is quite a contrast to the rather liberal approach in 4.2.2 and before, where access rights
+.. i18n: could be defined but were not activated by default.
+..
+
+.. note:: Changes to Default Access Rights
+
+ New versions of OpenERP differ from earlier versions of OpenERP and Tiny ERP in this area:
+ many groups have been predefined and access to many of the menus and objects are keyed to these
+ groups by default.
+ This is quite a contrast to the rather liberal approach in 4.2.2 and before, where access rights
+ could be defined but were not activated by default.
+
+.. i18n: .. index::
+.. i18n: single: partner; managing
+..
+
+.. index::
+ single: partner; managing
+
+.. i18n: Managing Partners
+.. i18n: -----------------
+..
+
+Managing Partners
+-----------------
+
+.. i18n: In OpenERP, a partner represents an entity that you do business with. That can be a prospect, a
+.. i18n: customer, a supplier, or even an employee of your company.
+..
+
+In OpenERP, a partner represents an entity that you do business with. That can be a prospect, a
+customer, a supplier, or even an employee of your company.
+
+.. i18n: List of Partners
+.. i18n: ^^^^^^^^^^^^^^^^
+..
+
+List of Partners
+^^^^^^^^^^^^^^^^
+
+.. i18n: Click :menuselection:`Sales --> Address Book --> Customers` in the main menu to open the list of partners who are customers. Then click the name of the first partner to get hold of the details – a form appears with
+.. i18n: information about the company, such as its corporate name, its primary language, its reference and whether it is a
+.. i18n: \ ``Customer`` \ and/or a \ ``Supplier`` \. You will also find several other tabs on it:
+..
+
+Click :menuselection:`Sales --> Address Book --> Customers` in the main menu to open the list of partners who are customers. Then click the name of the first partner to get hold of the details – a form appears with
+information about the company, such as its corporate name, its primary language, its reference and whether it is a
+\ ``Customer`` \ and/or a \ ``Supplier`` \. You will also find several other tabs on it:
+
+.. i18n: * the :guilabel:`General` tab contains information about different contacts at that partner, postal information,
+.. i18n: communication information and the categories it belongs to.
+.. i18n:
+.. i18n: * the :guilabel:`Sales & Purchases` tab contains information that is slightly less immediate.
+.. i18n:
+.. i18n: * the :menuselection:`History` tab (visible if you install other modules like :mod:`crm`)
+.. i18n: contains the history of all the events that the partner has
+.. i18n: been involved in. These events are created automatically by different system documents: invoices,
+.. i18n: orders, support requests and so on, from a list that can be configured in the system.
+.. i18n: These give you a rapid view of the partner's history on a single
+.. i18n: screen.
+.. i18n:
+.. i18n: * the :menuselection:`Notes` tab is an area for free text notes.
+..
+
+* the :guilabel:`General` tab contains information about different contacts at that partner, postal information,
+ communication information and the categories it belongs to.
+
+* the :guilabel:`Sales & Purchases` tab contains information that is slightly less immediate.
+
+* the :menuselection:`History` tab (visible if you install other modules like :mod:`crm`)
+ contains the history of all the events that the partner has
+ been involved in. These events are created automatically by different system documents: invoices,
+ orders, support requests and so on, from a list that can be configured in the system.
+ These give you a rapid view of the partner's history on a single
+ screen.
+
+* the :menuselection:`Notes` tab is an area for free text notes.
+
+.. i18n: To the right of the form is a list of Reports, Actions, Links and Attachments related to a partner. Click some of
+.. i18n: them to get a feel for their use.
+..
+
+To the right of the form is a list of Reports, Actions, Links and Attachments related to a partner. Click some of
+them to get a feel for their use.
+
+.. i18n: .. figure:: images/partner.png
+.. i18n: :align: center
+.. i18n: :scale: 80
+.. i18n:
+.. i18n: *Partner form*
+..
+
+.. figure:: images/partner.png
+ :align: center
+ :scale: 80
+
+ *Partner form*
+
+.. i18n: .. index::
+.. i18n: single: partner; category
+..
+
+.. index::
+ single: partner; category
+
+.. i18n: .. tip:: Partner Categories
+.. i18n:
+.. i18n: Partner Categories enable you to segment different partners according to their relation with you
+.. i18n: (client, prospect, supplier, and so on). A partner can belong to several categories – for example
+.. i18n: it may be both a customer and supplier at the same time.
+.. i18n:
+.. i18n: But there are also Customer and Supplier checkboxes on the partner form, which are different.
+.. i18n: These checkboxes are designed to enable OpenERP to quickly select what should appear on some of the
+.. i18n: system drop-down selection boxes. They, too, need to be set correctly.
+..
+
+.. tip:: Partner Categories
+
+ Partner Categories enable you to segment different partners according to their relation with you
+ (client, prospect, supplier, and so on). A partner can belong to several categories – for example
+ it may be both a customer and supplier at the same time.
+
+ But there are also Customer and Supplier checkboxes on the partner form, which are different.
+ These checkboxes are designed to enable OpenERP to quickly select what should appear on some of the
+ system drop-down selection boxes. They, too, need to be set correctly.
+
+.. i18n: Partner Categories
+.. i18n: ^^^^^^^^^^^^^^^^^^
+..
+
+Partner Categories
+^^^^^^^^^^^^^^^^^^
+
+.. i18n: You can list your partners by category using the menu :menuselection:`Sales --> Configuration -->
+.. i18n: Address Book --> Partners Categories`. Click a category to obtain a list of partners in that category.
+..
+
+You can list your partners by category using the menu :menuselection:`Sales --> Configuration -->
+Address Book --> Partners Categories`. Click a category to obtain a list of partners in that category.
+
+.. i18n: .. figure:: images/main_window_partner_menu_config.png
+.. i18n: :scale: 75
+.. i18n: :align: center
+.. i18n:
+.. i18n: *Categories of partner*
+..
+
+.. figure:: images/main_window_partner_menu_config.png
+ :scale: 75
+ :align: center
+
+ *Categories of partner*
+
+.. i18n: The administrator can define new categories. So you will create a new category and link it to a
+.. i18n: partner:
+..
+
+The administrator can define new categories. So you will create a new category and link it to a
+partner:
+
+.. i18n: #. Use :menuselection:`Sales --> Configuration --> Address Book --> Partners Categories`
+.. i18n: to reach the list of categories in a list view.
+.. i18n:
+.. i18n: #. Click :guilabel:`New` to open an empty form for creating a new category
+.. i18n:
+.. i18n: #. Enter \ ``My Prospects``\ in the field :guilabel:`Category Name`. Then click on the
+.. i18n: :guilabel:`Search` icon to the right of the :guilabel:`Parent Category` field and select
+.. i18n: \ ``Prospect``\ in the list that appears.
+.. i18n:
+.. i18n: #. Then save your new category using the :guilabel:`Save` button.
+..
+
+ #. Use :menuselection:`Sales --> Configuration --> Address Book --> Partners Categories`
+ to reach the list of categories in a list view.
+
+ #. Click :guilabel:`New` to open an empty form for creating a new category
+
+ #. Enter \ ``My Prospects``\ in the field :guilabel:`Category Name`. Then click on the
+ :guilabel:`Search` icon to the right of the :guilabel:`Parent Category` field and select
+ \ ``Prospect``\ in the list that appears.
+
+ #. Then save your new category using the :guilabel:`Save` button.
+
+.. i18n: You may add exiting partners to this new category using the :guilabel:`Add` button in the
+.. i18n: :guilabel:`Partners` section.
+..
+
+You may add exiting partners to this new category using the :guilabel:`Add` button in the
+:guilabel:`Partners` section.
+
+.. i18n: .. tip:: Required Fields
+.. i18n:
+.. i18n: Fields colored blue are required. If you try to save the form while any of these fields are empty,
+.. i18n: the field turns red to indicate that there is a problem. It is impossible to save the form until
+.. i18n: you have completed every required field.
+..
+
+.. tip:: Required Fields
+
+ Fields colored blue are required. If you try to save the form while any of these fields are empty,
+ the field turns red to indicate that there is a problem. It is impossible to save the form until
+ you have completed every required field.
+
+.. i18n: You can review your new category structure using the list view.
+.. i18n: You should see the new structure of \ ``Prospects / My Prospects``\ there.
+..
+
+You can review your new category structure using the list view.
+You should see the new structure of \ ``Prospects / My Prospects``\ there.
+
+.. i18n: .. figure:: images/main_window_partner_tab.png
+.. i18n: :scale: 75
+.. i18n: :align: center
+.. i18n:
+.. i18n: *Creating a new partner category*
+..
+
+.. figure:: images/main_window_partner_tab.png
+ :scale: 75
+ :align: center
+
+ *Creating a new partner category*
+
+.. i18n: To create a new partner and link it to this new category, open a new partner form to modify it.
+..
+
+To create a new partner and link it to this new category, open a new partner form to modify it.
+
+.. i18n: #. Type \ ``New Partner``\ into the :guilabel:`Name` field.
+.. i18n:
+.. i18n: #. In the :guilabel:`General` tab, click the :guilabel:`Add` button under the
+.. i18n: :guilabel:`Categories` section and select your
+.. i18n: new category from the list that appears: \ ``Prospect / My Prospects`` \.
+.. i18n:
+.. i18n: #. Then save your partner by clicking :guilabel:`Save`. The partner now belongs in the category
+.. i18n: \ ``Prospect / My Prospects`` \.
+.. i18n:
+.. i18n: #. Monitor your modification in the menu :menuselection:`Sales --> Configuration --> Address Book -->
+.. i18n: Partners Categories`. Select the category :guilabel:`Prospect / My Prospects`. The list of partners opens
+.. i18n: and you will find your new partner there in that list.
+..
+
+ #. Type \ ``New Partner``\ into the :guilabel:`Name` field.
+
+ #. In the :guilabel:`General` tab, click the :guilabel:`Add` button under the
+ :guilabel:`Categories` section and select your
+ new category from the list that appears: \ ``Prospect / My Prospects`` \.
+
+ #. Then save your partner by clicking :guilabel:`Save`. The partner now belongs in the category
+ \ ``Prospect / My Prospects`` \.
+
+ #. Monitor your modification in the menu :menuselection:`Sales --> Configuration --> Address Book -->
+ Partners Categories`. Select the category :guilabel:`Prospect / My Prospects`. The list of partners opens
+ and you will find your new partner there in that list.
+
+.. i18n: .. tip:: Searching for Documents
+.. i18n:
+.. i18n: If you need to search through a long list of partners, it is best to use the available search
+.. i18n: criteria rather than scroll through the whole partner list. It is a habit that will save you a lot of
+.. i18n: time in the long run as you search for all kinds of documents.
+..
+
+.. tip:: Searching for Documents
+
+ If you need to search through a long list of partners, it is best to use the available search
+ criteria rather than scroll through the whole partner list. It is a habit that will save you a lot of
+ time in the long run as you search for all kinds of documents.
+
+.. i18n: .. note:: Example Categories of Partners
+.. i18n:
+.. i18n: A partner can be assigned to several categories. These enable you to create alternative
+.. i18n: classifications as necessary, usually in a hierarchical form.
+.. i18n:
+.. i18n: Here are some structures that are often used:
+.. i18n:
+.. i18n: * geographical locations,
+.. i18n:
+.. i18n: * interest in certain product lines,
+.. i18n:
+.. i18n: * subscriptions to newsletters,
+.. i18n:
+.. i18n: * type of industry.
+..
+
+.. note:: Example Categories of Partners
+
+ A partner can be assigned to several categories. These enable you to create alternative
+ classifications as necessary, usually in a hierarchical form.
+
+ Here are some structures that are often used:
+
+ * geographical locations,
+
+ * interest in certain product lines,
+
+ * subscriptions to newsletters,
+
+ * type of industry.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added file 'i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_db_create.rst'
--- i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_db_create.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_db_create.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,111 @@
+
+.. i18n: Database Creation
+.. i18n: =================
+..
+
+Database Creation
+=================
+
+.. i18n: Use the technique outlined in :ref:`ch-inst` to create a new database, \ ``openerp_ch02``\ . This
+.. i18n: database will contain the demonstration data provided with OpenERP and a large proportion of the
+.. i18n: core OpenERP functionality. You will need to know your super administrator password for this – or
+.. i18n: you will have to find somebody who does have it to create this seed database.
+..
+
+Use the technique outlined in :ref:`ch-inst` to create a new database, \ ``openerp_ch02``\ . This
+database will contain the demonstration data provided with OpenERP and a large proportion of the
+core OpenERP functionality. You will need to know your super administrator password for this – or
+you will have to find somebody who does have it to create this seed database.
+
+.. i18n: Start the database creation process from the :guilabel:`Login` page by clicking
+.. i18n: :guilabel:`Databases` and then completing the following fields on the :guilabel:`Create Database` form:
+..
+
+Start the database creation process from the :guilabel:`Login` page by clicking
+:guilabel:`Databases` and then completing the following fields on the :guilabel:`Create Database` form:
+
+.. i18n: * :guilabel:`Super admin password` : by default it is \ ``admin``\ , if you or your system
+.. i18n: administrator have not changed it,
+.. i18n:
+.. i18n: * :guilabel:`New database name` : \ ``openerp_ch02``\ ,
+.. i18n:
+.. i18n: * :guilabel:`Load Demonstration data` checkbox: \ ``checked``\ ,
+.. i18n:
+.. i18n: * :guilabel:`Default Language` : \ ``English (US)``\ ,
+.. i18n:
+.. i18n: * :guilabel:`Administrator password` : \ ``admin``\ (because it is easiest to remember at this stage, but obviously completely insecure),
+.. i18n:
+.. i18n: * :guilabel:`Confirm password` : \ ``admin``\ .
+..
+
+* :guilabel:`Super admin password` : by default it is \ ``admin``\ , if you or your system
+ administrator have not changed it,
+
+* :guilabel:`New database name` : \ ``openerp_ch02``\ ,
+
+* :guilabel:`Load Demonstration data` checkbox: \ ``checked``\ ,
+
+* :guilabel:`Default Language` : \ ``English (US)``\ ,
+
+* :guilabel:`Administrator password` : \ ``admin``\ (because it is easiest to remember at this stage, but obviously completely insecure),
+
+* :guilabel:`Confirm password` : \ ``admin``\ .
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added file 'i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_install_functionality.rst'
--- i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_install_functionality.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_install_functionality.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,490 @@
+
+.. i18n: .. index::
+.. i18n: single: module; new functionality
+..
+
+.. index::
+ single: module; new functionality
+
+.. i18n: Installing New Functionality
+.. i18n: ============================
+..
+
+Installing New Functionality
+============================
+
+.. i18n: All of OpenERP's functionality is contained in its many and various modules. Many of these, the
+.. i18n: core modules, are automatically loaded during the initial installation of the system and can be
+.. i18n: updated online later. Although they are mostly not installed in your database at the outset, they are
+.. i18n: available on your computer for immediate installation. Additional modules can also be loaded online
+.. i18n: from the official OpenERP site http://openerp.com. These modules are inactive when they are loaded
+.. i18n: into the system, and can then be installed in a separate step.
+..
+
+All of OpenERP's functionality is contained in its many and various modules. Many of these, the
+core modules, are automatically loaded during the initial installation of the system and can be
+updated online later. Although they are mostly not installed in your database at the outset, they are
+available on your computer for immediate installation. Additional modules can also be loaded online
+from the official OpenERP site http://openerp.com. These modules are inactive when they are loaded
+into the system, and can then be installed in a separate step.
+
+.. i18n: You will start by checking if there are any updates available online that apply to your initial
+.. i18n: installation. Then you will install a CRM module to complete your existing database.
+..
+
+You will start by checking if there are any updates available online that apply to your initial
+installation. Then you will install a CRM module to complete your existing database.
+
+.. i18n: .. index::
+.. i18n: single: module; upgrading
+..
+
+.. index::
+ single: module; upgrading
+
+.. i18n: Updating the Modules list
+.. i18n: -------------------------
+..
+
+Updating the Modules list
+-------------------------
+
+.. i18n: Click :menuselection:`Administration --> Modules --> Update Modules List` to start the
+.. i18n: updating tool. The :guilabel:`Module Update` window opens notifying the user that
+.. i18n: OpenERP will look at the server side for adding new modules and updating
+.. i18n: existing ones.
+..
+
+Click :menuselection:`Administration --> Modules --> Update Modules List` to start the
+updating tool. The :guilabel:`Module Update` window opens notifying the user that
+OpenERP will look at the server side for adding new modules and updating
+existing ones.
+
+.. i18n: Click :guilabel:`Update` to start the update on the server side. When it is
+.. i18n: complete, you will see a :guilabel:`Module update result` section indicating how many new modules were added
+.. i18n: and how many existing modules were updated. Click :guilabel:`Open Modules` to return to the updated list.
+..
+
+Click :guilabel:`Update` to start the update on the server side. When it is
+complete, you will see a :guilabel:`Module update result` section indicating how many new modules were added
+and how many existing modules were updated. Click :guilabel:`Open Modules` to return to the updated list.
+
+.. i18n: .. note:: Modules
+.. i18n:
+.. i18n: All the modules available on your computer can be found in the addons directory of your OpenERP
+.. i18n: server. Each module there is represented by a directory carrying the name of the module or by a
+.. i18n: file with the module name and .zip appended to it. The file is in ZIP archive format and replicates
+.. i18n: the directory structure of unzipped modules.
+..
+
+.. note:: Modules
+
+ All the modules available on your computer can be found in the addons directory of your OpenERP
+ server. Each module there is represented by a directory carrying the name of the module or by a
+ file with the module name and .zip appended to it. The file is in ZIP archive format and replicates
+ the directory structure of unzipped modules.
+
+.. i18n: .. tip:: Searching through the whole list
+.. i18n:
+.. i18n: The list of modules shows only the first available modules. In the web client you can search or
+.. i18n: follow the First / Previous / Next / Last links to get to any point in the whole list, and you can
+.. i18n: change the number of entries listed by clicking the row number indicators between :guilabel:`Previous`
+.. i18n: and :guilabel:`Next`
+.. i18n: and selecting a different number from the default of 20.
+.. i18n:
+.. i18n: If you use the GTK client you can search, as you would with the web client, or use the selection field
+.. i18n: (currently showing 80) to
+.. i18n: the top right of the window to change the number of entries returned by the search from its default
+.. i18n: limit of 80, or its default offset of 0 (starting at the first entry) in the whole list.
+..
+
+.. tip:: Searching through the whole list
+
+ The list of modules shows only the first available modules. In the web client you can search or
+ follow the First / Previous / Next / Last links to get to any point in the whole list, and you can
+ change the number of entries listed by clicking the row number indicators between :guilabel:`Previous`
+ and :guilabel:`Next`
+ and selecting a different number from the default of 20.
+
+ If you use the GTK client you can search, as you would with the web client, or use the selection field
+ (currently showing 80) to
+ the top right of the window to change the number of entries returned by the search from its default
+ limit of 80, or its default offset of 0 (starting at the first entry) in the whole list.
+
+.. i18n: .. index::
+.. i18n: single: module; installing
+..
+
+.. index::
+ single: module; installing
+
+.. i18n: The Configuration / Reconfigure Wizard
+.. i18n: --------------------------------------
+..
+
+The Configuration / Reconfigure Wizard
+--------------------------------------
+
+.. i18n: One of the new features of OpenERP is the :guilabel:`Configuration` wizard. Once run, the :guilabel:`Reconfigure` shortcut will appear. This wizard provides an easy way to install modules, thanks to its user-friendly and easy-to-use interface. The user may invoke this wizard at his own convenience using the shortcut :guilabel:`Reconfigure`, found just below the database and user name in the web interface or in the Shortcut menu in the GTK client. The same Configuration dialog box appears that you may have encountered at the time of installing a new database. Why did we call it the :guilabel:`Reconfigure` wizard? Indeed, because it allows the user to review installed applications and install related additional features or simply to install new applications on the fly.
+..
+
+One of the new features of OpenERP is the :guilabel:`Configuration` wizard. Once run, the :guilabel:`Reconfigure` shortcut will appear. This wizard provides an easy way to install modules, thanks to its user-friendly and easy-to-use interface. The user may invoke this wizard at his own convenience using the shortcut :guilabel:`Reconfigure`, found just below the database and user name in the web interface or in the Shortcut menu in the GTK client. The same Configuration dialog box appears that you may have encountered at the time of installing a new database. Why did we call it the :guilabel:`Reconfigure` wizard? Indeed, because it allows the user to review installed applications and install related additional features or simply to install new applications on the fly.
+
+.. i18n: When you go through the various steps in the wizard, you will come across some options that are checked and greyed. These are applications already installed. In the \ ``openerp_ch02`` \ database configuration, you may see that the \ ``Customer Relationship Management`` \ option is already checked because this Business Application has been installed in this database.
+.. i18n: Install extra applications simply by checking the corresponding options and clicking :guilabel:`Install` or click :guilabel:`Skip` to stop the configuration. You will eventually also come across the :guilabel:`CRM Application Configuration` step which you may use to add features to your CRM application. For now, select the \ ``Claims`` \ option and click :guilabel:`Configure`. This will in turn install the :mod:`crm_claim` module.
+..
+
+When you go through the various steps in the wizard, you will come across some options that are checked and greyed. These are applications already installed. In the \ ``openerp_ch02`` \ database configuration, you may see that the \ ``Customer Relationship Management`` \ option is already checked because this Business Application has been installed in this database.
+Install extra applications simply by checking the corresponding options and clicking :guilabel:`Install` or click :guilabel:`Skip` to stop the configuration. You will eventually also come across the :guilabel:`CRM Application Configuration` step which you may use to add features to your CRM application. For now, select the \ ``Claims`` \ option and click :guilabel:`Configure`. This will in turn install the :mod:`crm_claim` module.
+
+.. i18n: .. figure:: images/reconfigure_wizard.png
+.. i18n: :scale: 75
+.. i18n: :align: center
+.. i18n:
+.. i18n: *Reconfigure wizard showing Customer Relationship Management application as installed*
+..
+
+.. figure:: images/reconfigure_wizard.png
+ :scale: 75
+ :align: center
+
+ *Reconfigure wizard showing Customer Relationship Management application as installed*
+
+.. i18n: You may continue adding features this way, skip configuration steps or simply exit from this wizard. When you feel the need to
+.. i18n: load your system with additional features, you may invoke the :guilabel:`Reconfigure` wizard again at any point.
+..
+
+You may continue adding features this way, skip configuration steps or simply exit from this wizard. When you feel the need to
+load your system with additional features, you may invoke the :guilabel:`Reconfigure` wizard again at any point.
+
+.. i18n: .. note:: You can also change the Configuration Wizard through the :menuselection:`Administration --> Configuration --> Configuration Wizards --> Configuration Wizards`.
+..
+
+.. note:: You can also change the Configuration Wizard through the :menuselection:`Administration --> Configuration --> Configuration Wizards --> Configuration Wizards`.
+
+.. i18n: Installing an Application / Module from the Modules list
+.. i18n: --------------------------------------------------------
+..
+
+Installing an Application / Module from the Modules list
+--------------------------------------------------------
+
+.. i18n: .. index::
+.. i18n: single: module; google maps
+..
+
+.. index::
+ single: module; google maps
+
+.. i18n: You will now install a module named :mod:`google_map`, which will enable you to add a feature to the partner form to open the location directly in Google Maps. This is part of the core installation, so you do not need to load anything to make this work.
+..
+
+You will now install a module named :mod:`google_map`, which will enable you to add a feature to the partner form to open the location directly in Google Maps. This is part of the core installation, so you do not need to load anything to make this work.
+
+.. i18n: Open the list of modules from :menuselection:`Administration --> Modules --> Modules`. Search for the module by entering the name :mod:`google_map` in the :guilabel:`Name` field on the search screen then clicking it in the list that appears to open it. The form that describes the module gives you useful information such as its version number, its status and a review of its
+.. i18n: functionality. Click :guilabel:`Schedule for Installation` and the status of the module changes to :guilabel:`To be installed`.
+..
+
+Open the list of modules from :menuselection:`Administration --> Modules --> Modules`. Search for the module by entering the name :mod:`google_map` in the :guilabel:`Name` field on the search screen then clicking it in the list that appears to open it. The form that describes the module gives you useful information such as its version number, its status and a review of its
+functionality. Click :guilabel:`Schedule for Installation` and the status of the module changes to :guilabel:`To be installed`.
+
+.. i18n: .. tip:: From now on you can schedule and install modules from list view too. Notice the buttons on the right side and the action button to install.
+..
+
+.. tip:: From now on you can schedule and install modules from list view too. Notice the buttons on the right side and the action button to install.
+
+.. i18n: .. figure:: images/install_google_map_module.png
+.. i18n: :scale: 75
+.. i18n: :align: center
+.. i18n:
+.. i18n: *Installation of the Google Maps module*
+..
+
+.. figure:: images/install_google_map_module.png
+ :scale: 75
+ :align: center
+
+ *Installation of the Google Maps module*
+
+.. i18n: .. tip:: Technical Guide
+.. i18n:
+.. i18n: If you select a module in any of the module lists by clicking on a module line and then on
+.. i18n: :guilabel:`Technical Guide` at the top right of the window, OpenERP produces a technical report
+.. i18n: on that module. It is helpful only if the module is installed.
+.. i18n:
+.. i18n: This report comprises a list of all the objects and all the fields along with their descriptions.
+.. i18n: The report adapts to your system and reflects any modifications you have made and all the other
+.. i18n: modules you have installed.
+..
+
+.. tip:: Technical Guide
+
+ If you select a module in any of the module lists by clicking on a module line and then on
+ :guilabel:`Technical Guide` at the top right of the window, OpenERP produces a technical report
+ on that module. It is helpful only if the module is installed.
+
+ This report comprises a list of all the objects and all the fields along with their descriptions.
+ The report adapts to your system and reflects any modifications you have made and all the other
+ modules you have installed.
+
+.. i18n: Then, either use the menu :menuselection:`Administration --> Modules --> Apply Scheduled Upgrades`, or from the :guilabel:`Actions` section click :guilabel:`Apply Scheduled Upgrades`, then :guilabel:`Start update` on the :guilabel:`Module Upgrade`
+.. i18n: form that appears. Close the window when the operation has completed. Return to the :guilabel:`Sales` menu; you will
+.. i18n: see the new menu :menuselection:`Products` has become available.
+..
+
+Then, either use the menu :menuselection:`Administration --> Modules --> Apply Scheduled Upgrades`, or from the :guilabel:`Actions` section click :guilabel:`Apply Scheduled Upgrades`, then :guilabel:`Start update` on the :guilabel:`Module Upgrade`
+form that appears. Close the window when the operation has completed. Return to the :guilabel:`Sales` menu; you will
+see the new menu :menuselection:`Products` has become available.
+
+.. i18n: .. tip:: Refreshing the menu in the GTK Client
+.. i18n:
+.. i18n: After an update in the GTK client you will have to open a new menu to refresh the content –
+.. i18n: otherwise you will not see the new menu item. To do that, use the window menu :menuselection:`Form -->
+.. i18n: Reload / Undo` or use the shortcut :kbd:`Ctrl+R`.
+..
+
+.. tip:: Refreshing the menu in the GTK Client
+
+ After an update in the GTK client you will have to open a new menu to refresh the content –
+ otherwise you will not see the new menu item. To do that, use the window menu :menuselection:`Form -->
+ Reload / Undo` or use the shortcut :kbd:`Ctrl+R`.
+
+.. i18n: Installing a Module with its Dependencies
+.. i18n: -----------------------------------------
+..
+
+Installing a Module with its Dependencies
+-----------------------------------------
+
+.. i18n: .. index::
+.. i18n: single: module; stock
+..
+
+.. index::
+ single: module; stock
+
+.. i18n: Now install the Warehouse Management module using the same process as before.
+.. i18n: Start from :menuselection:`Administration --> Modules --> Modules`.
+..
+
+Now install the Warehouse Management module using the same process as before.
+Start from :menuselection:`Administration --> Modules --> Modules`.
+
+.. i18n: #. Get the list of modules, and search for the :mod:`stock` module in that list.
+.. i18n:
+.. i18n: #. Schedule the module for installation by clicking :guilabel:`Schedule for Installation`.
+.. i18n:
+.. i18n: #. Do the same for :mod:`account`.
+.. i18n:
+.. i18n: #. Click :guilabel:`Apply Scheduled Upgrades` on the action toolbar to the right.
+.. i18n:
+.. i18n: #. Click :guilabel:`Start update` to install both modules.
+.. i18n:
+.. i18n: #. After a few seconds, when the installation is complete, you may close this dialog box.
+.. i18n:
+.. i18n: #. You will see details of all the features installed by the modules on a new
+.. i18n: :guilabel:`Features` tab on the module form.
+..
+
+ #. Get the list of modules, and search for the :mod:`stock` module in that list.
+
+ #. Schedule the module for installation by clicking :guilabel:`Schedule for Installation`.
+
+ #. Do the same for :mod:`account`.
+
+ #. Click :guilabel:`Apply Scheduled Upgrades` on the action toolbar to the right.
+
+ #. Click :guilabel:`Start update` to install both modules.
+
+ #. After a few seconds, when the installation is complete, you may close this dialog box.
+
+ #. You will see details of all the features installed by the modules on a new
+ :guilabel:`Features` tab on the module form.
+
+.. i18n: When you return to the :menuselection:`Warehouse` menu, you will find the new menu items under it like
+.. i18n: :menuselection:`Warehouse --> Warehouse Management --> Incoming Shipments`, :menuselection:`Warehouse --> Products Moves`, which are a part of the Warehouse management system. You will also see all the accounting functions that are now available in the :menuselection:`Accounting` menu.
+..
+
+When you return to the :menuselection:`Warehouse` menu, you will find the new menu items under it like
+:menuselection:`Warehouse --> Warehouse Management --> Incoming Shipments`, :menuselection:`Warehouse --> Products Moves`, which are a part of the Warehouse management system. You will also see all the accounting functions that are now available in the :menuselection:`Accounting` menu.
+
+.. i18n: There is no particular relationship between the modules installed and the menus added. Most of the
+.. i18n: core modules add complete menus but some also add sub-menus to menus already in the system. Other
+.. i18n: modules add menus and sub-menus as they need. Modules can also add additional fields to existing
+.. i18n: forms, or simply additional demonstration data or some settings specific to a given requirement.
+..
+
+There is no particular relationship between the modules installed and the menus added. Most of the
+core modules add complete menus but some also add sub-menus to menus already in the system. Other
+modules add menus and sub-menus as they need. Modules can also add additional fields to existing
+forms, or simply additional demonstration data or some settings specific to a given requirement.
+
+.. i18n: .. index::
+.. i18n: single: module; dependencies
+.. i18n: ..
+..
+
+.. index::
+ single: module; dependencies
+..
+
+.. i18n: .. note:: Dependencies Between Modules
+.. i18n:
+.. i18n: The module form shows two tabs before it is installed.
+.. i18n: The first tab gives basic information about the module, and the
+.. i18n: second gives a list of modules that this module depends on. So when you install a module, OpenERP
+.. i18n: automatically selects all the necessary dependencies to install this module.
+.. i18n:
+.. i18n: That is also how you develop the profile modules: they simply define a list of modules that you want
+.. i18n: in your profile as a set of dependencies.
+..
+
+.. note:: Dependencies Between Modules
+
+ The module form shows two tabs before it is installed.
+ The first tab gives basic information about the module, and the
+ second gives a list of modules that this module depends on. So when you install a module, OpenERP
+ automatically selects all the necessary dependencies to install this module.
+
+ That is also how you develop the profile modules: they simply define a list of modules that you want
+ in your profile as a set of dependencies.
+
+.. i18n: Although you can install a module and all its dependencies at once, you cannot remove them in one
+.. i18n: fell swoop – you would have to uninstall module by module. Uninstalling is more complex than
+.. i18n: installing because you have to handle existing system data.
+..
+
+Although you can install a module and all its dependencies at once, you cannot remove them in one
+fell swoop – you would have to uninstall module by module. Uninstalling is more complex than
+installing because you have to handle existing system data.
+
+.. i18n: .. note:: Uninstalling Modules
+.. i18n:
+.. i18n: Although it works quite well, uninstalling modules is not perfect in OpenERP. It is not guaranteed
+.. i18n: to return the system exactly to the state it was in before installation.
+.. i18n:
+.. i18n: So it is recommended that you make a backup of the database before installing your new modules so
+.. i18n: that you can test the new modules and decide whether they are suitable or not. If they are not, then
+.. i18n: you can return to your backup. If they are, then you will probably still reinstall the modules on
+.. i18n: your backup so that you do not have to delete all your test data.
+.. i18n:
+.. i18n: If you wanted to uninstall, you would use the menu :menuselection:`Administration --> Modules
+.. i18n: --> Modules` and then uninstall them in the inverse order of their
+.. i18n: dependencies: ``stock``, ``account``.
+..
+
+.. note:: Uninstalling Modules
+
+ Although it works quite well, uninstalling modules is not perfect in OpenERP. It is not guaranteed
+ to return the system exactly to the state it was in before installation.
+
+ So it is recommended that you make a backup of the database before installing your new modules so
+ that you can test the new modules and decide whether they are suitable or not. If they are not, then
+ you can return to your backup. If they are, then you will probably still reinstall the modules on
+ your backup so that you do not have to delete all your test data.
+
+ If you wanted to uninstall, you would use the menu :menuselection:`Administration --> Modules
+ --> Modules` and then uninstall them in the inverse order of their
+ dependencies: ``stock``, ``account``.
+
+.. i18n: Installing Additional Functionality
+.. i18n: -----------------------------------
+..
+
+Installing Additional Functionality
+-----------------------------------
+
+.. i18n: To discover the full range of OpenERP's possibilities, you can install many additional modules.
+.. i18n: Installing them with their demonstration data provides a convenient way of exploring the whole core
+.. i18n: system. When you build on the \ ``openerp_ch02``\ database, you will automatically include
+.. i18n: demonstration data because you checked the :guilabel:`Load Demonstration Data` checkbox when you originally
+.. i18n: created the database.
+..
+
+To discover the full range of OpenERP's possibilities, you can install many additional modules.
+Installing them with their demonstration data provides a convenient way of exploring the whole core
+system. When you build on the \ ``openerp_ch02``\ database, you will automatically include
+demonstration data because you checked the :guilabel:`Load Demonstration Data` checkbox when you originally
+created the database.
+
+.. i18n: .. index::
+.. i18n: single: module; importing
+.. i18n: ..
+..
+
+.. index::
+ single: module; importing
+..
+
+.. i18n: Click :menuselection:`Administration --> Modules --> Modules` to give you an
+.. i18n: overview of all of the modules available for installation.
+..
+
+Click :menuselection:`Administration --> Modules --> Modules` to give you an
+overview of all of the modules available for installation.
+
+.. i18n: To test several modules, you will not have to install them all one by one. You can use the dependencies
+.. i18n: between modules to load several at once.
+..
+
+To test several modules, you will not have to install them all one by one. You can use the dependencies
+between modules to load several at once.
+
+.. i18n: .. Copyright © Open Object Press. All rights reserved.
+..
+
+.. Copyright © Open Object Press. All rights reserved.
+
+.. i18n: .. You may take electronic copy of this publication and distribute it if you don't
+.. i18n: .. change the content. You can also print a copy to be read by yourself only.
+..
+
+.. You may take electronic copy of this publication and distribute it if you don't
+.. change the content. You can also print a copy to be read by yourself only.
+
+.. i18n: .. We have contracts with different publishers in different countries to sell and
+.. i18n: .. distribute paper or electronic based versions of this book (translated or not)
+.. i18n: .. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. i18n: .. also helps us to create incentives to pay contributors and authors using author
+.. i18n: .. rights of these sales.
+..
+
+.. We have contracts with different publishers in different countries to sell and
+.. distribute paper or electronic based versions of this book (translated or not)
+.. in bookstores. This helps to distribute and promote the OpenERP product. It
+.. also helps us to create incentives to pay contributors and authors using author
+.. rights of these sales.
+
+.. i18n: .. Due to this, grants to translate, modify or sell this book are strictly
+.. i18n: .. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. i18n: .. written authorisation for this.
+..
+
+.. Due to this, grants to translate, modify or sell this book are strictly
+.. forbidden, unless Tiny SPRL (representing Open Object Press) gives you a
+.. written authorisation for this.
+
+.. i18n: .. Many of the designations used by manufacturers and suppliers to distinguish their
+.. i18n: .. products are claimed as trademarks. Where those designations appear in this book,
+.. i18n: .. and Open Object Press was aware of a trademark claim, the designations have been
+.. i18n: .. printed in initial capitals.
+..
+
+.. Many of the designations used by manufacturers and suppliers to distinguish their
+.. products are claimed as trademarks. Where those designations appear in this book,
+.. and Open Object Press was aware of a trademark claim, the designations have been
+.. printed in initial capitals.
+
+.. i18n: .. While every precaution has been taken in the preparation of this book, the publisher
+.. i18n: .. and the authors assume no responsibility for errors or omissions, or for damages
+.. i18n: .. resulting from the use of the information contained herein.
+..
+
+.. While every precaution has been taken in the preparation of this book, the publisher
+.. and the authors assume no responsibility for errors or omissions, or for damages
+.. resulting from the use of the information contained herein.
+
+.. i18n: .. Published by Open Object Press, Grand Rosière, Belgium
+..
+
+.. Published by Open Object Press, Grand Rosière, Belgium
=== added file 'i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_newfeatures.rst'
--- i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_newfeatures.rst 1970-01-01 00:00:00 +0000
+++ i18n/zh_CN/source/book/1/1_2_Guided_Tour/1_2_Guided_Tour_newfeatures.rst 2012-12-04 03:46:24 +0000
@@ -0,0 +1,320 @@
+
+.. i18n: *********************
+.. i18n: What's New in OpenERP
+.. i18n: *********************
+..
+
+*********************
+What's New in OpenERP
+*********************
+
+.. i18n: .. index::
+.. i18n: single: new
+.. i18n: single: features
+..
+
+.. index::
+ single: new
+ single: features
+
+.. i18n: General Features
+.. i18n: ================
+..
+
+General Features
+================
+
+.. i18n: * OpenERP has been structured as Business Applications and its menu has been changed to match this,
+.. i18n:
+.. i18n: * Major improvements in usability, especially in the Web version,
+.. i18n:
+.. i18n: * Simplified versus Extended view,
+.. i18n:
+.. i18n: * When you search for a record, e.g. a customer / supplier, the web version will propose to create the new partner when no existing partner is found,
+.. i18n:
+.. i18n: * When you click a Business Application in the Web version, the related Dashboard will be opened,
+.. i18n:
+.. i18n: * To display the process view, click the Question Mark next to the title in the web version,
+.. i18n:
+.. i18n: * Menutips & Tooltips will be displayed to explain more about the active screen,
+.. i18n:
+.. i18n: * Dynamic Filters which allow you to easily create and save your own filters, with Group by options, Extended filters, and much more,
+.. i18n:
+.. i18n: * User Roles are no longer used, they have been integrated in the User Groups,
+.. i18n:
+.. i18n: * The Administrator will now only have the rights according to the user groups that have been assigned to him,
+.. i18n:
+.. i18n: * Multicompany has been integrated in the core of OpenERP and does not require the installation of modules. You just have to add the User Group Useability / Multi-Company,
+.. i18n:
+.. i18n: * Perform actions, such as update status, confirm, delete, ... directly from List View,
+.. i18n:
+.. i18n: * Use communication tools such as Fetchmail, Outlook & Thunderbird integration and CalDAV / WebDAV (also available on Android & Iphone),
+.. i18n:
+.. i18n: * Create your own e-mail templates for use throughout OpenERP,
+.. i18n:
+.. i18n: * Use the Scheduler for objects other than Manufacturing too,
+.. i18n:
+.. i18n: * Click the `star` in the web version to quickly create a shortcut for a screen you often use,
+.. i18n:
+.. i18n: * When you perform an action in List view in the web version, (i.e. change the status of a lead), OpenERP will display a bar containing information about this change. You can click the link to open the lead concerned,
+.. i18n:
+.. i18n: * Updated configuration wizard to install new features using OpenERP modules in user friendly way.
+..
+
+* OpenERP has been structured as Business Applications and its menu has been changed to match this,
+
+* Major improvements in usability, especially in the Web version,
+
+* Simplified versus Extended view,
+
+* When you search for a record, e.g. a customer / supplier, the web version will propose to create the new partner when no existing partner is found,
+
+* When you click a Business Application in the Web version, the related Dashboard will be opened,
+
+* To display the process view, click the Question Mark next to the title in the web version,
+
+* Menutips & Tooltips will be displayed to explain more about the active screen,
+
+* Dynamic Filters which allow you to easily create and save your own filters, with Group by options, Extended filters, and much more,
+
+* User Roles are no longer used, they have been integrated in the User Groups,
+
+* The Administrator will now only have the rights according to the user groups that have been assigned to him,
+
+* Multicompany has been integrated in the core of OpenERP and does not require the installation of modules. You just have to add the User Group Useability / Multi-Company,
+
+* Perform actions, such as update status, confirm, delete, ... directly from List View,
+
+* Use communication tools such as Fetchmail, Outlook & Thunderbird integration and CalDAV / WebDAV (also available on Android & Iphone),
+
+* Create your own e-mail templates for use throughout OpenERP,
+
+* Use the Scheduler for objects other than Manufacturing too,
+
+* Click the `star` in the web version to quickly create a shortcut for a screen you often use,
+
+* When you perform an action in List view in the web version, (i.e. change the status of a lead), OpenERP will display a bar containing information about this change. You can click the link to open the lead concerned,
+
+* Updated configuration wizard to install new features using OpenERP modules in user friendly way.
+
+.. i18n: Business Application-related Features
+.. i18n: =====================================
+..
+
+Business Application-related Features
+=====================================
+
+.. i18n: *Sales Management*
+..
+
+*Sales Management*
+
+.. i18n: * CRM has been integrated in the Sales Management Business Application,
+.. i18n:
+.. i18n: * Geolocalization module, also allowing you to send qualified opportunities directly to external partners,
+.. i18n:
+.. i18n: * Manage your Marketing Campaigns and send automated e-mails based on your own templates,
+.. i18n:
+.. i18n: * For Leads, OpenERP will check the email address of the contact and when found for an existing partner, it will propose to merge the new contact with the corresponding partner,
+.. i18n:
+.. i18n: * Create your company wiki for Sales FAQ,
+.. i18n:
+.. i18n: * History tab in the Customer form to keep track of all events,
+.. i18n:
+.. i18n: * When you convert a lead to an opportunity, you now have the option to not create a partner, but just keep the contact data in the opportunity,
+.. i18n:
+.. i18n: * Create a new partner from a lead or an opportunity, or merge with an existing partner.
+..
+
+* CRM has been integrated in the Sales Management Business Application,
+
+* Geolocalization module, also allowing you to send qualified opportunities directly to external partners,
+
+* Manage your Marketing Campaigns and send automated e-mails based on your own templates,
+
+* For Leads, OpenERP will check the email address of the contact and when found for an existing partner, it will propose to merge the new contact with the corresponding partner,
+
+* Create your company wiki for Sales FAQ,
+
+* History tab in the Customer form to keep track of all events,
+
+* When you convert a lead to an opportunity, you now have the option to not create a partner, but just keep the contact data in the opportunity,
+
+* Create a new partner from a lead or an opportunity, or merge with an existing partner.
+
+.. i18n: *Warehouse Management*
+..
+
+*Warehouse Management*
+
+.. i18n: * Push & Pull rules for stock locations have been extended and integrated with multicompany,
+.. i18n:
+.. i18n: * Configure units of measure by reference unit, bigger than / smaller then reference unit,
+.. i18n:
+.. i18n: * Update stock level from the Product form and automatically create a physical inventory for it.
+..
+
+* Push & Pull rules for stock locations have been extended and integrated with multicompany,
+
+* Configure units of measure by reference unit, bigger than / smaller then reference unit,
+
+* Update stock level from the Product form and automatically create a physical inventory for it.
+
+.. i18n: *Accounting & Financial Management*
+..
+
+*Accounting & Financial Management*
+
+.. i18n: * By default, only one Entry Sequence is available for a journal. If you want to use two sequences for your journal numbering, please install the :mod:`account_sequence` module,
+.. i18n:
+.. i18n: * Separate numbering is now also available for Bank Journals,
+.. i18n:
+.. i18n: * Quickly enter Journal Entries from List View from the Journal Items menu. Configure your journal with default debit & credit accounts, select the journal in the Journal Items List View, click New and start creating new entries,
+.. i18n:
+.. i18n: * Chart of Accounts and Chart of Taxes can be displayed for a selected period,
+.. i18n:
+.. i18n: * OpenERP has added a flexible, easy Invoicing module allowing you to keep track of your accounting, even when you are not an accountant. If you install the Invoicing module, in Simplified view, you will only have the Invoicing items. You should not use both Invoicing and Accounting,
+.. i18n:
+.. i18n: * Use the Financial Management Configuration Wizard to easily select features you want to use,
+.. i18n:
+.. i18n: * On installation of a predefined Chart of Accounts, the wizard also proposes default bank and cash accounts, and default Sales and Purchase taxes,
+.. i18n:
+.. i18n: * On a journal you can set whether OpenERP should check if the invoice date is in the current period. This used to be a separate module,
+.. i18n:
+.. i18n: * Different journal types for Refunds and Invoices,
+.. i18n:
+.. i18n: * When creating a new journal, parameters are preset according to the journal type. The Entry Sequence for the journal is automatically created on Save,
+.. i18n:
+.. i18n: * Cash Box, possible to keep a real cash register.
+..
+
+* By default, only one Entry Sequence is available for a journal. If you want to use two sequences for your journal numbering, please install the :mod:`account_sequence` module,
+
+* Separate numbering is now also available for Bank Journals,
+
+* Quickly enter Journal Entries from List View from the Journal Items menu. Configure your journal with default debit & credit accounts, select the journal in the Journal Items List View, click New and start creating new entries,
+
+* Chart of Accounts and Chart of Taxes can be displayed for a selected period,
+
+* OpenERP has added a flexible, easy Invoicing module allowing you to keep track of your accounting, even when you are not an accountant. If you install the Invoicing module, in Simplified view, you will only have the Invoicing items. You should not use both Invoicing and Accounting,
+
+* Use the Financial Management Configuration Wizard to easily select features you want to use,
+
+* On installation of a predefined Chart of Accounts, the wizard also proposes default bank and cash accounts, and default Sales and Purchase taxes,
+
+* On a journal you can set whether OpenERP should check if the invoice date is in the current period. This used to be a separate module,
+
+* Different journal types for Refunds and Invoices,
+
+* When creating a new journal, parameters are preset according to the journal type. The Entry Sequence for the journal is automatically created on Save,
+
+* Cash Box, possible to keep a real cash register.
+
+.. i18n: *Project Management*
+..
+
+*Project Management*
+
+.. i18n: * Improved Gantt chart in the Web version,
+.. i18n:
+.. i18n: * Long Term Planning that can be calculated according to the working time of each em
Follow ups
