Return-Path: X-Original-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2074F7CCC for ; Mon, 19 Dec 2011 21:11:18 +0000 (UTC) Received: (qmail 95537 invoked by uid 500); 19 Dec 2011 21:11:18 -0000 Delivered-To: apmail-incubator-ooo-commits-archive@incubator.apache.org Received: (qmail 95491 invoked by uid 500); 19 Dec 2011 21:11:18 -0000 Mailing-List: contact ooo-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-commits@incubator.apache.org Received: (qmail 95483 invoked by uid 99); 19 Dec 2011 21:11:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Dec 2011 21:11:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Dec 2011 21:11:14 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id A5FB52388C22; Mon, 19 Dec 2011 21:10:23 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1220945 [11/28] - in /incubator/ooo/ooo-site/trunk/content/l10n: ./ L10N_Framework/ L10N_Framework/Examples.inv/ L10N_Framework/ooo20/ L10N_Framework/ooo20/oo_images/ download/ i18n_framework/ i18n_framework/cldr/ localization/ localizatio... Date: Mon, 19 Dec 2011 21:10:16 -0000 To: ooo-commits@incubator.apache.org From: wave@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20111219211023.A5FB52388C22@eris.apache.org> Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/LocaleData.html URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/LocaleData.html?rev=1220945&view=auto ============================================================================== --- incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/LocaleData.html (added) +++ incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/LocaleData.html Mon Dec 19 21:10:12 2011 @@ -0,0 +1,658 @@ + + + + + + + + + + + + + +

XlocaleData (an excerpt from +the Developers Guide I18n chapter)

[TOPIC:com.sun.star.i18n.XLocaleData]One +of the most important tasks in implementing a new locale is to define +all the locale data to be used, listed in the following table as +types returned by the [IDL:com.sun.star.i18n.XLocaleData] +interface methods:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ Type +	+ Count +
+ [IDL:com.sun.star.i18n.LanguageCountryInfo] +	+ exactly 1 +
+ [IDL:com.sun.star.i18n.LocaleDataItem] +	+ exactly 1 +
+ sequence<[IDL:com.sun.star.i18n.Calendar]> +	+ 1 or more +
+ sequence<[IDL:com.sun.star.i18n.Currency]> +	+ 1 or more +
+ sequence<[IDL:com.sun.star.i18n.FormatElement]> +	+ at least all + [IDL:com.sun.star.i18n.NumberFormatIndex] format codes (see + below) +
+ sequence<[IDL:com.sun.star.i18n.Implementation]> + collator implementations +	+ 0 or more, if none specified the + ICU collator will be called for the language given in + <LanguageCountryInfo> +
+ sequence<string> search + options (transliteration modules) +	+ 0 or more +
+ sequence<string> collation + options (transliteration modules) +	+ 0 or more +
+ sequence<string> names of + supported transliterations (transliteration modules) +	+ 0 or more +
+ [IDL:com.sun.star.i18n.ForbiddenCharacters] +	+ exactly 1, though may have empty + elements +
+ sequence<string> reserved + words +	+ all words of + [IDL:com.sun.star.i18n.reservedWords] +
+ sequence<[IDL:com.sun.star.beans.PropertyValues]> + numbering levels + (no public XLocaleData API method + available, used by and accessible through + [IDL:com.sun.star.text.XDefaultNumberingProvider] method + getDefaultContinuousNumberingLevels() implemented in i18npool) +	+ exactly 8 <NumberingLevel> + entities +
+ sequence<[IDL:com.sun.star.container.XIndexAccess]> + outline styles + (no public XLocaleData API method + available, used by and accessible through + [IDL:com.sun.star.text.XDefaultNumberingProvider] method + getDefaultOutlineNumberings() implemented in i18npool ) +	+ exactly 8 <OutlineStyle> + entities consisting of 5 <OutlineNumberingLevel> entities + each +

Locale data is defined in an XML file. +It is translated into a C++ source file during the build process, +which is compiled and linked together with other compiled locale data +files into shared libraries. The contents of the XML file, their +elements, and how they are to be defined are described in +i18npool/source/localedata/data/locale.dtd. +The latest revision available for a specific CVS branch of that file +provides up-to-date information about the definitions, as well as +additional information.

If the language-country combination is +not already listed in tools/inc/lang.hxx +and tools/source/intntl/isolang.cxx and +svx/source/dialog/langtab.src, +OpenOffice.org is probably not prepared to deal with your specific +locale. For assistance, you can consult +http://l10n.openoffice.org/adding_language.html#step1 +(Add the New Language to the Resource System) and join the +dev@l10n.openoffice.org mailing list (see +also +http://l10n.openoffice.org/servlets/ProjectMailingListList).

In order to conform with the available +build infrastructure, the name of your locale data file should follow +the conventions used in the i18npool/source/localedata/data +directory: <language>_<country>.xml, +where language is a lowercase, two letter +ISO-639 code, and country is an uppercase +two letter ISO-3166 code. Start by copying the en_US.xml +file to your <language>_<country>.xml +file and adopt the entries to suit your needs. Add the corresponding +*.cxx and *.obj +target file name to the i18npool/source/localedata/data/makefile.mk. +Note that there is an explicit rule defined, so that you do not need +to add the *.xml file name anywhere. You +must also add the locale to the aDllsTable +structure located in i18npool/source/localedata/data/localedata.cxx. +Make sure to specify the correct library name, since it must +correspond to the library name used in the makefile. Finally, the +public symbols to be exported must be added to the linker map file +corresponding to the library. You can use the +i18npool/source/localedata/data/linkermapfile-check.awk +script to assist you. Instructions for how to use +the script are located the header comments of the file.

<LC_FORMAT><FormatElement>

To be able to load documents of +versions up to and including StarOffice 5.2 (old binary file format), +each locale must define all number formats mentioned in +[IDL:com.sun.star.i18n.NumberFormatIndex] +and assign the proper formatindex="..." +attribute.
Failing to do so may result in data not properly +displayed or not displayed at all if a built-in "System" or +"Default" format code was used (as generally done by the +average user) and the document is loaded under a locale not having +those formats defined. Since old versions did merge some format +information of the [Windows] Regional Settings, it might be necessary +to define some duplicated codes to fill all positions. To verify that +all necessary elements are defined, use a non-product build of +OpenOffice.org and open a number formatting dialog, and select your +locale from the Language list box. An assertion message box +appears if there are any missing elements. The errors are only shown +the very first time the locale is selected in a given document.

<LC_FORMAT><FormatElement><FormatCode>

In general, definition of number +format codes follows the user visible rules, apart from that any +non-ASCII character must be entered using UTF-8 encoding. For a +detailed description of codes and a list of possible keywords please +consult the OpenOffice.org English online help on section "number +format codes".
Be sure to use the separators you declared in +the <LC_CTYPE> +section in the number format codes, for example <DecimalSeparator>, +<ThousandSeparator>, +otherwise the number formatter generates incorrect formats.
Verify +the defined codes again by using the number formatter dialog of a +non-product OpenOffice.org build. If anything is incorrect, an +assertion message box appears containing information about the +error.
The format indices 1..49 are reserved and, for backward +compatibility, must be used as stated in +offapi/com/sun/star/i18n/NumberFormatIndex.idl. +Note that 48 and 49 are used internally and must not be used in +locale data XML files. All other formats must be present.

Characters of date and time +keywords, such as YYYY for year, had previously been localized for a +few locales (for example, JJJJ in German). The new I18N framework no +longer follows that approach, because it may lead to ambiguous and +case insensitive character combinations that cannot be resolved at +runtime. Localized keyword support is only given for some old +locales, other locales must define their codes using English +notation.
The table below shows the localized keyword codes:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ + +	+ DayOfWeek +	+ Era +	+ Year +	+ Month +	+ Day +	+ Hour +
+ English (and all other locales + not mentioned) +	+ A +	+ G +	+ Y +	+ M +	+ D +	+ H +
+ de_AT, de_CH, de_DE, de_LI, de_LU +	+ + +	+ + +	+ J +	+ + +	+ T +	+ + +
+ nl_BE, nl_NL +	+ + +	+ + +	+ J +	+ + +	+ + +	+ U +
+ fr_BE, fr_CA, fr_CH, fr_FR, + fr_LU, fr_MC +	+ O +	+ + +	+ A +	+ + +	+ J +	+ + +
+ it_CH, it_IT +	+ O +	+ X +	+ A +	+ + +	+ G +	+ + +
+ pt_BR, pt_PT +	+ O +	+ + +	+ A +	+ + +	+ + +	+ + +
+ es_AR, es_BO, es_CL, es_CO, + es_CR, es_DO, es_EC, es_ES, es_GT, es_HN, es_MX, es_NI, es_PA, + es_PE, es_PR, es_PY, es_SV, es_UY, es_VE +	+ O +	+ + +	+ A +	+ + +	+ + +	+ + +
+ da_DK +	+ + +	+ + +	+ + +	+ + +	+ + +	+ T +
+ nb_NO, nn_NO, no_NO +	+ + +	+ + +	+ + +	+ + +	+ + +	+ T +
+ sv_FI, sv_SE +	+ + +	+ + +	+ + +	+ + +	+ + +	+ T +
+ fi_FI +	+ + +	+ + +	+ V +	+ K +	+ P +	+ T +

The formatindex="21" +[IDL:com.sun.star.i18n.NumberFormatIndex] DATE_SYS_DDMMYYYY +format code is used to edit date formatted data. It represents a date +using the most detailed information available, for example, a 4-digit +year and instead of a 2-digit year. The YMD default order (how a date +is assembled) is determined from the order encountered in this +format.
Similarly, the formatindex="47" +[IDL:com.sun.star.i18n.NumberFormatIndex] +DATETIME_SYS_DDMMYYYY_HHMMSS +format code is used to edit date-time data. Both format codes must +display data in a way that is parable by the application, in order to +be able to reassemble edited data. This generally means using only +YYYY,MM,DD,HH,MM,SS keywords and <DateSeparator> +and <TimeSeparator>.

The [$xxx-yyy] notation is needed +for compatibility reasons. The xxx +part denotes the currency symbol, and the yyy +part specifies the locale identifier in Microsoft Language ID +hexadecimal notation. For example, having “409” as the +locale identifier (English-US) and “$” as the currency +symbol results in [$$-409]. A list of available Language IDs known to +the OpenOffice.org application can be found at project util module +tools in file tools/inc/lang.hxx. Format +indices 12, 13, 14, 15, 17 with [$xxx-yyy] notation must use the xxx +currency symbol that has the attribute +usedInCompatibleFormatCodes="true" (see element +<LC_CURRENCY> +in the locale.dtd file).

+ + \ No newline at end of file Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/LocaleData.html ------------------------------------------------------------------------------ svn:eol-style = native Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Open-sourcing_i18n_framework.html URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Open-sourcing_i18n_framework.html?rev=1220945&view=auto ============================================================================== --- incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Open-sourcing_i18n_framework.html (added) +++ incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Open-sourcing_i18n_framework.html Mon Dec 19 21:10:12 2011 @@ -0,0 +1,434 @@ + + + + + + + + + + + +

Status open-sourcing i18n +framework

The sources are in the i18npool +project.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ Topic +	+ Problem +	+ Depends on +	+ Solution +	+ Effort +	+ Next step +	+ Status +
+ Localedata_CJK +						+ done +
+ Localedata_ASCII +						+ done +
+ Localedata UNO +						+ done +
+ XML Parser +						+ done +
+ Unotypes +						+ done +
+ Default Numberingprovider +						+ done +
+ Numberformat +						+ done +
+ CJK Breakiterator +		+ + +		+ + +	+ + +	+ done +
+ Search & Replace +		+ + +	+ + +		+ + +	+ done +
+ Transliteration +		+ + +	+ + +		+ + +	+ done +
+ Character classification +	+ + +		+ + +		+ + +	+ done +
+ Breakiterator +	+ + +		+ + +	+ + +	+ + +	+ done +
+ Calendar +	+ + +		+ + +	+ + +	+ + +	+ done +
+ Regular Expressions +	+ + +		+ + +	+ + +	+ + +	+ done +
+ General Collation +	+ + +		+ + +	+ + +	+ + +	+ done +
+ Register Services +	+ + +	+ Collation; Hangul/Hanja conversion +	+ + +	+ + +		+ done with exceptions as stated below +
+ CJK Collation +	+ ICU collation doesn't know "ignore Kana", + API and StarSuite do. +	+ Sun internal collation data +	+ Enhance ICU +	+ ? +	+ + +	+ + +
+ Western Collation +	+ ICU collation also ignores Width if only ignore + Case was requested, API allows distinction. +	+ Sun internal collation data +	+ Enhance ICU +	+ ? +	+ + +	+ + +
+ Hangul/Hanja Conversion +	+ Dictionary based conversion not open-sourceable. +	+ Proprietary Hangul/Hanja dictionary +	+ Will not be open-sourced +	+ + +	+ + +	+ + +

+ + \ No newline at end of file Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Open-sourcing_i18n_framework.html ------------------------------------------------------------------------------ svn:eol-style = native Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Paragraph_Alignment.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Paragraph_Alignment.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Paragraph_Alignment.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc.html URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc.html?rev=1220945&view=auto ============================================================================== --- incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc.html (added) +++ incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc.html Mon Dec 19 21:10:12 2011 @@ -0,0 +1,174 @@ + + + + + + + + + + + + + +

+

Vertical Writing in +Calc

To allow the user to write vertically in Calc cells the following +changes need to be made:

Current Status

Currently Vertical Writing only applies +to Western rules, the text will be positioned in a vertical manner +and the characters will be turned by 90° clockwise. This applies +to all characters without any exception (see figure 1). Furthermore +changing to edit mode in such formatted cell leads back to horizontal +input. The reading direction is also still left-to-right. This status +is sufficient for Western layout purposes and has to stay this way.

Rahmen1

CJK Sufficiency of Vertical Writing

While the vertical writing above applies to Western tastes it is +no match for Asian needs. Asian layout needs the following items:

Write right-to-left in vertical mode
+
Do not turn Western input 90° clockwise but have it + displayed vertically (see figure 2)
+
Do not turn special characters, such as brackets.
+
Do not change into horizontal input mode when in edit mode.
+

Rahmen2

+ + + + + + + + + + + + + + + +

+ English +	+ German +
+ Use Asian vertical layout mode +	+ Asiatischen, vertikalen Layout Modus benutzen +

To accomplish this layout scheme an enhanced UI must be created.

The user now can choose in between the old way by just pressing +the Text Direction button for Vertical Layout or one can chose to +activate the Asian Vertical Layout mode additionally. This would +switch in the mode described above.

Once the Text Direction button for Vertical Layout is unchecked +the "Use Asian vertical layout mode" checkbox/entry will be +greyed out. The status though should stay thus re-enabling vertical +layout will result in the last setting chosen before.

If Asian Language Support is disabled within StarOffice/StarSuite +the "Use Asian vertical layout mode" checkbox/entry must be +hidden. Furthermore the Object Bar should get two new symbols (“Text +direction from left to right” and “Text direction from +top to bottom”). Both are hidden by default. For further +details please refer to figure 3 below +

Figure + 3

+

+

+ + \ No newline at end of file Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc.html ------------------------------------------------------------------------------ svn:eol-style = native Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_35155795.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_35155795.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_35155795.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_m1a237ea2.png URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_m1a237ea2.png?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_m1a237ea2.png ------------------------------------------------------------------------------ svn:mime-type = image/png Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_m72f34545.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_m72f34545.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_Writing_in_Calc_html_m72f34545.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer.html URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer.html?rev=1220945&view=auto ============================================================================== --- incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer.html (added) +++ incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer.html Mon Dec 19 21:10:12 2011 @@ -0,0 +1,241 @@ + + + + + + + + + + + + + + +

Vertical Text Layout in +Writer

(Updated 02/01/2002)

Intro

Since Writer will be capable of vertical writing +form version 6.x on re-work on dialogues (nomenclature) and general +UI (button design) is needed,

The following commented screenshots will show +necessary changes. Please let me know if there are any dialogues +missing.

Please note: some of those tab pages will re-occur +in different occasions (like in “Paragraph” and “Page +Layout”).

General UI (Buttons)

As one can all possible buttons (incl. hidden +ones) are on display in figure above. Since they relate to vertical +text +

Nomenclature Changes

Due to the fact that “Left”, “Right”, +“Bottom” and “Top” will became relative terms +a new nomenclature is in need. Otherwise all dialogues and styles +need to be changed on the fly once text direction is changed.

Furthermore future text layout like Right-to-Left +are to be taken in consideration.

The array of various dialogues show new +nomenclature where ever applicable. +

All margin setting have been revised.

+ + + + + + + + + + + + + + + + + + + +

+ English +	+ German +
+ Margin before text +	+ Rand vor Text +
+ Margin after text +	+ Rand hinter Text +

All alignment settings have been revised as well +the text-to-text alignment (former vertical alignment).

Snap to text grid (if active): If active all Asian +character will automatically aligned to text grid if grid is set and +activated on page.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ English +	+ German +
+ At beginning of text +	+ Am Anfang des Textes +
+ At end of text +	+ Am Ende des Textes +
+ Text-to-text +	+ Text-an-Text +
+ Alignment +	+ Ausrichtung +
+ Snap to text grid (if active) +	+ Am Textraster ausrichten (wenn aktiviert) +

Text flow has been added to set up page layout +other than LTR direction. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

+ English +	+ German +
+ Text flow +	+ Textfluss +
+ Left-to-right (horizontal) +	+ Links-nach-rechts (Horizontal) +
+ Left-to-right (vertical) +	+ Links-nach-rechts (Vertikal) +
+ Right-to-left (horizontal) +	+ Rechts-nach-links (Horizontal) +
+ Right-to-left (vertical) +	+ Rechts-nach-links (Vertical) +

Exception so far:

Tab stops have alignments like right and left. I +have honestly not a clue how to give the text-flow-neutral names! +

Line Numbering

Line numbering with vertical text will have +numbers applied to “top” of page, 270°turned. See +figure below.

ask Japanese work mates,too

Cursor Travelling

Cursor should travel analogue/accordingly to +keyboard layout. I.e. cursor up always travel up, down always down +etc. Same behaviour as in text frames already implemented.

+ + \ No newline at end of file Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer.html ------------------------------------------------------------------------------ svn:eol-style = native Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_4c2567ee.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_4c2567ee.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_4c2567ee.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_51cc6311.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_51cc6311.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_51cc6311.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m1ed87497.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m1ed87497.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m1ed87497.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m349cc61e.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m349cc61e.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m349cc61e.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif Added: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m621fddc1.gif URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m621fddc1.gif?rev=1220945&view=auto ============================================================================== Binary file - no diff available. Propchange: incubator/ooo/ooo-site/trunk/content/l10n/i18n_framework/Vertical_writing_in_Writer_html_m621fddc1.gif ------------------------------------------------------------------------------ svn:mime-type = image/gif