https://wiki.openoffice.org/w/api.php?action=feedcontributions&feedformat=atom&user=Regina 2026-05-22T09:44:13Z User contributions MediaWiki 1.35.14 https://wiki.openoffice.org/w/index.php?title=Create_a_New_Custom_Shape_in_Source_in_File&diff=248969 2021-09-07T11:29:07Z

<p>Regina: /* References */</p> <hr /> <div>{|<br /> |-<br /> |{{DraftPage|EN}} || {{HelpNeeded|EN|Check the spelling, accuracy and style}}<br /> |}<br /> <br /> This tutorial addresses developers and advanced users. It shows how to generate a new custom shape. For this aim the source text of the file is edited directly. The tutorial is at the same time an introduction to the ODF specification of custom shapes.<br /> <br /> === Getting started ===<br /> This chapter gives you an overview about the work flow and tools by creating a simple shape step by step.<br /> <br /> ==== New Document ====<br /> In this tutorial we edit a file directly, no macro is used.<br /> <br /> Apache OpenOffice has a setting to optimize the file size. That is done by removing all unnecessary blanks and line ends, so that the whole content is one large line. That is very bad, when you will edit such file. Some editors might not even open the file because the line is too long. <br /> <br /> Therefore go to menu “Tools”, item “Options…”, and then section “Load/Save”. Disable the option “Size optimization for ODF format”.<br /> <br /> Now start with a new Draw document and insert a rectangle. Make sure you use the rectangle form the “Basic Shapes”. Name the shape “MyShape” and save the document to e.g. “Start.odg”. Close the document but not Apache OpenOffice.<br /> <br /> :Not starting from scratch but with an existing custom shape has some advantages: You need not take care about the document itself, about embedding the shape into a page and a layer, or about any styles.<br /> <br /> :It is useful to name a shape. Such named shape is listed in the Navigator and you can select it from the Navigator.<br /> <br /> A odg-document is actual a zip-container. So you first need to unzip the file. I use the application “7-Zip” for this task, because it does not look at the filename-extension, but can unzip the odg-file directly. Other unpacker might need, that you change the filename-extension from “.odg” to “.zip”.<br /> <br /> :The ODF specification knows a flat, not packed format too. It has the filename-extension “.fodg”, but Apache OpenOffice cannot yet read oder write it.<br /> <br /> You see some sub-folders and some files with filename-extension “.xml”. The file &lt;tt&gt;content.xml&lt;/tt&gt; is the file we are going to edit. It is useful to know a little bit about a markup languages like XML or HTML, but such knowledge is no precondition.<br /> <br /> ==== Examine the File &lt;tt&gt;content.xml&lt;/tt&gt; ====<br /> You can use each editor, which is able to write UTF-8 encoding. I work on Windows and prefer the application “XML Notepad 2007”, an editor, which handles nodes, so I do not need to write the tag syntax.<br /> <br /> First we will have a look at the file without editing it, to find the place where the custom shape is located. I&#039;ll comment the other parts shortly, but you need not knew any details.<br /> <br /> You see, that it is a usual xml-file. The first line contains the prolog&lt;br /&gt; &lt;tt&gt;&lt;nowiki&gt;&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;&lt;/nowiki&gt;&lt;/tt&gt;.<br /> <br /> Tbd:Picture<br /> <br /> The second line is very, very long. It contains a list of namespaces. Each element or attribute identifier is prefixed with a namespace to make it unique. Custom shapes use in most cases the prefixes &lt;tt&gt;draw:&lt;/tt&gt; and &lt;tt&gt;svg:&lt;/tt&gt;.<br /> <br /> The text &lt;tt&gt;&lt;office:scripts /&gt;&lt;/tt&gt; in the third line is the place where macros would go, when they were included in the document.<br /> <br /> The next part is enclosed in &lt;tt&gt;&lt;office:automatic-styles&gt;&lt;/tt&gt; ...&lt;tt&gt;&lt;/office:automatic-styles&gt;&lt;/tt&gt;. It contains the description of all direct, anonymous formatting, which you made using the toolbars. Your style definitions from the “Styles and Formatting&quot;-window are in the file &lt;tt&gt;styles.xml&lt;/tt&gt;. You will not need to use these parts, because you can style your shapes easily using the user interface of Apache OpenOffice.<br /> <br /> Now we come nearer to the shape. You see the tags &lt;tt&gt;&lt;office:body&gt;&lt;/tt&gt; and then &lt;tt&gt;&lt;office:drawing&gt;&lt;/tt&gt; and then &lt;tt&gt;&lt;draw:page ... &gt;&lt;/tt&gt;. And then the tag &lt;tt&gt;&lt;draw:custom-shape ...&gt;&lt;/tt&gt;. On target!<br /> <br /> Tbd:Picture<br /> <br /> ==== Understanding the Element &lt;tt&gt;custom-shape&lt;/tt&gt; ====<br /> In contrast to OOXML with its abbreviations, ODF is very verbose, so you will understand a lot of parts immediately.<br /> <br /> The element &lt;tt&gt;custom-shape&lt;/tt&gt; has some attributes and some sub-elements. The attributes describe the relation to the draw page. That is nothing specific, you will find it for all drawing objects.<br /> <br /> Tbd:Picture<br /> <br /> ;&lt;tt&gt;draw:style-name=&quot;gr1&quot;&lt;/tt&gt; :A reference to the graphic style, which is used for this shape. In that style you will find things like line width and fill color.<br /> ;&lt;tt&gt;draw:text-style-name=&quot;P1&quot;&lt;/tt&gt; :A reference to the text style, which is used for the text of the shape. In that style you will find the used font for example.<br /> ;&lt;tt&gt;draw:layer=&quot;layout&quot;&lt;/tt&gt; :A draw page consists of several layers, the default one for shapes in Draw is the layer “layout”. Other layers are “background” or “controls”, and you can define additional layers in Draw.<br /> ;&lt;tt&gt;draw:name=&quot;MyShape&quot;&lt;/tt&gt; :Do you recognize it? That is the name you have given to the rectangle. <br /> ;&lt;tt&gt;svg:width=&quot;6cm&quot; svg:height=&quot;6cm&quot;&lt;/tt&gt; :This gives the size of the shape.<br /> ;&lt;tt&gt;svg:x=&quot;3cm&quot; svg:y=&quot;2cm&quot;&lt;/tt&gt; :And this is the position of the left, top corner of the shape.<br /> <br /> The last four attributes correspond to the settings, which you can make in the “Position and Size” dialog of the shape. They define the rectangle with the green handles, which you see, when you click the shape. This information can be extended by an attribute svg:transform for rotation, shearing or any linear transformation matrix.<br /> <br /> The ODF specification does not create an own definition for these attributes, but uses the already well defined attributes of the SVG specification of the W3 consortium. When possible, the ODF specification uses SVG specifications or at least follow them close.<br /> <br /> ;&lt;tt&gt;&lt;text:p /&gt;&lt;/tt&gt; :Here you will see text, which you have entered in the shape. The rectangle has not got any text, therefore the element is empty. <br /> <br /> ;&lt;tt&gt;&lt;draw:enhanced-geometry ... /&gt;&lt;/tt&gt; :This is the distinctive part, it is specific to custom-shapes. Here we made our changes. The rectangle is a very simple shape, so the element has only some attributes but no sub-elements.<br /> <br /> Tbd:picture<br /> <br /> ;&lt;tt&gt;svg:viewBox&lt;/tt&gt; :This defines a local coordinate system, it does not define the size of the shape. The latter had already been defined above. The first two values are the minimum x- and y-value. They correspond to the left/top position, the third and forth value are width and height but now in local coordinates. If you omit this attribute, Apache OpenOffice uses min-x/min-y value 0 | 0 and width/height value 21600 | 21600. You can use smaller values if you like, because the coordinates of the points can be floating-point numbers. But when you will share your files with users of PowerPoint you should stick with 21600 | 21600, because PowerPoint can only use integer values in its current versions. The ODF specification would allow negative values for min-x/min-y, but because of {{bug|121453}} the coordinate system has to always start in 0 | 0.<br /> <br /> ;&lt;tt&gt;draw:type&lt;/tt&gt; :It defines the kind of shape. Apache OpenOffice uses this to track those shapes, which correspond to Microsoft custom shapes and to the predefined shapes in OOXML. So it does the right things when export a document into one of the formats of MSOffice. Shapes without such special treating shout get the default type &lt;tt&gt;non-primitive&lt;/tt&gt;.<br /> <br /> ;&lt;tt&gt;draw:enhanced-path&lt;/tt&gt; :It describes the line, which actually makes the shape. You can think of a custom shape as a rectangle canvas, on which lines are drawn. Such lines are called a “path”. The commands to define a path are based on the SVG path definitions, but they are not identical to them. Therefore the own namespace &lt;tt&gt;draw&lt;/tt&gt; is used. One restriction is, that always absolute coordinates for points are used. Consequently all commands are upper case letters.<br /> <br /> :Most commands start drawing from the actual position after drawing the previous commands. Therefore the path often starts with the move command M. A straight line is drawn by the command L. And the command Z will close the path. For the full set of available commands see the [http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1417000_253892949 section 19.145] in the specification or the list below.<br /> <br /> ==== Editing the Element &lt;tt&gt;custom-shape&lt;/tt&gt; ====<br /> The first own shape will be a parabola. So change the value of attributes &quot;draw:name&quot; to &quot;Parabola&quot; and &lt;code&gt;draw:type&lt;/code&gt; to &lt;code&gt;&quot;non-primitive&quot;&lt;/code&gt;<br /> <br /> It will be a normal parabola y=x² with a x-range from -3 to 3, which results in a y-range from 0 to 9. So we need &quot;svg:viewBox=&quot;0 0 6 9&quot; and have to transform the mathematical coordinates to this local coordinate system.<br /> <br /> A parabola can be drawn with a quadratic Béziercurve, which is command Q. But that kind of curve is not yet available in AOO3.4, but will be first implemented in AOO4.0. Therefore I use a cubic Bézier curve here, which is command C. In general a cubic Bézier curve is defined by start point, two control points and an end point. For the desired parabola the mathematical coordinates would be start point(-3|9), first control point (-1|-3), second control point (1|-3), and end point (3|9).<br /> <br /> [[File:HT_Draw-CustomShape_parabole.png|thumbnail|Mathematical coordinates (left) and local (screen) coordinates (right)]]<br /> <br /> We have to transform this mathematical points to the local coordinate system and get start point (0|0), first control (2|12), second control (4|12), and end point (6|0). Notice, that the control points are outside the range given by the attribute svg:viewBox, but that does not matter. Even the path itself may be outside.<br /> <br /> The command for the cubic Bézier curve does not contain the start point, but uses the current position of the path as start point. Therefor we first need to move to point (0|0). Write &lt;tt&gt;M 0 0&lt;/tt&gt;. The parameters for a command are separated by a space. The specification allows a comma too, but because of {{bug|121507}} it is not yet possible in AOO3.4. Then write &lt;tt&gt;C 2 12 4 12 6 0&lt;/tt&gt;. Do not close the path, so do not write &lt;tt&gt;Z&lt;/tt&gt;. That&#039;s all. Save the file. &#039;&#039;If you work directly on a fodg-file you have to close the file now.&#039;&#039;<br /> <br /> ====Getting back to Apache OpenOffice====<br /> We need to go back and undo our unzip. Do not zip the folder, but mark the whole content and zip it. You likely get a file, which is inside the folder, but that does not matter now. You need to rename the file to &lt;tt&gt;.odg&lt;/tt&gt; filename-extension. And you should use a filename, which gives you a hint, which shape you have designed in it. Name it &lt;tt&gt;Parabola.odg&lt;/tt&gt; for example. If you leave the file extension &lt;tt&gt;.zip&lt;/tt&gt; unchanged, you cannot open the file directly, but need to specify the import filter.<br /> <br /> Go back to Apache OpenOffice and open the file. You hopefully see a nice parabola.<br /> <br /> ====Make the Shape Available====<br /> But how make the new shape available for other documents? Use the Gallery! You can create an own theme, for example “Mathematics”. Click the shape, press the mouse button for about two seconds and then - still pressing down the mouse button - drag it into a theme.<br /> <br /> If you want to distribute your shapes, then you can distribute your Gallery theme or you collect your new shapes in a document, from which the user can drag them in his own Gallery.<br /> <br /> ====Working with the Shape====<br /> You can use your own shape the same way as the predefined ones. If you want it unfilled or with a thicker line, you can easily style it. Make the parabola wider or smaller, or rotate it. It will alway be a correct parabola with a smooth line. <br /> <br /> Tbd: picture of use<br /> <br /> == Unzip-Zip-Workflow for ODF Documents ==<br /> <br /> Although an .odg document is actually a zip-container, it has a special feature. The file mimetype (It has no filename-extension!) is not compressed and it needs to be the first file in the container. Your work-flow has to consider this.<br /> <br /> === Using Features of Windows ===<br /> # Rename the .odg file to .zip. Ignore the warning.<br /> # Double click the zip-container. Windows 7 treats a zip-container nearly as a folder and you will see a treeview of the container content.<br /> # Grab the file &quot;content.xml&quot; and drag it outside the container. Hold down the shift-key to move the file. Do not close the treeview of the container.<br /> # Open the file &quot;content.xml&quot; (or another one you will work on) in your favorite editor, make all the changes you want, save the file and then close it.<br /> # Grab the file and drag it back into the container.<br /> # Go one level up in the tree-view and rename the file back from .zip to the original .odg filename extension.<br /> # Open the file in Apache OpenOffice and check your changes.<br /> <br /> This work-flow leaves the file &#039;mimetype&#039; untouched, but you need to rename the .odg file.<br /> <br /> === Using the Packer 7-Zip on Windows ===<br /> # Right click the .odg file and open it with 7-Zip.<br /> # Right click the file content.xml and open it &quot;external&quot;, or double click the file. This will open it with the application, that is bound to the filename extension .xml. Or configure 7-Zip to use your favorite editor (only first time), and right click the file and choose item &quot;edit&quot;.<br /> # Make all your changes, save the file and close it. 7-Zip will notice, that the file is changed and ask you to update it. Agree.<br /> # Close 7-Zip.<br /> # Open the file in Apache OpenOffice, check your changes and save the file.<br /> <br /> 7-Zip will keep the file &#039;mimetype&#039; uncompressed. But unfortunately, 7-Zip will reorder the files alphabetically. Therefore the file &#039;mimetype&#039; is no longer the first one in the package. Saving the file with Apache OpenOffice will repair this, but might alter your changes too. Nevertheless this work-flow is very quick, when you do not want to alter the content, but only examine it.<br /> <br /> If you ever need to repair the .odg file using 7-Zip, you can do it this way:<br /> # Unpack the .odg file to e.g. C:\Temp\<br /> # Start command window.<br /> # Add 7-Zip temporarily to your path by e.g. &lt;tt&gt;set path=%path%;C:\Program Files\7-Zip\&lt;/tt&gt;<br /> # Change to directory C:\Temp\<br /> # Call the command line version of 7-Zip by &lt;tt&gt;7z a -mx=0 dummy.zip mimetype&lt;/tt&gt; (a means add, -mx=0 means without compressing).<br /> # Close command window. This will set back your path settings.<br /> # Use the Windows filemanager and drag the remaining files into the new dummy.zip container. You cannot do this with the file &#039;mimetype&#039;, because Windows will compress it automatically, when you drag it into a zip-container.<br /> # Rename the file dummy.zip to the correct file name having .odg file name extension.<br /> # Move the file to the desired place.<br /> <br /> === Using Cygwin ===<br /> This proposal will likely work similar on Linux, but I have not tested it.<br /> (proposed by Ariel Constenla-Haile, sited from mailinglist openoffice-dev https://mail-archives.apache.org/mod_mbox/openoffice-dev/201303.mbox/%3C20130328122918.GA598%40localhost%3E )<br /> All of the following should be available in your cygwin:<br /> <br /> only take the content.xml out of the ODF file:<br /> ]$ unzip demo.odg content.xml<br /> Archive: demo.odg<br /> inflating: content.xml <br /> <br /> indent it, to make it more readable:<br /> ]$ xmlindent -w content.xml<br /> <br /> edit it (vim has syntax highlighting):<br /> ]$ vim content.xml<br /> <br /> put the modified content.xml back:<br /> ]$ zip demo.odg content.xml<br /> updating: content.xml<br /> (deflated 84%)<br /> <br /> If you get a warning like this:<br /> zip warning: Local Entry CRC does not match CD: content.xml<br /> It&#039;s just a warning, the file can be opened safely (nevertheless, best back it up before playing with all this) vid.<br /> https://softsolder.com/2010/07/25/<br /> <br /> == Features in Detail ==<br /> <br /> ===Defining Cartesian Handles===<br /> In the next example a triangle with a vertical edge on the left side is made. The opposite corner will be movable up and down using a handle. The triangle is placed on a 10 × 10 canvas.<br /> <br /> [[File:FR.HT Draw-Forme personnalisee triangle.png|thumbnail|Triangle with vertical edge]]<br /> <br /> We start with a version that has the fixed corners in (0|0), (10|6) and (0|10). That is done nearly similar to the rectangle in section &quot;Getting started&quot;. Try it yourself. You should have got:<br /> &lt;syntaxhighlight lang=&quot;XML&quot;&gt;<br /> &lt;draw:enhanced-geometry<br /> svg:viewBox=&quot;0 0 10 10&quot;<br /> draw:type=&quot;non-primitive&quot;<br /> draw:enhanced-path=&quot;M 0 0 L 10 6 0 10 Z&quot;<br /> /&gt;<br /> &lt;/syntaxhighlight&gt;<br /> <br /> Why use the Z command and not a line to point (0|0)? Using a L command would not close the path to a polygon, but it would be a polyline with four points, which start and end points are accidentally at the same position. The command Z makes it a polygon with three points.<br /> <br /> A handle is a little yellow circle. You can drag it with the mouse and move it. Its coordinates are variable. Therefore the shape needs something to hold varying values. This is done in an attribute &lt;tt&gt;draw:modifiers&lt;/tt&gt; of the element draw:enhanced-geometry. It is a list of values. You write it with an initial value, but that will later on change, when you move the handle.<br /> &lt;pre&gt;&lt;draw:enhanced-geometry ... draw:modifiers=&quot;6&quot; /&gt;&lt;/pre&gt;<br /> <br /> The handle itself is made by an element &lt;tt&gt;draw:handle&lt;/tt&gt;, a sub-element of the element draw:enhanced-geometry. This has an attribute draw:handle-position with a pair of values. The first is the x-coordinate, the second the y-coordinate. The x-coordinate is 10, the y-coordinate gets a reference to the modifier. Such reference is written with the character $ followed by the position of the value in the list. Counting starts on 0. When you move the handle, the actual value is written to the modifier and when you change the modifier the handle will follow. So the text is now:<br /> &lt;syntaxhighlight lang=&quot;XML&quot;&gt;<br /> &lt;draw:enhanced-geometry <br /> ...<br /> draw:modifiers=&quot;6&quot;<br /> draw:enhanced-path=&quot;M 0 0 L 10 6 0 10 Z&quot; &gt;<br /> &lt;draw:handle draw:handle-position=&quot;10 $0&quot; /&gt;<br /> &lt;/draw:enhanced-geometry&gt;<br /> &lt;/syntaxhighlight&gt;<br /> Notice, that the element draw:handle has no content and therefore a combined start-end tag is used. And the element draw:enhanced-geometry now has a sub-element and therefore a separate end tag is needed.<br /> <br /> You should look at it in AOO. When you zip it, make sure that you only mark those files originally belonging to the document. Previous odg-files or backup files from your editor must not be included in the zip-archive.<br /> <br /> You should get a triangle and a handle. You can move the handle up and down, but the corner of the triangle will not yet follow the movement. The y-coordinate of the corner needs to use the modifier value too. That is done with a reference to the modifier. The syntax is the same as in the handle-position.<br /> <br /> Go back to your editor and change the attribute draw:enhanced-path to<br /> &lt;syntaxhighlight lang=&quot;XML&quot;&gt;<br /> draw:enhanced-path=&quot;M 0 0 L 10 $0 0 10 Z&quot;<br /> &lt;/syntaxhighlight&gt;<br /> <br /> So you have got finally<br /> &lt;syntaxhighlight lang=&quot;XML&quot;&gt;<br /> &lt;draw:enhanced-geometry<br /> svg:viewBox=&quot;0 0 10 10&quot;<br /> draw:type=&quot;non-primitive&quot;<br /> draw:modifiers=&quot;6&quot; <br /> draw:enhanced-path=&quot;M 0 0 L 10 $0 0 10 Z&quot; &gt;<br /> &lt;draw:handle draw:handle-position=&quot;10 $0&quot; /&gt;<br /> &lt;/draw:enhanced-geometry&gt;<br /> &lt;/syntaxhighlight&gt;<br /> <br /> Save, zip and tryout your shape.[[File:FR.HT_Draw-Forme_personnalisee_triangle_déformé.png|thumbnail]]<br /> <br /> ===Using Equations===<br /> This chapter shows you how to use equations by creating a parallelogram.<br /> <br /> The example parallelogram has a fixed edge on the left side and the opposite edge will be movable up and down. The coordinate system is again set to size 10 × 10.<br /> <br /> [[File:FR.HT_Draw-Forme_personnalisee_parallélogramme.png|thumbnail]]<br /> <br /> This is not very different from the triangle above, so try it yourself.<br /> <br /> You have likely written<br /> &lt;pre&gt;<br /> &lt;draw:enhanced-geometry<br /> svg:viewBox=&quot;0 0 10 10&quot;<br /> draw:type=&quot;non-primitive&quot;<br /> draw:modifiers=&quot;3&quot;<br /> draw:enhanced-path=&quot;M 0 0 L 10 $0 10 $0+10 0 10 Z&quot;&gt;<br /> &lt;draw:handle draw:handle-position=&quot;10 $0&quot; /&gt;<br /> &lt;/draw:enhanced-geometry&gt;<br /> &lt;/pre&gt;<br /> and find, that it does not work. That is because of the part &lt;tt&gt;$0+10&lt;/tt&gt; in the path. It is not possible to use an expression in a parameter of a command. A further element is needed, the element draw:equation.<br /> <br /> The element &lt;tt&gt;draw:equation&lt;/tt&gt; is a sub-element of the element draw:enhanced-geometry. It has an attribute &lt;tt&gt;draw:name&lt;/tt&gt; and an attribute &lt;tt&gt;draw:formula&lt;/tt&gt;. It has no child element, so it is a combined start-end tag &lt;draw:equation draw:name=&quot;...&quot; draw:formula=&quot;...&quot; /&gt;.<br /> <br /> The name of the formula is used to reference the value. The specification allows an arbitrary string as name. But Apache OpenOffice converts it automatically to &quot;f0&quot;, &quot;f1&quot;, &quot;f2&quot; and so on. So it is easier for you to identify your formulas, if you use these names from the beginning.<br /> <br /> The expression itself goes to the attribute formula. Besides the operators +, -, *, / you can use some functions (e.g. sqrt for the square root) and some special constants (e.g. pi). You find these in [http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1417052_253892949 chapter 19.171 draw:formula] in the specification or see the tables below. So your new element looks like &lt;tt&gt;&lt;draw:equation draw:name=&quot;f0&quot; draw:formula=&quot;$0+10&quot; /&gt;&lt;/tt&gt;.<br /> <br /> A reference is then used instead of the expression in the path. Such reference to a formula is written with a ? character immediately followed by the name of the equation. The path becomes &lt;tt&gt;draw:enhanced-path=&quot;M 0 0 L 10 $0 10 ?f0 0 10 Z&quot;&lt;/tt&gt;.<br /> <br /> All together you get the enhanced-geometry<br /> &lt;syntaxhighlight lang=&quot;XML&quot;&gt;<br /> &lt;draw:enhanced-geometry<br /> svg:viewBox=&quot;0 0 10 10&quot;<br /> draw:type=&quot;non-primitive&quot;<br /> draw:modifiers=&quot;3&quot;<br /> draw:enhanced-path=&quot;M 0 0 L 10 $0 10 ?f0 0 10 Z&quot;&gt;<br /> &lt;draw:equation draw:name=&quot;f0&quot; draw:formula=&quot;$0+10&quot; /&gt;<br /> &lt;draw:handle draw:handle-position=&quot;10 $0&quot; /&gt;<br /> &lt;/draw:enhanced-geometry&gt;<br /> &lt;/syntaxhighlight&gt;<br /> <br /> ===Defining Polar Handles===<br /> Tbd. Example right triangle with Thales circle<br /> <br /> ===Setting Gluepoints===<br /> Tbd. Setting glue points to the Thales circle<br /> <br /> ===Simple Text===<br /> Tbd. Example arc with text.<br /> <br /> ===FontWork===<br /> Tbd. Introduce fontwork attributes.<br /> <br /> ===Extruding===<br /> Tbd. Extrude with UI and show resulting elements and attributes<br /> <br /> == References ==<br /> <br /> &#039;&#039;&#039;Eisenberg, J. David&#039;&#039;&#039;&lt;br /&gt;&#039;&#039;Creating Custom Shapes&#039;&#039;.2005.&lt;br /&gt; http://books.evc-cit.info/books/odbook/custom_shapes_article.pdf [called 2021-09-07]<br /> <br /> &#039;&#039;&#039;OpenDocument-v1.2-part1&#039;&#039;&#039;&lt;br /&gt;&#039;&#039;Open Document Format for Office Applications (OpenDocument) Version 1.2&#039;&#039;&lt;br /&gt;&#039;&#039;Part1: OpenDocument Schema&#039;&#039;. 29 September 2011. OASIS Standard.&lt;br /&gt;http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html.<br /> <br /> &#039;&#039;&#039;W3C SVG Working Group&#039;&#039;&#039;&lt;br /&gt;&#039;&#039;SVG 1.1 Second Edition Recommendation&#039;&#039;. 16 August 2011.&lt;br /&gt; http://www.w3.org/TR/SVG/Overview.html</div>

Regina https://wiki.openoffice.org/w/index.php?title=MediaWiki:Books/Framework_Article&diff=237230 2016-01-18T21:53:27Z

<p>Regina: Created page with &quot;{{saved_book | setting-papersize = A4 | setting-showtoc = 1 | setting-columns = 1 }} == Framework Article == === OpenOffice.org 3.0 === :Framework/Article/Accelerators C...&quot;</p> <hr /> <div>{{saved_book<br /> | setting-papersize = A4<br /> | setting-showtoc = 1<br /> | setting-columns = 1<br /> }}<br /> <br /> == Framework Article ==<br /> === OpenOffice.org 3.0 ===<br /> :[[Framework/Article/Accelerators Configuration]]<br /> :[[Framework/Article/Addon Menu Toolbar Merging]]<br /> :[[Framework/Article/Asynchronous Callback Service]]<br /> :[[Framework/Article/Command Line Arguments]]<br /> :[[Framework/Article/Easy To Use Message Boxes]]<br /> :[[Framework/Article/Filter]]<br /> :[[Framework/Article/Gap Analysis Tookit API]]<br /> :[[Framework/Article/Generic UNO Interfaces for complex toolbar controls]]<br /> :[[Framework/Article/Implementation of the Dispatch API In SFX2]]<br /> :[[Framework/Article/Language Selection Statusbar Control]]<br /> :[[Framework/Article/OpenOffice.org 2.0 User Interface Controller Internals]]<br /> :[[Framework/Article/OpenOffice.org 2.x Commands]]<br /> :[[Framework/Article/OpenOffice.org 3.x Commands]]<br /> :[[Framework/Article/Options Dialog Configuration]]<br /> :[[Framework/Article/Tool Panels]]<br /> :[[Framework/Article/Tool Panels Internals]]<br /> :[[Framework/Article/VCLTestTool]]<br /> :[[Framework/WorkInProgress/Tabbed Windows Extension]]<br /> <br /> [[Category:Books|Framework Article]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Documentation/Building_Guide_AOO/Step_by_step&diff=236868 2015-10-27T16:38:38Z

<p>Regina: /* Windows 7 */ Warning not to use Windows unpacker added</p> <hr /> <div>{{DISPLAYTITLE:Step by step building guides for different platforms}}<br /> <br /> __TOC__<br /> <br /> This page is intended as a collection of simple step-by-step recipes to build Apache OpenOffice from source code. A more thorough explanation of what the individual steps do and why they are necessary can be found in the [[Documentation/Building_Guide_AOO|building guide]].<br /> =Ubuntu 14.04=<br /> The basic building steps under Ubuntu 12.04 (see below) are to be followed in Ubuntu 14.04 as well; however, there are some minor build issues that any developer, using this OS, needs to be aware of, if he gets stuck while building. The following is the list of issues, with their fixes, that a developer may face with:<br /> <br /> * Issue 124712 (build broken in svl); see the link https://issues.apache.org/ooo/show_bug.cgi?id=124712 for detailed information.<br /> If you are building trunk, the patch is already applied; if you are building from a release tag or tarball, the patch needs to be applied for all releases &lt;= 4.1.1.<br /> <br /> * Issue 125475; see the link https://issues.apache.org/ooo/show_bug.cgi?id=125475 for detailed information. This happens if you explicitly upgraded your GCC and related tools to version 4.9; it will not appear if you use GCC 4.8.x.<br /> <br /> As the BZ says, it is because of buggy toolchain g++4.9. So for now in Ubuntu Linux 14.04, build the source using g++4.8.2, gcc4.8.2; these are the default compilers in Ubuntu Linux 14.04 anyway; please check it using the following commands:<br /> g++ -v<br /> gcc -v<br /> if not, you&#039;ve to download them.<br /> sudo apt-get install g++-4.8<br /> cd /usr/bin<br /> rm gcc<br /> rm g++<br /> ln -s gcc-4.8 gcc<br /> ln -s g++-4.8 g++<br /> <br /> * Failed to find ./solver/420/unxlngx6.pro/lib/x86_64-linux-gnu/libstdc++.so.6.0.20 error.<br /> <br /> cp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.20 ./solver/420/unxlngx6.pro/lib/<br /> rm ./solver/420/unxlngx6.pro/lib/libstdc++.so.6<br /> ln -s ./solver/420/unxlngx6.pro/lib/libstdc++.so.6.0.20 ./solver/420/unxlngx6.pro/lib/libstdc++.so.6<br /> <br /> * No such file or directory - connectivity/virtualdbtools.hxx while building svx.<br /> <br /> if you get an error like this, then that means connectivity is not built properly. Build connectivity using build --all:connectivity and this error will go away.<br /> <br /> =Ubuntu 12.04=<br /> <br /> *Setup VirtualBox with Ubuntu 12.04 64 bit on Windows7 64bit host. A native installation is of course fine, too.<br /> *Let updater update ca. 380 packages. Restart.<br /> *Get the source. You can start with the source release or by checking out from SVN:<br /> {| class=&quot;prettytable&quot;<br /> |-<br /> ! Source release<br /> ! SVN<br /> |- valign=&quot;top&quot;<br /> | Build from source release if you want to build OpenOffice once but don&#039;t want to do any development.<br /> | Build from SVN if you want to development work with OpenOffice.<br /> |- valign=&quot;top&quot;<br /> | <br /> * Download AOO 4.1.1 source tarball from<br /> http://people.apache.org/~jsc/developer-snapshots/r1372282/src/aoo-4.1.1-incubating-src.tar.bz2<br /> <br /> * Optional: Download signature from<br /> http://people.apache.org/~jsc/developer-snapshots/r1372282/src/aoo-4.1.1-incubating-src.tar.bz2.asc<br /> <br /> and verify the source tarball with<br /> gpg --verify aoo-4.1.1-incubating-src.tar.bz2.asc \<br /> aoo-4.1.1-incubating-src.tar.bz2<br /> Note that you have to have the keys already imported to your key chain.<br /> The keys can be found on the download page:<br /> <br /> http://www.apache.org/dist/incubator/ooo/KEYS<br /> <br /> * Unpack source:<br /> cd /tmp<br /> tar -xjf ~/Downloads/aoo-4.1.1-incubating-src.tar.bz2<br /> cd aoo-4.1.1/main<br /> | <br /> * Start with creating a parent directory for the source code. Don&#039;t use &lt;code&gt;/tmp&lt;/code&gt; because that is deleted on every boot:<br /> sudo mkdir /source<br /> sudo chown &lt;your-user-name&gt; /source<br /> cd /source<br /> * Install subversion and checkout the source:<br /> sudo apt-get install subversion<br /> svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk<br /> cd aoo-trunk/main<br /> |}<br /> <br /> * Install requirements (this will also install packages that are not listed):<br /> sudo apt-get install g++ gcc bison flex libarchive-zip-perl libcups2-dev \<br /> libpam0g-dev gperf libfreetype6-dev libxaw7-dev libfontconfig1-dev \<br /> libxrandr-dev patch libgconf2-dev libgnomevfs2-dev ant libgtk2.0-dev \<br /> junit junit4 libidl-dev liborbit2-dev openjdk-6-jdk libwww-perl \<br /> libxml-parser-perl autoconf libssl-dev<br /> <br /> * Run autoconf to generate configure script:<br /> autoconf<br /> <br /> * Configure (see the building guide section on [[Documentation/Building_Guide_AOO#Configuration_and_bootstrapping|configuration]] for further options):<br /> ./configure \<br /> --with-dmake-url=http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 \<br /> --with-epm-url=http://www.msweet.org/files/project2/epm-3.7-source.tar.gz \<br /> --disable-odk \<br /> --disable-binfilter<br /> <br /> * Finish configuration and download missing tarballs and extensions:<br /> ./bootstrap<br /> <br /> * Include the configured environment:<br /> source LinuxX86-64Env.Set.sh<br /> <br /> * Build:<br /> cd instsetoo_native/<br /> build --all<br /> This may take a while to complete. Several hours are not uncommon. To speed things up you may want to run &#039;build&#039; like this<br /> build --all -P&lt;n&gt; -- -P&lt;n&gt;<br /> to start a parallel build. Replace &lt;n&gt; with the number of CPU cores. <br /> <br /> * Install:<br /> sudo dpkg -i unxlngx6.pro/Apache_OpenOffice/deb/install/en-US/DEBS/*.deb<br /> sudo dpkg -i unxlngx6.pro/Apache_OpenOffice/deb/install/en-US/DEBS/desktop-integration/openoffice4.2-debian-menus_4.2-9800_all.deb<br /> <br /> * Start Apache OpenOffice:<br /> /opt/openoffice4/program/soffice<br /> <br /> =Windows 7=<br /> <br /> &#039;&#039;&#039;Complete requirements found at [http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements General Build Requirements] and [http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows Building on Windows].&#039;&#039;&#039;<br /> This is a &#039;&#039;&#039;sample&#039;&#039;&#039; step-by-step guide - check the complete requirements and report on dev@openoffice.apache.org, if problems with this step-by-step guide occurs.<br /> <br /> *Install cygwin, &#039;&#039;&#039;32bit version&#039;&#039;&#039;<br /> **Browse to http://cygwin.com.<br /> **Click on the setup.exe link (most recent Cygwin DLL at the moment is 1.7.16-1) to download the installer and run it.<br /> **Click through the questions.<br /> **On the &quot;Choose A Download Site&quot; select a nearby download server.<br /> **Expect a &quot;Setup Alert&quot; dialog box on the first cygwin install on the computer.<br /> **Click OK to close it.<br /> **On the page that allows you to select additional packages just select wget (enter wget in the Search box and select the wget enty in the Web/Default section.<br /> **Click Next to finish package selection.<br /> **Click Next to resolve dependencies.<br /> **After installation is finished click the Finish button to close the dialog. <br /> <br /> *Start cygwin bash in a terminal<br /> ::One way to do this is:<br /> ::*Press WindowsKey-R<br /> ::*Enter c:\cygwin\Cygwin.bat<br /> ::*Hit Return.<br /> <br /> * Install Java.<br /> ::Choose between JDK 1.7 or OpenJDK.<br /> <br /> * Install Ant<br /> **Browse to http://ant.apache.org/bindownload.cgi<br /> **Chose a mirror near you.<br /> **Download the zip archive (currently that is apache-ant-1.8.4-bin.zip).<br /> **Open downloaded archive in file explorer and unzip it to a location of your choice, eg &lt;code&gt;c:\&lt;/code&gt;. Note that &lt;code&gt;C:\Program Files (x86)&lt;/code&gt; will not work due to problems of quoting the spaces and parentheses.<br /> <br /> * Prepare to install missing cygwin packages by installing apt-cyg from googlecode.com&lt;pre&gt;cd to /cygdrive/c/temp&lt;/pre&gt;(or any other temporary directory of your choice)&lt;pre&gt;wget http://apt-cyg.googlecode.com/svn/trunk/apt-cyg&amp;#10;chmod +x apt-cyg&amp;#10;mv apt-cyg /usr/local/bin/&lt;/pre&gt;<br /> * Use apt-cyg to install missing cygwin packages&lt;pre&gt;apt-cyg install perl zip unzip gperf autoconf rsync gcc4-g++ bison flex patch subversion&lt;/pre&gt;or alternatively run setup and select the packages&lt;br /&gt;If you will use git, you need in addition the packages&lt;pre&gt;git git-svn&lt;/pre&gt;<br /> <br /> * Replace symlinked awk with copy of gawk.exe:&lt;pre&gt;rm /usr/bin/awk&amp;#10;mv /usr/bin/gawk.exe /usr/bin/awk.exe&lt;/pre&gt;Note that if the &lt;code&gt;rm&lt;/code&gt; command fails then the &lt;code&gt;mv&lt;/code&gt; is not necessary.<br /> <br /> * Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1 (recommend by Microsoft) <br /> ** Browse to http://www.microsoft.com/en-us/download/details.aspx?id=3138.<br /> ** Download Setup.exe and run the web installer (note that it will be saved as Setup(1).exe to disambiguate from the previously downloaded cygwin installer.) You can use the default values in the installation dialog.<br /> ** Alternatively download the iso image http://www.microsoft.com/en-us/download/details.aspx?id=18950. Burn it to a dvd or unzip it.<br /> <br /> * Download MS Visual C++ 2008 SP1 Redistributable Package (x86)<br /> ** http://www.microsoft.com/en-us/download/details.aspx?id=26368 ( There have been security updates, which are not included in older versions.)<br /> **Download files vcredist_x86.exe and vcrestist_x64.exe&lt;br /&gt; If you download the most actual version of Apache OpenOffice and unpack it, you will find the files vcredist_x86.exe and vcredist_x64.exe in folder redist. You can use them as well.<br /> <br /> * Optional: Install DirectX SDK (for graphics hardware support in the slide show)<br /> ** Browse to http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&amp;id=6812<br /> ** Download and run DXSDK_Jun10.exe<br /> <br /> * Optional: Install NSIS installer (for creating the EXE installer)<br /> ** Browse to http://nsis.sourceforge.net<br /> ** Download and run the installer.<br /> <br /> * Get AOO source code. You can use the source release or check out from SVN. Build from source release if you want to build OpenOffice once but don&#039;t want to contribute patches. If you will contribute patches, you need to generate them against an actual version of trunk. In this case check out from SVN to be able to rebase before generating patches. You can work with subversion or with git-svn.<br /> <br /> ::; Source release : <br /> ::* Browse to http://www.openoffice.org/download/other.html#tested-sdk and locate the table row that starts with &quot;Source code&quot;<br /> ::* Download source code in an archive format of your choice (note that tar.bz2 is typically smaller than tar.gz and zip)<br /> ::* Optional: Verify the archive - following given link or instructions.<br /> ::* Unpack source (in cygwin-terminal). Use the file name exactly as downloaded.&lt;pre&gt;cd /tmp&amp;#10;tar -xjf &lt;download-location&gt;/&lt;downloaded-source-release.tar.bz2&gt;&amp;#10;cd &lt;unpacked-source&gt;/main&amp;#10;&lt;/pre&gt;Do not use Windows unpacker, they might cause access right problems. <br /> <br /> ::; Checkout from SVN using subversion :<br /> ::*Get subversion (only first time)&lt;pre&gt;apt-cyg install subversion&lt;/pre&gt; <br /> ::*Start with creating a parent directory for the source code: &lt;pre&gt;mkdir /cygdrive/c/source&amp;#10;cd /cygdrive/c/source&lt;/pre&gt;<br /> ::*Check out source from Apache SVN repository&lt;pre&gt;svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk&amp;#10;cd aoo-trunk/main&lt;/pre&gt;<br /> <br /> ::; Checkout from SVN using git-svn :<br /> ::*Get git and git-svn (only first time)&lt;pre&gt;apt-cyg install git git-svn&lt;/pre&gt;<br /> ::*Get the actual revision number from http://svn.apache.org/viewvc/OpenOffice/trunk/, e.g. 1234567<br /> ::*Create an empty directory and change to it, e.g.&lt;pre&gt;mkdir /cygdrive/c/source&amp;#10;cd /cygdrive/c/source&lt;/pre&gt;<br /> ::*Check out source from Apache SVN repository&lt;pre&gt;git svn clone --revision 1234567:HEAD https://svn.apache.org/repos/asf/openoffice/trunk&amp;#10;cd trunk/main&lt;/pre&gt;<br /> <br /> * Remember the source path (this is optional, it keeps the following lines short):&lt;pre&gt;SourceMain=`pwd`&lt;/pre&gt; [Why? I have not used it. [[User:Regina|Regina]] ([[User talk:Regina|talk]]) 21:42, 24 February 2013 (UTC)]<br /> :[Added explanation above [[User:Andre|Andre]]]<br /> <br /> * Optional: Get dbghelp.dll (for using the &lt;code&gt;--enable-dbgutil&lt;/code&gt; configure option)<br /> ** This dll is part of MS Visual Studio.<br /> ** Copy file to &lt;code&gt;main/external/dbghelp&lt;/code&gt;. Use Windows file manager or in cygwin terminal&lt;pre&gt;cp /cygdrive/c/Program\ Files\ \(x86\)/Microsoft\ Visual\ Studio\ 9.0/Common7/IDE/dbghelp.dll $SourceMain/external/dbghelp&lt;/pre&gt;<br /> <br /> * Copy vcredist_x86.exe and vcredist_x64.exe (see above) to main/external/vcredist.<br /> ** Use Windows file manager or in cygwin terminal&lt;pre&gt;cp &lt;download-location&gt;/vcredist_x86.exe $SourceMain/external/vcredist&amp;#10;cp &lt;download-location&gt;/vcredist_x64.exe $SourceMain/external/vcredist&lt;/pre&gt;<br /> <br /> * Get GDI+ redistributable.<br /> **Browse to http://www.microsoft.com/en-us/download/details.aspx?id=18909<br /> **Download WindowsXP-KB975337-x86-ENU.exe<br /> **Run WindowsXP-KB975337-x86-ENU.exe<br /> **Enter a temporary path (eg c:\temp\gdiplus) in the dialog and click OK to extract files<br /> **Copy gdiplus.dll to main/external&lt;pre&gt;cp /cygdrive/c/temp/gdiplus/asms/10/msft/windows/gdiplus/gdiplus.dll $SourceMain/external/gdiplus/&lt;/pre&gt;<br /> ** Remove the temporary path&lt;pre&gt;rm -fr /cygdrive/c/temp/gdiplus&lt;/pre&gt;<br /> <br /> * Get msvcr100.dll:&lt;pre&gt;cp /cygdrive/c/Windows/System32/msvcr100.dll $SourceMain/external/msvcp100&lt;/pre&gt;<br /> <br /> * Make sure that you are in the main source directory:&lt;pre&gt;cd $SourceMain&lt;/pre&gt;<br /> <br /> * Run autoconf to create the configure script:&lt;pre&gt;autoconf&lt;/pre&gt;<br /> <br /> * Call configure<br /> ** Run configure (adapt paths as necessary)&lt;pre&gt;SDK_PATH=&quot;/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0&quot;&amp;#10;./configure \&amp;#10; --with-frame-home=&quot;$SDK_PATH&quot; \&amp;#10; --with-psdk-home=&quot;$SDK_PATH&quot; \&amp;#10; --with-midl-path=&quot;$SDK_PATH/bin&quot; \&amp;#10; --with-directx-home=&quot;C:/Program Files (x86)/Microsoft DirectX SDK (June 2010)&quot; \&amp;#10; --with-ant-home=&quot;/cygdrive/c/apache-ant-1.8.4&quot; \&amp;#10; --with-dmake-url=&quot;http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2&quot; \&amp;#10; --with-epm-url=&quot;http://www.msweet.org/files/project2/epm-3.7-source.tar.gz&quot; \&amp;#10; --enable-pch \&amp;#10; --disable-atl \&amp;#10; --disable-activex \&amp;#10; --without-junit&lt;/pre&gt;If you have not installed the optional DirectX SDK then remove the &lt;code&gt;--with-directx-home switch&lt;/code&gt;<br /> *Finish configuration and download missing external source tarballs and extensions&lt;pre&gt;./bootstrap&lt;/pre&gt;<br /> * Include the configured environment&lt;pre&gt;source winenv.set.sh&lt;/pre&gt;<br /> * Build&lt;pre&gt;cd instsetoo_native/&amp;#10;build --all&lt;/pre&gt;Depending on your computer this will take one or more hours to finish.<br /> <br /> * Install&lt;br/&gt;There are three options:<br /> *# Regular install with integration into Windows.&lt;br/&gt;This allows only one instance of AOO to be installed.<br /> *#* Start setup.exe and click through dialog:&lt;br/&gt;&lt;pre&gt;$SourceMain/instsetoo_native/wntmsci12.pro/OpenOffice/msi/install/en-US/setup.exe&lt;/pre&gt;<br /> *#* Apache OpenOffice can be started via the Windows start menu.<br /> *# Install without integration into Windows.&lt;br/&gt;This allows several instance of AOO, based on the same version, to be installed side by side.&lt;br/&gt;It still requires Administrator permissions.<br /> *#* Start &lt;code&gt;setup.exe&lt;/code&gt; with option &lt;code&gt;-a&lt;/code&gt;:&lt;br/&gt;&lt;pre&gt;$SourceMain/instsetoo_native/wntmsci12.pro/OpenOffice/msi/install/en-US/setup.exe -a&lt;/pre&gt;<br /> *#* Enter an installation path into the dialog and click through the dialog to finish installation.<br /> *#* Start AOO by running&lt;br/&gt;&lt;pre&gt;&lt;installation-path&gt;/program/soffice.exe&lt;/pre&gt;<br /> *# Unpack archive without installation.&lt;br/&gt;This does not require Administrator permissions<br /> *#* Go to installation directory:&lt;br/&gt;&lt;pre&gt;cd &lt;installation-target&gt;&lt;/pre&gt;<br /> *#* Unzip archive:&lt;br/&gt;&lt;pre&gt;unzip $SourceMain/instsetoo_native/wntmsci12.pro/OpenOffice/archive/install/en-US/Apache_OpenOffice_4.0.1_Win_x86_install-arc_en-US.zip&lt;/pre&gt;<br /> *#* Start AOO by running:&lt;br/&gt;&lt;pre&gt;./Apache_OpenOffice_4.0.1_Win_x86_install-arc_en-US/program/soffice.exe&lt;/pre&gt;<br /> <br /> =[https://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_MacOSX Mac OS/X]=<br /> <br /> <br /> [[Category:Documentation]][[Category:Development]][[Category:Porting]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=User:Regina/MYDrafts6&diff=235711 2014-10-23T20:54:20Z

<p>Regina: </p> <hr /> <div>Comparison of color names<br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! html-color-name !! rgb !! example !! StarMath grammar !! StarMath token !! enum !! solution<br /> |-<br /> | white || #FFFFFF || &lt;span style=&quot;color:#FFFFFF&quot;&gt;example&lt;/span&gt; || white || TWHITE || COL_WHITE || nothing to do<br /> |-<br /> | silver || #C0C0C0 || &lt;span style=&quot;color:#C0C0C0&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGRAY || new StarMath color name &quot;silver&quot; added<br /> |-<br /> | gray || #808080 || &lt;span style=&quot;color:#808080&quot;&gt;example&lt;/span&gt; || -- || -- || COL_GRAY || new StarMath color name &quot;gray&quot; added<br /> |-<br /> | black || #000000 || &lt;span style=&quot;color:#000000&quot;&gt;example&lt;/span&gt; || black || TBLACK || COL_BLACK || nothing to do<br /> |-<br /> | red || #FF0000 || &lt;span style=&quot;color:#FF0000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTRED || ? conflict with StarMath &quot;red&quot; &lt;br /&gt;<br /> → StarMath &quot;red&quot; is now rendered as html-color-name &quot;red&quot;<br /> |-<br /> | maroon || #800000 || &lt;span style=&quot;color:#800000&quot;&gt;example&lt;/span&gt; || red || TRED || COL_RED || ? rendering is &quot;maroon&quot;, AOO file save is &quot;red&quot;&lt;br /&gt;→ new StarMath color name &quot;maroon&quot; added<br /> |-<br /> | yellow || #FFFF00 || &lt;span style=&quot;color:#FFFF00&quot;&gt;example&lt;/span&gt; || yellow || TYELLOW || COL_YELLOW || nothing to do<br /> |-<br /> | olive || #808000 || &lt;span style=&quot;color:#808000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_BROWN || new StarMath color name &quot;olive&quot; added<br /> |-<br /> | lime || #00FF00 || &lt;span style=&quot;color:#00FF00&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGREEN || new StarMath color name &quot;lime&quot; added<br /> |-<br /> | green || #008000 || &lt;span style=&quot;color:#008000&quot;&gt;example&lt;/span&gt; || green || TGREEN || COL_GREEN || nothing to do<br /> |-<br /> | aqua || #00FFFF || &lt;span style=&quot;color:#00FFFF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTCYAN || ? conflict with StarMath &quot;cyan&quot;&lt;br /&gt;→ new StarMath color name &quot;aqua&quot; added <br /> |-<br /> | teal || #008080 || &lt;span style=&quot;color:#008080&quot;&gt;example&lt;/span&gt; || cyan || TCYAN || COL_CYAN || ? rendering is &quot;teal&quot;, AOO file save is &quot;aqua&quot;&lt;br /&gt;→ new StarMath color name &quot;teal&quot; added, color name &quot;cyan&quot; is kept with wrong rendering for compatibility<br /> |-<br /> | blue || #0000FF || &lt;span style=&quot;color:#0000FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTBLUE || ? conflict with StarMath &quot;blue&quot;&lt;br /&gt;→ StarMath &quot;blue&quot; is now rendered as html-color-name &quot;blue&quot;<br /> |-<br /> | navy || #000080 || &lt;span style=&quot;color:#000080&quot;&gt;example&lt;/span&gt; || blue || TBLUE || COL_BLUE || ? rendering is &quot;navy&quot;, AOO file save is &quot;blue&quot;&lt;br /&gt;→ new StarMath color name &quot;navy&quot; added<br /> |-<br /> | fuchsia || #FF00FF || &lt;span style=&quot;color:#FF00FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTMAGENTA || ? conflict with StarMath &quot;magenta&quot;&lt;br /&gt;→ new StarMath color name &quot;fuchsia&quot; added<br /> |-<br /> | purple || #800080 || &lt;span style=&quot;color:#800080&quot;&gt;example&lt;/span&gt; || magenta || TMAGENTA || COL_MAGENTA || ? rendering is &quot;purple&quot;, AOO file save is &quot;fuchsia&quot;&lt;br /&gt;→ new StarMath color name &quot;purple&quot; added, color name &quot;magenta&quot; is kept with wrong rendering for compatibility<br /> |}</div>

Regina https://wiki.openoffice.org/w/index.php?title=User:Regina/MYDrafts6&diff=235710 2014-10-23T12:34:20Z

<p>Regina: </p> <hr /> <div>Comparison of color names<br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! html-color-name !! rgb !! example !! StarMath grammar !! StarMath token !! enum !! solution<br /> |-<br /> | white || #FFFFFF || &lt;span style=&quot;color:#FFFFFF&quot;&gt;example&lt;/span&gt; || white || TWHITE || COL_WHITE || nothing to do<br /> |-<br /> | silver || #C0C0C0 || &lt;span style=&quot;color:#C0C0C0&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGRAY || to be add as &quot;silver&quot;<br /> |-<br /> | gray || #808080 || &lt;span style=&quot;color:#808080&quot;&gt;example&lt;/span&gt; || -- || -- || COL_GRAY || to be add as &quot;gray&quot;<br /> |-<br /> | black || #000000 || &lt;span style=&quot;color:#000000&quot;&gt;example&lt;/span&gt; || black || TBLACK || COL_BLACK || nothing to do<br /> |-<br /> | red || #FF0000 || &lt;span style=&quot;color:#FF0000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTRED || ? conflict with StarMath &quot;red&quot;<br /> |-<br /> | maroon || #800000 || &lt;span style=&quot;color:#800000&quot;&gt;example&lt;/span&gt; || red || TRED || COL_RED || ? rendering is &quot;maroon&quot;, AOO file save is &quot;red&quot;<br /> |-<br /> | yellow || #FFFF00 || &lt;span style=&quot;color:#FFFF00&quot;&gt;example&lt;/span&gt; || yellow || TYELLOW || COL_YELLOW || nothing to do<br /> |-<br /> | olive || #808000 || &lt;span style=&quot;color:#808000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_BROWN || to be add as &quot;olive&quot;<br /> |-<br /> | lime || #00FF00 || &lt;span style=&quot;color:#00FF00&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGREEN || to be add as &quot;lime&quot;<br /> |-<br /> | green || #008000 || &lt;span style=&quot;color:#008000&quot;&gt;example&lt;/span&gt; || green || TGREEN || COL_GREEN || nothing to do<br /> |-<br /> | aqua || #00FFFF || &lt;span style=&quot;color:#00FFFF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTCYAN || ? conflict with StarMath &quot;cyan&quot;<br /> |-<br /> | teal || #008080 || &lt;span style=&quot;color:#008080&quot;&gt;example&lt;/span&gt; || cyan || TCYAN || COL_CYAN || ? rendering is &quot;teal&quot;, AOO file save is &quot;aqua&quot; <br /> |-<br /> | blue || #0000FF || &lt;span style=&quot;color:#0000FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTBLUE || ? conflict with StarMath &quot;blue&quot;<br /> |-<br /> | navy || #000080 || &lt;span style=&quot;color:#000080&quot;&gt;example&lt;/span&gt; || blue || TBLUE || COL_BLUE || ? rendering is &quot;navy&quot;, AOO file save is &quot;blue&quot;<br /> |-<br /> | fuchsia || #FF00FF || &lt;span style=&quot;color:#FF00FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTMAGENTA || ? conflict with StarMath &quot;magenta&quot;<br /> |-<br /> | purple || #800080 || &lt;span style=&quot;color:#800080&quot;&gt;example&lt;/span&gt; || magenta || TMAGENTA || COL_MAGENTA || ? rendering is &quot;purple&quot;, AOO file save is &quot;fuchsia&quot;<br /> |}</div>

Regina https://wiki.openoffice.org/w/index.php?title=User:Regina/MYDrafts6&diff=235709 2014-10-23T12:32:54Z

<p>Regina: </p> <hr /> <div>Comparison of color names<br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! html-color-name !! rgb !! example !! StarMath grammar !! StarMath token !! enum !! solution<br /> |-<br /> | white || #FFFFFF || &lt;span style=&quot;color:#FFFFFF&quot;&gt;example&lt;/span&gt; || white || TWHITE || COL_WHITE || nothing to do<br /> |-<br /> | silver || #C0C0C0 || &lt;span style=&quot;color:#C0C0C0&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGRAY || to be add as &quot;silver&quot;<br /> |-<br /> | gray || #808080 || &lt;span style=&quot;color:#808080&quot;&gt;example&lt;/span&gt; || -- || -- || COL_GRAY || to be add as &quot;gray&quot;<br /> |-<br /> | black || #000000 || &lt;span style=&quot;color:#000000&quot;&gt;example&lt;/span&gt; || black || TBLACK || COL_BLACK || nothing to do<br /> |-<br /> | red || #FF0000 || &lt;span style=&quot;color:#FF0000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTRED || ? conflict with StarMath &quot;red&quot;<br /> |-<br /> | maroon || #800000 || &lt;span style=&quot;color:#800000&quot;&gt;example&lt;/span&gt; || red || TRED || COL_RED || ? rendering is &quot;maroon&quot;, AOO file save is &quot;red&quot;<br /> |-<br /> | yellow || #FFFF00 || &lt;span style=&quot;color:#FFFF00&quot;&gt;example&lt;/span&gt; || yellow || TYELLOW || COL_YELLOW || nothing to do<br /> |-<br /> | olive || #808000 || &lt;span style=&quot;color:#808000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_BROWN || to be add as &quot;olive&quot;<br /> |-<br /> | lime || #00FF00 || &lt;span style=&quot;color:#00FF00&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGREEN || to be add as &quot;lime&quot;<br /> |-<br /> | green || #008000 || &lt;span style=&quot;color:#008000&quot;&gt;example&lt;/span&gt; || green || TGREEN || COL_GREEN || nothing to do<br /> |-<br /> | aqua || #00FFFF || &lt;span style=&quot;color:#00FFFF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTCYAN || ? conflict with StarMath &quot;cyan&quot;<br /> |-<br /> | teal || #008080 || &lt;span style=&quot;color:#008080&quot;&gt;example&lt;/span&gt; || cyan || TCYAN || COL_CYAN || ? rendering is &quot;teal&quot;, AOO file save is &quot;cyan&quot; <br /> |-<br /> | blue || #0000FF || &lt;span style=&quot;color:#0000FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTBLUE || ? conflict with StarMath &quot;blue&quot;<br /> |-<br /> | navy || #000080 || &lt;span style=&quot;color:#000080&quot;&gt;example&lt;/span&gt; || blue || TBLUE || COL_BLUE || ? rendering is &quot;navy&quot;, AOO file save is &quot;blue&quot;<br /> |-<br /> | fuchsia || #FF00FF || &lt;span style=&quot;color:#FF00FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTMAGENTA || ? conflict with StarMath &quot;magenta&quot;<br /> |-<br /> | purple || #800080 || &lt;span style=&quot;color:#800080&quot;&gt;example&lt;/span&gt; || magenta || TMAGENTA || COL_MAGENTA || ? rendering is &quot;purple&quot;, AOO file save is &quot;fuchsia&quot;<br /> |}</div>

Regina https://wiki.openoffice.org/w/index.php?title=User:Regina/MYDrafts6&diff=235708 2014-10-23T12:29:19Z

<p>Regina: Created page with &quot;Comparison of color names {| class=&quot;wikitable sortable&quot; |- ! html-color-name !! rgb !! example !! StarMath grammar !! StarMath token !! enum !! solution |- | white || #FFFFFF ...&quot;</p> <hr /> <div>Comparison of color names<br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! html-color-name !! rgb !! example !! StarMath grammar !! StarMath token !! enum !! solution<br /> |-<br /> | white || #FFFFFF || &lt;span style=&quot;color:#FFFFFF&quot;&gt;example&lt;/span&gt; || white || TWHITE || COL_WHITE || nothing to do<br /> |-<br /> | silver || #C0C0C0 || &lt;span style=&quot;color:#C0C0C0&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGRAY || to be add<br /> |-<br /> | gray || #808080 || &lt;span style=&quot;color:#808080&quot;&gt;example&lt;/span&gt; || -- || -- || COL_GRAY || to be add<br /> |-<br /> | black || #000000 || &lt;span style=&quot;color:#000000&quot;&gt;example&lt;/span&gt; || black || TBLACK || COL_BLACK || nothing to do<br /> |-<br /> | red || #FF0000 || &lt;span style=&quot;color:#FF0000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTRED || ? conflict with StarMath &quot;red&quot;<br /> |-<br /> | maroon || #800000 || &lt;span style=&quot;color:#800000&quot;&gt;example&lt;/span&gt; || red || TRED || COL_RED || ? rendering is &quot;maroon&quot;, AOO file save is &quot;red&quot;<br /> |-<br /> | yellow || #FFFF00 || &lt;span style=&quot;color:#FFFF00&quot;&gt;example&lt;/span&gt; || yellow || TYELLOW || COL_YELLOW || nothing to do<br /> |-<br /> | olive || #808000 || &lt;span style=&quot;color:#808000&quot;&gt;example&lt;/span&gt; || -- || -- || COL_BROWN || to be add<br /> |-<br /> | lime || #00FF00 || &lt;span style=&quot;color:#00FF00&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTGREEN || to be add<br /> |-<br /> | green || #008000 || &lt;span style=&quot;color:#008000&quot;&gt;example&lt;/span&gt; || green || TGREEN || COL_GREEN || nothing to do<br /> |-<br /> | aqua || #00FFFF || &lt;span style=&quot;color:#00FFFF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTCYAN || ? conflict with StarMath &quot;cyan&quot;<br /> |-<br /> | teal || #008080 || &lt;span style=&quot;color:#008080&quot;&gt;example&lt;/span&gt; || cyan || TCYAN || COL_CYAN || ? rendering is &quot;teal&quot;, AOO file save is &quot;cyan&quot; <br /> |-<br /> | blue || #0000FF || &lt;span style=&quot;color:#0000FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTBLUE || ? conflict with StarMath &quot;blue&quot;<br /> |-<br /> | navy || #000080 || &lt;span style=&quot;color:#000080&quot;&gt;example&lt;/span&gt; || blue || TBLUE || COL_BLUE || ? rendering is &quot;navy&quot;, AOO file save is &quot;blue&quot;<br /> |-<br /> | fuchsia || #FF00FF || &lt;span style=&quot;color:#FF00FF&quot;&gt;example&lt;/span&gt; || -- || -- || COL_LIGHTMAGENTA || ? conflict with StarMath &quot;magenta&quot;<br /> |-<br /> | purple || #800080 || &lt;span style=&quot;color:#800080&quot;&gt;example&lt;/span&gt; || magenta || TMAGENTA || COL_MAGENTA || ? rendering is &quot;purple&quot;, AOO file save is &quot;fuchsia&quot;<br /> |}</div>

Regina https://wiki.openoffice.org/w/index.php?title=User:Regina&diff=235707 2014-10-23T11:38:48Z

<p>Regina: </p> <hr /> <div>;native language: German<br /> ;active in project: de, qa, sc, graphics, LibreOffice, Apache OpenOffice<br /> ;user name: regina<br /> ;special interest: www.ooowiki.de<br /> ;email: rb.henschel@t-online.de<br /> <br /> [[Anleitung]]<br /> <br /> == ToDo ==<br /> === Working on functions sides ===<br /> [[Documentation/How_Tos/Calc: Statistical functions|&#039;&#039;&#039;Statistical functions&#039;&#039;&#039;]]<br /> <br /> [[Documentation/How_Tos/Calc: Functions listed alphabetically|&#039;&#039;&#039;Functions listed alphabetically&#039;&#039;&#039;]],<br /> [[Documentation/How_Tos/Calc: Functions listed by category|&#039;&#039;&#039;Functions listed by category&#039;&#039;&#039;]]<br /> <br /> [[Calc/ODFF_Implementation/Examine_functions|ODFF and accuracy problems in statitistic functions]]<br /> <br /> [[Calc/Drafts/Treatment_of_new_Excel_2010_functions|Treatment of new Excel 2010 functions]]<br /> <br /> === Planning Wiki-Pages ===<br /> [[/MyDrafts]] new document on &#039;&#039;Precision and Accuracy&#039;&#039;<br /> <br /> [[/MYDrafts2]] new specification for print ranges<br /> <br /> [[/MYDrafts3]] TTEST<br /> <br /> [[/MYDrafts4]] Angle problems in ODF 1.2<br /> <br /> [[/ComparisonWriterDrawPicture]] Comparison between Writer- and Draw-picture<br /> <br /> [[/MYDrafts5]] Custom Shapes<br /> <br /> === Development ===<br /> Currently: Adding more font colors to Math [[/MYDrafts6]] Colors in Math<br /> <br /> == Sandbox ==<br /> === math tests ===<br /> <br /> [[http://meta.wikimedia.org/wiki/Help:Formula]]<br /> <br /> Test Wiki-markup here<br /> <br /> &lt;math&gt;\sum_{k=1}^N k \pm i&lt;/math&gt;<br /> <br /> &lt;math&gt;a - b &lt;/math&gt;<br /> <br /> &lt;math&gt;a + b&lt;/math&gt;<br /> <br /> &lt;math&gt;{a \pm b}&lt;/math&gt;<br /> <br /> &lt;nowiki&gt;&lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;<br /> <br /> &lt;math&gt;\scriptstyle \sqrt {n-1}&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\scriptstyle \sqrt {n-1}&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\sqrt {n-1}&lt;/math&gt; &lt;nowiki&gt;&lt;math&gt;\sqrt {n-1}&lt;/math&gt; &lt;/nowiki&gt; <br /> <br /> &lt;math&gt; s_{X_1 - X_2}&lt;/math&gt; &lt;nowiki&gt;&lt;math&gt; s_{X_1 - X_2}&lt;/math&gt; &lt;/nowiki&gt; <br /> <br /> &lt;math&gt;1-P( -|z| \le Z \le |z|)&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;1-P( -|z| \le Z \le |z|)&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\textstyle \sum_{k=1}^N k^2&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\textstyle \sum_{k=1}^N k^2&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;nowiki&gt;&lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;<br /> <br /> &lt;math&gt;\frac{1}{N} \sum_{k=2}^N k^2&lt;/math&gt;<br /> &lt;nowiki&gt;&lt;math&gt;\frac{1}{N} \sum_{k=2}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\frac{1} {n} \sum_{i} {(x_i - \bar x)(y_i - \bar y)}&lt;/math&gt;<br /> &lt;nowiki&gt;\frac{1} {n} \sum_{i} {(x_i - \bar x)(y_i - \bar y)}&lt;/math&gt;&lt;/nowiki&gt;<br /> <br /> === dashboard ===</div>

Regina https://wiki.openoffice.org/w/index.php?title=User:Regina&diff=235706 2014-10-23T11:37:27Z

<p>Regina: /* Development */</p> <hr /> <div>;native language: German<br /> ;active in project: de, qa, sc, graphics, LibreOffice, Apache OpenOffice<br /> ;user name: regina<br /> ;special interest: www.ooowiki.de<br /> ;email: rb.henschel@t-online.de<br /> <br /> [[Anleitung]]<br /> <br /> == ToDo ==<br /> === Working on functions sides ===<br /> [[Documentation/How_Tos/Calc: Statistical functions|&#039;&#039;&#039;Statistical functions&#039;&#039;&#039;]]<br /> <br /> [[Documentation/How_Tos/Calc: Functions listed alphabetically|&#039;&#039;&#039;Functions listed alphabetically&#039;&#039;&#039;]],<br /> [[Documentation/How_Tos/Calc: Functions listed by category|&#039;&#039;&#039;Functions listed by category&#039;&#039;&#039;]]<br /> <br /> [[Calc/ODFF_Implementation/Examine_functions|ODFF and accuracy problems in statitistic functions]]<br /> <br /> [[Calc/Drafts/Treatment_of_new_Excel_2010_functions|Treatment of new Excel 2010 functions]]<br /> <br /> === Planning Wiki-Pages ===<br /> [[/MyDrafts]] new document on &#039;&#039;Precision and Accuracy&#039;&#039;<br /> <br /> [[/MYDrafts2]] new specification for print ranges<br /> <br /> [[/MYDrafts3]] TTEST<br /> <br /> [[/MYDrafts4]] Angle problems in ODF 1.2<br /> <br /> [[/ComparisonWriterDrawPicture]] Comparison between Writer- and Draw-picture<br /> <br /> [[/MYDrafts5]] Custom Shapes<br /> <br /> === Development ===<br /> Currently: Adding more font colors to Math<br /> <br /> == Sandbox ==<br /> === math tests ===<br /> <br /> [[http://meta.wikimedia.org/wiki/Help:Formula]]<br /> <br /> Test Wiki-markup here<br /> <br /> &lt;math&gt;\sum_{k=1}^N k \pm i&lt;/math&gt;<br /> <br /> &lt;math&gt;a - b &lt;/math&gt;<br /> <br /> &lt;math&gt;a + b&lt;/math&gt;<br /> <br /> &lt;math&gt;{a \pm b}&lt;/math&gt;<br /> <br /> &lt;nowiki&gt;&lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;<br /> <br /> &lt;math&gt;\scriptstyle \sqrt {n-1}&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\scriptstyle \sqrt {n-1}&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\sqrt {n-1}&lt;/math&gt; &lt;nowiki&gt;&lt;math&gt;\sqrt {n-1}&lt;/math&gt; &lt;/nowiki&gt; <br /> <br /> &lt;math&gt; s_{X_1 - X_2}&lt;/math&gt; &lt;nowiki&gt;&lt;math&gt; s_{X_1 - X_2}&lt;/math&gt; &lt;/nowiki&gt; <br /> <br /> &lt;math&gt;1-P( -|z| \le Z \le |z|)&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;1-P( -|z| \le Z \le |z|)&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\textstyle \sum_{k=1}^N k^2&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\textstyle \sum_{k=1}^N k^2&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;nowiki&gt;&lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;<br /> <br /> &lt;math&gt;\frac{1}{N} \sum_{k=2}^N k^2&lt;/math&gt;<br /> &lt;nowiki&gt;&lt;math&gt;\frac{1}{N} \sum_{k=2}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\frac{1} {n} \sum_{i} {(x_i - \bar x)(y_i - \bar y)}&lt;/math&gt;<br /> &lt;nowiki&gt;\frac{1} {n} \sum_{i} {(x_i - \bar x)(y_i - \bar y)}&lt;/math&gt;&lt;/nowiki&gt;<br /> <br /> === dashboard ===</div>

Regina https://wiki.openoffice.org/w/index.php?title=User:Regina&diff=235705 2014-10-23T11:36:22Z

<p>Regina: /* Planning Wiki-Pages */</p> <hr /> <div>;native language: German<br /> ;active in project: de, qa, sc, graphics, LibreOffice, Apache OpenOffice<br /> ;user name: regina<br /> ;special interest: www.ooowiki.de<br /> ;email: rb.henschel@t-online.de<br /> <br /> [[Anleitung]]<br /> <br /> == ToDo ==<br /> === Working on functions sides ===<br /> [[Documentation/How_Tos/Calc: Statistical functions|&#039;&#039;&#039;Statistical functions&#039;&#039;&#039;]]<br /> <br /> [[Documentation/How_Tos/Calc: Functions listed alphabetically|&#039;&#039;&#039;Functions listed alphabetically&#039;&#039;&#039;]],<br /> [[Documentation/How_Tos/Calc: Functions listed by category|&#039;&#039;&#039;Functions listed by category&#039;&#039;&#039;]]<br /> <br /> [[Calc/ODFF_Implementation/Examine_functions|ODFF and accuracy problems in statitistic functions]]<br /> <br /> [[Calc/Drafts/Treatment_of_new_Excel_2010_functions|Treatment of new Excel 2010 functions]]<br /> <br /> === Planning Wiki-Pages ===<br /> [[/MyDrafts]] new document on &#039;&#039;Precision and Accuracy&#039;&#039;<br /> <br /> [[/MYDrafts2]] new specification for print ranges<br /> <br /> [[/MYDrafts3]] TTEST<br /> <br /> [[/MYDrafts4]] Angle problems in ODF 1.2<br /> <br /> [[/ComparisonWriterDrawPicture]] Comparison between Writer- and Draw-picture<br /> <br /> [[/MYDrafts5]] Custom Shapes<br /> <br /> === Development ===<br /> Currently: Adapt smoothing with splines to ODF1.2 norm<br /> <br /> == Sandbox ==<br /> === math tests ===<br /> <br /> [[http://meta.wikimedia.org/wiki/Help:Formula]]<br /> <br /> Test Wiki-markup here<br /> <br /> &lt;math&gt;\sum_{k=1}^N k \pm i&lt;/math&gt;<br /> <br /> &lt;math&gt;a - b &lt;/math&gt;<br /> <br /> &lt;math&gt;a + b&lt;/math&gt;<br /> <br /> &lt;math&gt;{a \pm b}&lt;/math&gt;<br /> <br /> &lt;nowiki&gt;&lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;<br /> <br /> &lt;math&gt;\scriptstyle \sqrt {n-1}&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\scriptstyle \sqrt {n-1}&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\sqrt {n-1}&lt;/math&gt; &lt;nowiki&gt;&lt;math&gt;\sqrt {n-1}&lt;/math&gt; &lt;/nowiki&gt; <br /> <br /> &lt;math&gt; s_{X_1 - X_2}&lt;/math&gt; &lt;nowiki&gt;&lt;math&gt; s_{X_1 - X_2}&lt;/math&gt; &lt;/nowiki&gt; <br /> <br /> &lt;math&gt;1-P( -|z| \le Z \le |z|)&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;1-P( -|z| \le Z \le |z|)&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\textstyle \sum_{k=1}^N k^2&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\textstyle \sum_{k=1}^N k^2&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt; &lt;nowiki&gt; &lt;math&gt;\int_{1}^{3}\frac{e^3/x}{x^2}\, dx&lt;/math&gt; &lt;/nowiki&gt;<br /> <br /> &lt;nowiki&gt;&lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> &lt;math&gt;\sum_{k=1}^N k^2&lt;/math&gt;<br /> <br /> &lt;math&gt;\frac{1}{N} \sum_{k=2}^N k^2&lt;/math&gt;<br /> &lt;nowiki&gt;&lt;math&gt;\frac{1}{N} \sum_{k=2}^N k^2&lt;/math&gt;&lt;/nowiki&gt;<br /> <br /> &lt;math&gt;\frac{1} {n} \sum_{i} {(x_i - \bar x)(y_i - \bar y)}&lt;/math&gt;<br /> &lt;nowiki&gt;\frac{1} {n} \sum_{i} {(x_i - \bar x)(y_i - \bar y)}&lt;/math&gt;&lt;/nowiki&gt;<br /> <br /> === dashboard ===</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide&diff=230514 2013-08-28T18:40:25Z

<p>Regina: Added advise for translating the page</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Pootle User Guide}}<br /> __NOTOC__<br /> <br /> [http://www.apache.org/| The Apache Software Foundation] runs a Pootle Translate service to allow its projects an easy, cooperative way to localize their products. This guide describes how to use Pootle in the Apache OpenOffice project. As of August 2013, already 40 languages (out of the 120+ languages OpenOffice supports) are maintained in Pootle and more coming soon.<br /> <br /> For an introduction to the localization process read http://openoffice.apache.org/translate.html and for a more general overview start at http://openoffice.apache.org/get-involved.html.<br /> <br /> ;[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]: The chapter describes how to become a Translator.<br /> ;[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]: The chapter introduces you to the elements in the user interface of Pootle. <br /> ;[[Pootle_User_Guide/Offline_Translation|Offline Translation]]: The chapter explains how to translate offline.<br /> ;[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]: The chapter provides tips to ensure a high quality of the translation.<br /> ;[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]: The chapter describes the steps needed to provide a localized version of Apache OpenOffice.<br /> ;[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]: The chapter shows you helpers for the process of translation.<br /> ;[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]: The chapter lists tips and tricks for translating the user interface of Apache OpenOffice.<br /> ;[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]: The chapter lists tips and tricks for translating the built-in help of Apache OpenOffice.<br /> ;[[Pootle_User_Guide/General_Problems|General Problems]]: The chapter gives you assistance in general problems, which might occur during the translating process.<br /> <br /> [[Category:Localization]]<br /> <br /> &lt;!--<br /> (The description here uses the dummy language xy)<br /> We have agreed, that all localized content in this Wiki goes to the subfolder XY of the main Wiki URL. Notice the upper case of the subfolder name. If a page is a translation of an English page, the title in the URL is the same as the English one. Example: The URL of the translation of the page http://wiki.openoffice.org/wiki/Pootle_User_Guide has to be http://wiki.openoffice.org/wiki/XY/Pootle_User_Guide in the language xy.<br /> To connect the orignal and translated page insert the line<br /> [[xy:XY/Pootle_User_Guide]]<br /> at the bottom of the original page, ordered alphabetically by the namespace. Of cause use instead of Pootle_User_Guide the real page title. If your native language community has decided to use another structure under XY, you should ask the community members before you start translation.<br /> To get all the structure and formatting from the original page, open it in edit mode and copy the whole content to your new page, then cancel editing of the original page.<br /> --&gt;<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=DE/Pootle_User_Guide&diff=230513 2013-08-28T18:38:41Z

<p>Regina: Erste Schritte für die Übersetzung nach Deutsch</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle Handuch]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Anmelden und Einloggen]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Überblick Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Übersetzung]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Release einer deutschen Version]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technische Hilfsmittel]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Übersetzung der Benutzeroberfläche]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Übersetzung der eingebauten Hilfe]]<br /> *[[Pootle_User_Guide/General_Problems|Allgemeine Probleme]]<br /> }}<br /> &lt;!-- Die MasterTOC muss angepasst werden, sobald die einzelnen Seiten übersetzt sind. Bitte diese Unterseiten aber erst dann anlegen, wenn der Aufbau des englischen Originals stabil ist.--&gt;<br /> <br /> {{DISPLAYTITLE:Pootle Handbuch}}<br /> __NOTOC__<br /> <br /> [http://www.apache.org/| The Apache Software Foundation] runs a Pootle Translate service to allow its projects an easy, cooperative way to localize their products. This guide describes how to use Pootle in the Apache OpenOffice project. As of August 2013, already 40 languages (out of the 120+ languages OpenOffice supports) are maintained in Pootle and more coming soon.<br /> <br /> For an introduction to the localization process read http://openoffice.apache.org/translate.html and for a more general overview start at http://openoffice.apache.org/get-involved.html.<br /> <br /> ;[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]: The chapter describes how to become a Translator.<br /> ;[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]: The chapter introduces you to the elements in the user interface of Pootle. <br /> ;[[Pootle_User_Guide/Offline_Translation|Offline Translation]]: The chapter explains how to translate offline.<br /> ;[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]: The chapter provides tips to ensure a high quality of the translation.<br /> ;[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]: The chapter describes the steps needed to provide a localized version of Apache OpenOffice.<br /> ;[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]: The chapter shows you helpers for the process of translation.<br /> ;[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]: The chapter lists tips and tricks for translating the user interface of Apache OpenOffice.<br /> ;[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]: The chapter lists tips and tricks for translating the built-in help of Apache OpenOffice.<br /> ;[[Pootle_User_Guide/General_Problems|General Problems]]: The chapter gives you assistance in general problems, which might occur during the translating process.<br /> <br /> [[Category:Localization]]<br /> <br /> &lt;!--<br /> (The description here uses the dummy language xy)<br /> We have agreed, that all localized content in this Wiki goes to the subfolder XY of the main Wiki URL. Notice the upper case of the subfolder name. If a page is a translation of an English page, the title in the URL is the same as the English one. Example: The URL of the translation of the page http://wiki.openoffice.org/wiki/Pootle_User_Guide has to be http://wiki.openoffice.org/wiki/XY/Pootle_User_Guide in the language xy.<br /> To connect the orignal and translated page insert the line<br /> [[xy:XY/Pootle_User_Guide]]<br /> at the bottom of the original page, ordered alphabetically by the namespace. Of cause use instead of Pootle_User_Guide the real page title. If your native language community has decided to use another structure under XY, you should ask the community members before you start translation.<br /> To get all the structure and formatting from the original page, open it in edit mode and copy the whole content to your new page, then cancel editing of the original page.<br /> --&gt;<br /> <br /> [[en:Pootle_User_Guide]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230512 2013-08-28T17:13:55Z

<p>Regina: /* Placeholders */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> <br /> ==Basics about the Built-in Help Format==<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example File: helpcontent2/source/text/swriter/guide.po, Location: words_count.xhp#par_id3149821.5.help.text, <br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ==Line Breaks and Whitespace==<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ==Strings Used in the Index of the Help==<br /> <br /> Look at the example File:helpcontent2/source/text/swriter/guide.po, Locations: words_count.xhp#bm_id3149686.help.text, [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> <br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> <br /> ==Embedded Content==<br /> The help format allows to embed content from one help file into another. When you read text in the help window, you will not notice this. Use the help manipulation described in the section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]] to make such embedding visible.<br /> [[File:PootleGuide_EmbeddedVariable.png|800px|none]]<br /> <br /> Embedding is done by the elements &lt;tt&gt;embed&lt;/tt&gt; and &lt;tt&gt;embedvar&lt;/tt&gt;, for example &lt;code&gt;&lt;embedvar href=&quot;text/shared/guide/paintbrush.xhp#formatpaintbrush&quot;/&gt;&lt;/code&gt;. Such elements refer to a paragraph, section or variable in another file by the filename and the id value of the referenced part, &lt;tt&gt;formatpaintbrush&lt;/tt&gt; in the example. The id is shown in the manipulated help, so that you can search for it in Pootle by searching for &lt;tt&gt;id=&quot;&#039;&#039;an id&#039;&#039;&quot;&lt;/tt&gt; in the source text. For example search for &lt;tt&gt;id=&quot;formatpaintbrush&quot;&lt;/tt&gt; to find the origin of the above mentioned embedded text fragment.<br /> [[File:PootleGuide_SearchById.png|800px|none]]<br /> <br /> ==Images==<br /> [[File:PootleGuide_ImageTag.png|600px|none]]<br /> Images are included by an &lt;tt&gt;image&lt;/tt&gt; element. Inside of it you see an &lt;tt&gt;alt&lt;/tt&gt; child element. It specifies an alternative text for the image. At a first glance it is confusing. But look at the colors in the source text. In the example you see, that only the word &lt;tt&gt;Icon&lt;/tt&gt; has to be translated.<br /> <br /> The image element may have a &lt;tt&gt;caption&lt;/tt&gt; child element, but that is currently not used.<br /> <br /> ==Extended Tooltips==<br /> The text for the [[../Technical_Helpers#Extended_Tips| extended tips]] are stored in the built-in help and therefore their text is in the project Apache OpenOffice 4.x Help although the text is shown in the UI.<br /> <br /> [[File:PootleGuide_ahelp.png|600px|none]]<br /> <br /> Extended tips are provided by an &lt;tt&gt;ahelp&lt;/tt&gt; element. It has a &lt;tt&gt;hid&lt;/tt&gt; attribute to specify the &#039;&#039;help identifier&#039;&#039;, which connects the text to the UI element.<br /> <br /> If you have set the environment variable &lt;tt&gt;HELP_DEBUG=true&lt;/tt&gt;, you see the extended tip itself in the upper part and the help identifier in the lower part of the tip.<br /> <br /> If you know the help identifier of an UI element, you can search for the related text in Pootle. But in contrast to the project Apache OpenOffice 4.x you do not search in &#039;&#039;location&#039;&#039; but in &#039;&#039;source text&#039;&#039;.<br /> <br /> Unfortunately, if the attribute is &lt;tt&gt;hid=&quot;.&quot;&lt;/tt&gt;, the help identifier is given earlier in the help file, in a branch attribute of a bookmark element for example. And such bookmark element has no content to translate and therefore no entry in the Pootle database.<br /> <br /> Example: Edit a chart and call the context menu. It has the item &#039;&#039;Data Ranges&#039;&#039;. The extended tooltip shows &lt;tt&gt;Opens the Data Ranges dialog where you can edit Data Range and Data Series.&lt;/tt&gt; and the help identifier &lt;tt&gt;uno.DataRanges&lt;/tt&gt;. Imagine the text has an error and you need to find the string in Pootle to correct it. Your search for &#039;&#039;DataRanges&#039;&#039; gets no result.<br /> <br /> In such cases you should search for the extended tip itself. If you use not only a single word but a longer part of the tip, the number of search results will be small.<br /> <br /> Sometimes the attribute &lt;code&gt;visibility=&quot;hidden&quot;&lt;/code&gt; is used. Translate the content nevertheless. The value &quot;hidden&quot; causes, that the text is only shown as extended tooltip and not in the help window.<br /> <br /> ==Switches==<br /> Switches are used to show only one of several alternative strings in the help window. Which content is shown is determined at runtime based on a condition. The &lt;tt&gt;switch&lt;/tt&gt; element chooses a paragraph or section, the &lt;tt&gt;switchinline&lt;/tt&gt; element chooses a fragment inside a paragraph.<br /> <br /> The type of condition is given by a &lt;tt&gt;select&lt;/tt&gt; attribute. Possible values are:<br /> ;sys: Operating system. Runtime conditions are WIN UNIX MAC<br /> ;appl: Application. Runtime conditions are WRITER CALC DRAW IMPRESS MATH BASIC CHART<br /> ;distrib, target, lang, ver: These conditions are currently not used.<br /> <br /> The different contents are given in case or caseinline elements. They have a select attribute too. It has one of the possible runtime condition as value. The default or defaultinline element is used, when the current runtime condition does not fulfill any of the other case or caseinline elements.<br /> <br /> In a usual help window you see only those texts, where the condition is fulfilled by your current runtime environment.<br /> [[File:PootleGuide_selectSysMAC.png|600px|none]]<br /> <br /> On a Windows or Linux system the user sees &lt;tt&gt;hold down Ctrl and&lt;/tt&gt;, on a MAC system the user sees &lt;tt&gt;hold down Command and&lt;/tt&gt;.<br /> <br /> [[File:PootleGuilde_switchSysWINUNIX.png|600px|none]]<br /> <br /> The user on a Windows system sees &lt;tt&gt;The scanner must support the TWAIN standard.&lt;/tt&gt; The user on a Linux system sees &lt;tt&gt;The scanner must support the SANE standard.&lt;/tt&gt; The user on a MAC system sees nothing.<br /> <br /> [[File:PootleGuide_SwitchAppImpressDefault.png|600px|none]]<br /> Calling the help from Impress the user sees &lt;tt&gt;Rename Slide&lt;/tt&gt;, calling it from Draw or another application but Impress the user sees &lt;tt&gt;Rename Page&lt;/tt&gt;.<br /> <br /> Being a translators you likely want to see each possible text in the help window. For that purpose you have to manipulate your installation as described in section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]].<br /> <br /> ==Links==<br /> [[File:PootleGuide_LinkWithoutNameAttribute.png|600px|none]]<br /> The &lt;tt&gt;link&lt;/tt&gt; element creates a hyperlink, similar to those known from webpages. The target URL is given in the &lt;tt&gt;href&lt;/tt&gt; attribute. The content of the link element provides the visible text of the link.<br /> <br /> [[File:PootleGuide LinkWithNameAttribute.png|600px|none]]<br /> According to the specification, a link element should have a &lt;tt&gt;name&lt;/tt&gt; attribute to fulfill accessibility requirements. And in contrast to all other elements, the value of the name attribute has to be translated, although it is inside the opening tag.<br /> <br /> ==Items==<br /> [[File:PootleGuide_itemTypeLiteral.png|600px|none]]<br /> The &lt;tt&gt;item&lt;/tt&gt; element is used to characterize a part of the text. It is mostly used to provide a unique formatting for a class of objects. The class itself is given in the &lt;tt&gt;type&lt;/tt&gt; attribute. For translators the case &lt;code&gt;type=&quot;literal&quot;&lt;/code&gt; is relevant. It indicates, that the content should perhaps not be translated, for example because it is a book title or a Basic statement. In other cases it may be translated, for example for localized function names in Calc. So you have to examine the content carefully to decide whether a translation is needed.<br /> <br /> ==Placeholders==<br /> [[File:PootleGuide_Placeholder.png|600px|none]]<br /> The help contains some placeholders. You will see current placeholders &lt;code&gt;&lt;nowiki&gt;%PRODUCTNAME&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;%PRODUCTVERSION&lt;/nowiki&gt;&lt;/code&gt;, and the deprecated placeholders &lt;code&gt;&lt;nowiki&gt;$[officename]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;$[officeversion]&lt;/nowiki&gt;&lt;/code&gt;. When the help is displayed at runtime, the &#039;&#039;Main Transformation Style Sheet&#039;&#039; &lt;tt&gt;main_transform.xsl&lt;/tt&gt; replaces the placeholder with the information from the configuration file.<br /> <br /> Do not translate placeholders, but transfer them unchanged. Do not use the product name directly but always a placeholder. Otherwise the help will be wrong for different branding.<br /> <br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_Placeholder.png&diff=230511 2013-08-28T17:12:03Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230510 2013-08-28T17:09:33Z

<p>Regina: /* Items */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> <br /> ==Basics about the Built-in Help Format==<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example File: helpcontent2/source/text/swriter/guide.po, Location: words_count.xhp#par_id3149821.5.help.text, <br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ==Line Breaks and Whitespace==<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ==Strings Used in the Index of the Help==<br /> <br /> Look at the example File:helpcontent2/source/text/swriter/guide.po, Locations: words_count.xhp#bm_id3149686.help.text, [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> <br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> <br /> ==Embedded Content==<br /> The help format allows to embed content from one help file into another. When you read text in the help window, you will not notice this. Use the help manipulation described in the section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]] to make such embedding visible.<br /> [[File:PootleGuide_EmbeddedVariable.png|800px|none]]<br /> <br /> Embedding is done by the elements &lt;tt&gt;embed&lt;/tt&gt; and &lt;tt&gt;embedvar&lt;/tt&gt;, for example &lt;code&gt;&lt;embedvar href=&quot;text/shared/guide/paintbrush.xhp#formatpaintbrush&quot;/&gt;&lt;/code&gt;. Such elements refer to a paragraph, section or variable in another file by the filename and the id value of the referenced part, &lt;tt&gt;formatpaintbrush&lt;/tt&gt; in the example. The id is shown in the manipulated help, so that you can search for it in Pootle by searching for &lt;tt&gt;id=&quot;&#039;&#039;an id&#039;&#039;&quot;&lt;/tt&gt; in the source text. For example search for &lt;tt&gt;id=&quot;formatpaintbrush&quot;&lt;/tt&gt; to find the origin of the above mentioned embedded text fragment.<br /> [[File:PootleGuide_SearchById.png|800px|none]]<br /> <br /> ==Images==<br /> [[File:PootleGuide_ImageTag.png|600px|none]]<br /> Images are included by an &lt;tt&gt;image&lt;/tt&gt; element. Inside of it you see an &lt;tt&gt;alt&lt;/tt&gt; child element. It specifies an alternative text for the image. At a first glance it is confusing. But look at the colors in the source text. In the example you see, that only the word &lt;tt&gt;Icon&lt;/tt&gt; has to be translated.<br /> <br /> The image element may have a &lt;tt&gt;caption&lt;/tt&gt; child element, but that is currently not used.<br /> <br /> ==Extended Tooltips==<br /> The text for the [[../Technical_Helpers#Extended_Tips| extended tips]] are stored in the built-in help and therefore their text is in the project Apache OpenOffice 4.x Help although the text is shown in the UI.<br /> <br /> [[File:PootleGuide_ahelp.png|600px|none]]<br /> <br /> Extended tips are provided by an &lt;tt&gt;ahelp&lt;/tt&gt; element. It has a &lt;tt&gt;hid&lt;/tt&gt; attribute to specify the &#039;&#039;help identifier&#039;&#039;, which connects the text to the UI element.<br /> <br /> If you have set the environment variable &lt;tt&gt;HELP_DEBUG=true&lt;/tt&gt;, you see the extended tip itself in the upper part and the help identifier in the lower part of the tip.<br /> <br /> If you know the help identifier of an UI element, you can search for the related text in Pootle. But in contrast to the project Apache OpenOffice 4.x you do not search in &#039;&#039;location&#039;&#039; but in &#039;&#039;source text&#039;&#039;.<br /> <br /> Unfortunately, if the attribute is &lt;tt&gt;hid=&quot;.&quot;&lt;/tt&gt;, the help identifier is given earlier in the help file, in a branch attribute of a bookmark element for example. And such bookmark element has no content to translate and therefore no entry in the Pootle database.<br /> <br /> Example: Edit a chart and call the context menu. It has the item &#039;&#039;Data Ranges&#039;&#039;. The extended tooltip shows &lt;tt&gt;Opens the Data Ranges dialog where you can edit Data Range and Data Series.&lt;/tt&gt; and the help identifier &lt;tt&gt;uno.DataRanges&lt;/tt&gt;. Imagine the text has an error and you need to find the string in Pootle to correct it. Your search for &#039;&#039;DataRanges&#039;&#039; gets no result.<br /> <br /> In such cases you should search for the extended tip itself. If you use not only a single word but a longer part of the tip, the number of search results will be small.<br /> <br /> Sometimes the attribute &lt;code&gt;visibility=&quot;hidden&quot;&lt;/code&gt; is used. Translate the content nevertheless. The value &quot;hidden&quot; causes, that the text is only shown as extended tooltip and not in the help window.<br /> <br /> ==Switches==<br /> Switches are used to show only one of several alternative strings in the help window. Which content is shown is determined at runtime based on a condition. The &lt;tt&gt;switch&lt;/tt&gt; element chooses a paragraph or section, the &lt;tt&gt;switchinline&lt;/tt&gt; element chooses a fragment inside a paragraph.<br /> <br /> The type of condition is given by a &lt;tt&gt;select&lt;/tt&gt; attribute. Possible values are:<br /> ;sys: Operating system. Runtime conditions are WIN UNIX MAC<br /> ;appl: Application. Runtime conditions are WRITER CALC DRAW IMPRESS MATH BASIC CHART<br /> ;distrib, target, lang, ver: These conditions are currently not used.<br /> <br /> The different contents are given in case or caseinline elements. They have a select attribute too. It has one of the possible runtime condition as value. The default or defaultinline element is used, when the current runtime condition does not fulfill any of the other case or caseinline elements.<br /> <br /> In a usual help window you see only those texts, where the condition is fulfilled by your current runtime environment.<br /> [[File:PootleGuide_selectSysMAC.png|600px|none]]<br /> <br /> On a Windows or Linux system the user sees &lt;tt&gt;hold down Ctrl and&lt;/tt&gt;, on a MAC system the user sees &lt;tt&gt;hold down Command and&lt;/tt&gt;.<br /> <br /> [[File:PootleGuilde_switchSysWINUNIX.png|600px|none]]<br /> <br /> The user on a Windows system sees &lt;tt&gt;The scanner must support the TWAIN standard.&lt;/tt&gt; The user on a Linux system sees &lt;tt&gt;The scanner must support the SANE standard.&lt;/tt&gt; The user on a MAC system sees nothing.<br /> <br /> [[File:PootleGuide_SwitchAppImpressDefault.png|600px|none]]<br /> Calling the help from Impress the user sees &lt;tt&gt;Rename Slide&lt;/tt&gt;, calling it from Draw or another application but Impress the user sees &lt;tt&gt;Rename Page&lt;/tt&gt;.<br /> <br /> Being a translators you likely want to see each possible text in the help window. For that purpose you have to manipulate your installation as described in section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]].<br /> <br /> ==Links==<br /> [[File:PootleGuide_LinkWithoutNameAttribute.png|600px|none]]<br /> The &lt;tt&gt;link&lt;/tt&gt; element creates a hyperlink, similar to those known from webpages. The target URL is given in the &lt;tt&gt;href&lt;/tt&gt; attribute. The content of the link element provides the visible text of the link.<br /> <br /> [[File:PootleGuide LinkWithNameAttribute.png|600px|none]]<br /> According to the specification, a link element should have a &lt;tt&gt;name&lt;/tt&gt; attribute to fulfill accessibility requirements. And in contrast to all other elements, the value of the name attribute has to be translated, although it is inside the opening tag.<br /> <br /> ==Items==<br /> [[File:PootleGuide_itemTypeLiteral.png|600px|none]]<br /> The &lt;tt&gt;item&lt;/tt&gt; element is used to characterize a part of the text. It is mostly used to provide a unique formatting for a class of objects. The class itself is given in the &lt;tt&gt;type&lt;/tt&gt; attribute. For translators the case &lt;code&gt;type=&quot;literal&quot;&lt;/code&gt; is relevant. It indicates, that the content should perhaps not be translated, for example because it is a book title or a Basic statement. In other cases it may be translated, for example for localized function names in Calc. So you have to examine the content carefully to decide whether a translation is needed.<br /> <br /> ==Placeholders==<br /> The help contains some placeholders. You will see current placeholders &lt;code&gt;&lt;nowiki&gt;%PRODUCTNAME&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;%PRODUCTVERSION&lt;/nowiki&gt;&lt;/code&gt;, and the deprecated placeholders &lt;code&gt;&lt;nowiki&gt;$[officename]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;$[officeversion]&lt;/nowiki&gt;&lt;/code&gt;. When the help is displayed at runtime, the &#039;&#039;Main Transformation Style Sheet&#039;&#039; &lt;tt&gt;main_transform.xsl&lt;/tt&gt; replaces the placeholder with the information from the configuration file.<br /> <br /> Do not translate placeholders, but transfer them unchanged. Do not use the product name directly but always a placeholder. Otherwise the help will be wrong for different brandings.<br /> <br /> <br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_itemTypeLiteral.png&diff=230509 2013-08-28T17:06:20Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230508 2013-08-28T16:56:21Z

<p>Regina: /* Switches */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> <br /> ==Basics about the Built-in Help Format==<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example File: helpcontent2/source/text/swriter/guide.po, Location: words_count.xhp#par_id3149821.5.help.text, <br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ==Line Breaks and Whitespace==<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ==Strings Used in the Index of the Help==<br /> <br /> Look at the example File:helpcontent2/source/text/swriter/guide.po, Locations: words_count.xhp#bm_id3149686.help.text, [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> <br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> <br /> ==Embedded Content==<br /> The help format allows to embed content from one help file into another. When you read text in the help window, you will not notice this. Use the help manipulation described in the section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]] to make such embedding visible.<br /> [[File:PootleGuide_EmbeddedVariable.png|800px|none]]<br /> <br /> Embedding is done by the elements &lt;tt&gt;embed&lt;/tt&gt; and &lt;tt&gt;embedvar&lt;/tt&gt;, for example &lt;code&gt;&lt;embedvar href=&quot;text/shared/guide/paintbrush.xhp#formatpaintbrush&quot;/&gt;&lt;/code&gt;. Such elements refer to a paragraph, section or variable in another file by the filename and the id value of the referenced part, &lt;tt&gt;formatpaintbrush&lt;/tt&gt; in the example. The id is shown in the manipulated help, so that you can search for it in Pootle by searching for &lt;tt&gt;id=&quot;&#039;&#039;an id&#039;&#039;&quot;&lt;/tt&gt; in the source text. For example search for &lt;tt&gt;id=&quot;formatpaintbrush&quot;&lt;/tt&gt; to find the origin of the above mentioned embedded text fragment.<br /> [[File:PootleGuide_SearchById.png|800px|none]]<br /> <br /> ==Images==<br /> [[File:PootleGuide_ImageTag.png|600px|none]]<br /> Images are included by an &lt;tt&gt;image&lt;/tt&gt; element. Inside of it you see an &lt;tt&gt;alt&lt;/tt&gt; child element. It specifies an alternative text for the image. At a first glance it is confusing. But look at the colors in the source text. In the example you see, that only the word &lt;tt&gt;Icon&lt;/tt&gt; has to be translated.<br /> <br /> The image element may have a &lt;tt&gt;caption&lt;/tt&gt; child element, but that is currently not used.<br /> <br /> ==Extended Tooltips==<br /> The text for the [[../Technical_Helpers#Extended_Tips| extended tips]] are stored in the built-in help and therefore their text is in the project Apache OpenOffice 4.x Help although the text is shown in the UI.<br /> <br /> [[File:PootleGuide_ahelp.png|600px|none]]<br /> <br /> Extended tips are provided by an &lt;tt&gt;ahelp&lt;/tt&gt; element. It has a &lt;tt&gt;hid&lt;/tt&gt; attribute to specify the &#039;&#039;help identifier&#039;&#039;, which connects the text to the UI element.<br /> <br /> If you have set the environment variable &lt;tt&gt;HELP_DEBUG=true&lt;/tt&gt;, you see the extended tip itself in the upper part and the help identifier in the lower part of the tip.<br /> <br /> If you know the help identifier of an UI element, you can search for the related text in Pootle. But in contrast to the project Apache OpenOffice 4.x you do not search in &#039;&#039;location&#039;&#039; but in &#039;&#039;source text&#039;&#039;.<br /> <br /> Unfortunately, if the attribute is &lt;tt&gt;hid=&quot;.&quot;&lt;/tt&gt;, the help identifier is given earlier in the help file, in a branch attribute of a bookmark element for example. And such bookmark element has no content to translate and therefore no entry in the Pootle database.<br /> <br /> Example: Edit a chart and call the context menu. It has the item &#039;&#039;Data Ranges&#039;&#039;. The extended tooltip shows &lt;tt&gt;Opens the Data Ranges dialog where you can edit Data Range and Data Series.&lt;/tt&gt; and the help identifier &lt;tt&gt;uno.DataRanges&lt;/tt&gt;. Imagine the text has an error and you need to find the string in Pootle to correct it. Your search for &#039;&#039;DataRanges&#039;&#039; gets no result.<br /> <br /> In such cases you should search for the extended tip itself. If you use not only a single word but a longer part of the tip, the number of search results will be small.<br /> <br /> Sometimes the attribute &lt;code&gt;visibility=&quot;hidden&quot;&lt;/code&gt; is used. Translate the content nevertheless. The value &quot;hidden&quot; causes, that the text is only shown as extended tooltip and not in the help window.<br /> <br /> ==Switches==<br /> Switches are used to show only one of several alternative strings in the help window. Which content is shown is determined at runtime based on a condition. The &lt;tt&gt;switch&lt;/tt&gt; element chooses a paragraph or section, the &lt;tt&gt;switchinline&lt;/tt&gt; element chooses a fragment inside a paragraph.<br /> <br /> The type of condition is given by a &lt;tt&gt;select&lt;/tt&gt; attribute. Possible values are:<br /> ;sys: Operating system. Runtime conditions are WIN UNIX MAC<br /> ;appl: Application. Runtime conditions are WRITER CALC DRAW IMPRESS MATH BASIC CHART<br /> ;distrib, target, lang, ver: These conditions are currently not used.<br /> <br /> The different contents are given in case or caseinline elements. They have a select attribute too. It has one of the possible runtime condition as value. The default or defaultinline element is used, when the current runtime condition does not fulfill any of the other case or caseinline elements.<br /> <br /> In a usual help window you see only those texts, where the condition is fulfilled by your current runtime environment.<br /> [[File:PootleGuide_selectSysMAC.png|600px|none]]<br /> <br /> On a Windows or Linux system the user sees &lt;tt&gt;hold down Ctrl and&lt;/tt&gt;, on a MAC system the user sees &lt;tt&gt;hold down Command and&lt;/tt&gt;.<br /> <br /> [[File:PootleGuilde_switchSysWINUNIX.png|600px|none]]<br /> <br /> The user on a Windows system sees &lt;tt&gt;The scanner must support the TWAIN standard.&lt;/tt&gt; The user on a Linux system sees &lt;tt&gt;The scanner must support the SANE standard.&lt;/tt&gt; The user on a MAC system sees nothing.<br /> <br /> [[File:PootleGuide_SwitchAppImpressDefault.png|600px|none]]<br /> Calling the help from Impress the user sees &lt;tt&gt;Rename Slide&lt;/tt&gt;, calling it from Draw or another application but Impress the user sees &lt;tt&gt;Rename Page&lt;/tt&gt;.<br /> <br /> Being a translators you likely want to see each possible text in the help window. For that purpose you have to manipulate your installation as described in section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]].<br /> <br /> ==Links==<br /> [[File:PootleGuide_LinkWithoutNameAttribute.png|600px|none]]<br /> The &lt;tt&gt;link&lt;/tt&gt; element creates a hyperlink, similar to those known from webpages. The target URL is given in the &lt;tt&gt;href&lt;/tt&gt; attribute. The content of the link element provides the visible text of the link.<br /> <br /> [[File:PootleGuide LinkWithNameAttribute.png|600px|none]]<br /> According to the specification, a link element should have a &lt;tt&gt;name&lt;/tt&gt; attribute to fulfill accessibility requirements. And in contrast to all other elements, the value of the name attribute has to be translated, although it is inside the opening tag.<br /> <br /> ==Items==<br /> [[]]<br /> The &lt;tt&gt;item&lt;/tt&gt; element is used to characterize a part of the text. It is mostly used to provide a unique formatting for a class of objects. The class itself is given in the &lt;tt&gt;type&lt;/tt&gt; attribute. For translators the type=&quot;literal&quot; is relevant. It indicates, that the content should perhaps not be translated, for example because it is a book title or a Basic statement. In other cases it can be translated, for example for localized function names in Calc. So you have to examine the content carefully to decide whether a translation is needed.<br /> <br /> ==Placeholders==<br /> The help contains some placeholders. You will see current placeholders &lt;code&gt;&lt;nowiki&gt;%PRODUCTNAME&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;%PRODUCTVERSION&lt;/nowiki&gt;&lt;/code&gt;, and the deprecated placeholders &lt;code&gt;&lt;nowiki&gt;$[officename]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;$[officeversion]&lt;/nowiki&gt;&lt;/code&gt;. When the help is displayed at runtime, the &#039;&#039;Main Transformation Style Sheet&#039;&#039; &lt;tt&gt;main_transform.xsl&lt;/tt&gt; replaces the placeholder with the information from the configuration file.<br /> <br /> Do not translate placeholders, but transfer them unchanged. Do not use the product name directly but always a placeholder. Otherwise the help will be wrong for different brandings.<br /> <br /> <br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230507 2013-08-28T16:53:02Z

<p>Regina: /* Embedded Content */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> <br /> ==Basics about the Built-in Help Format==<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example File: helpcontent2/source/text/swriter/guide.po, Location: words_count.xhp#par_id3149821.5.help.text, <br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ==Line Breaks and Whitespace==<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ==Strings Used in the Index of the Help==<br /> <br /> Look at the example File:helpcontent2/source/text/swriter/guide.po, Locations: words_count.xhp#bm_id3149686.help.text, [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> <br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> <br /> ==Embedded Content==<br /> The help format allows to embed content from one help file into another. When you read text in the help window, you will not notice this. Use the help manipulation described in the section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]] to make such embedding visible.<br /> [[File:PootleGuide_EmbeddedVariable.png|800px|none]]<br /> <br /> Embedding is done by the elements &lt;tt&gt;embed&lt;/tt&gt; and &lt;tt&gt;embedvar&lt;/tt&gt;, for example &lt;code&gt;&lt;embedvar href=&quot;text/shared/guide/paintbrush.xhp#formatpaintbrush&quot;/&gt;&lt;/code&gt;. Such elements refer to a paragraph, section or variable in another file by the filename and the id value of the referenced part, &lt;tt&gt;formatpaintbrush&lt;/tt&gt; in the example. The id is shown in the manipulated help, so that you can search for it in Pootle by searching for &lt;tt&gt;id=&quot;&#039;&#039;an id&#039;&#039;&quot;&lt;/tt&gt; in the source text. For example search for &lt;tt&gt;id=&quot;formatpaintbrush&quot;&lt;/tt&gt; to find the origin of the above mentioned embedded text fragment.<br /> [[File:PootleGuide_SearchById.png|800px|none]]<br /> <br /> ==Images==<br /> [[File:PootleGuide_ImageTag.png|600px|none]]<br /> Images are included by an &lt;tt&gt;image&lt;/tt&gt; element. Inside of it you see an &lt;tt&gt;alt&lt;/tt&gt; child element. It specifies an alternative text for the image. At a first glance it is confusing. But look at the colors in the source text. In the example you see, that only the word &lt;tt&gt;Icon&lt;/tt&gt; has to be translated.<br /> <br /> The image element may have a &lt;tt&gt;caption&lt;/tt&gt; child element, but that is currently not used.<br /> <br /> ==Extended Tooltips==<br /> The text for the [[../Technical_Helpers#Extended_Tips| extended tips]] are stored in the built-in help and therefore their text is in the project Apache OpenOffice 4.x Help although the text is shown in the UI.<br /> <br /> [[File:PootleGuide_ahelp.png|600px|none]]<br /> <br /> Extended tips are provided by an &lt;tt&gt;ahelp&lt;/tt&gt; element. It has a &lt;tt&gt;hid&lt;/tt&gt; attribute to specify the &#039;&#039;help identifier&#039;&#039;, which connects the text to the UI element.<br /> <br /> If you have set the environment variable &lt;tt&gt;HELP_DEBUG=true&lt;/tt&gt;, you see the extended tip itself in the upper part and the help identifier in the lower part of the tip.<br /> <br /> If you know the help identifier of an UI element, you can search for the related text in Pootle. But in contrast to the project Apache OpenOffice 4.x you do not search in &#039;&#039;location&#039;&#039; but in &#039;&#039;source text&#039;&#039;.<br /> <br /> Unfortunately, if the attribute is &lt;tt&gt;hid=&quot;.&quot;&lt;/tt&gt;, the help identifier is given earlier in the help file, in a branch attribute of a bookmark element for example. And such bookmark element has no content to translate and therefore no entry in the Pootle database.<br /> <br /> Example: Edit a chart and call the context menu. It has the item &#039;&#039;Data Ranges&#039;&#039;. The extended tooltip shows &lt;tt&gt;Opens the Data Ranges dialog where you can edit Data Range and Data Series.&lt;/tt&gt; and the help identifier &lt;tt&gt;uno.DataRanges&lt;/tt&gt;. Imagine the text has an error and you need to find the string in Pootle to correct it. Your search for &#039;&#039;DataRanges&#039;&#039; gets no result.<br /> <br /> In such cases you should search for the extended tip itself. If you use not only a single word but a longer part of the tip, the number of search results will be small.<br /> <br /> Sometimes the attribute &lt;code&gt;visibility=&quot;hidden&quot;&lt;/code&gt; is used. Translate the content nevertheless. The value &quot;hidden&quot; causes, that the text is only shown as extended tooltip and not in the help window.<br /> <br /> ==Switches==<br /> Switches are used to show only one of several alternative strings in the help window. Which content is shown is determined at runtime based on a condition. The &lt;tt&gt;switch&lt;/tt&gt; element chooses a paragraph or section, the &lt;tt&gt;switchinline&lt;/tt&gt; element chooses a fragment inside a paragraph.<br /> <br /> The type of condition is given by a &lt;tt&gt;select&lt;/tt&gt; attribute. Possible values are:<br /> ;sys: Operating system. Runtime conditions are WIN UNIX MAC<br /> ;appl: Application. Runtime conditions are WRITER CALC DRAW IMPRESS MATH BASIC CHART<br /> ;distrib, target, lang, ver: These conditions are currently not used.<br /> <br /> The different contents are given in case or caseinline elements. They have a select attribute too. It has one of the possible runtime condition as value. The default or defaultinline element is used, when the current runtime condition does not fulfill any of the other case or caseinline elements.<br /> <br /> In a usual help window you see only those texts, where the condition is fulfilled by your current runtime environment.<br /> [[File:PootleGuide_selectSysMAC.png|600px|none]]<br /> <br /> On a Windows or Linux system the user sees &lt;tt&gt;hold down Ctrl and&lt;/tt&gt;, on a MAC system the user sees &lt;tt&gt;hold down Command and&lt;/tt&gt;.<br /> <br /> [[File:PootleGuilde_switchSysWINUNIX.png|600px|none]]<br /> <br /> The user on a Windows system sees &lt;tt&gt;The scanner must support the TWAIN standard.&lt;/tt&gt; The user on a Linux system sees &lt;tt&gt;The scanner must support the SANE standard.&lt;/tt&gt; The user on a MAC system sees nothing.<br /> <br /> [[File:PootleGuide_SwitchAppImpressDefault.png|600px|none]]<br /> Calling the help from Impress the user sees &lt;tt&gt;Rename Slide&lt;/tt&gt;, calling it from Draw or another application but Impress the user sees&lt;tt&gt;Rename Page&lt;/tt&gt;.<br /> <br /> Being a translators you likely want to see each possible text. For that purpose you have to manipulate your installation as discribed in section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]].<br /> <br /> <br /> ==Links==<br /> [[File:PootleGuide_LinkWithoutNameAttribute.png|600px|none]]<br /> The &lt;tt&gt;link&lt;/tt&gt; element creates a hyperlink, similar to those known from webpages. The target URL is given in the &lt;tt&gt;href&lt;/tt&gt; attribute. The content of the link element provides the visible text of the link.<br /> <br /> [[File:PootleGuide LinkWithNameAttribute.png|600px|none]]<br /> According to the specification, a link element should have a &lt;tt&gt;name&lt;/tt&gt; attribute to fulfill accessibility requirements. And in contrast to all other elements, the value of the name attribute has to be translated, although it is inside the opening tag.<br /> <br /> ==Items==<br /> [[]]<br /> The &lt;tt&gt;item&lt;/tt&gt; element is used to characterize a part of the text. It is mostly used to provide a unique formatting for a class of objects. The class itself is given in the &lt;tt&gt;type&lt;/tt&gt; attribute. For translators the type=&quot;literal&quot; is relevant. It indicates, that the content should perhaps not be translated, for example because it is a book title or a Basic statement. In other cases it can be translated, for example for localized function names in Calc. So you have to examine the content carefully to decide whether a translation is needed.<br /> <br /> ==Placeholders==<br /> The help contains some placeholders. You will see current placeholders &lt;code&gt;&lt;nowiki&gt;%PRODUCTNAME&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;%PRODUCTVERSION&lt;/nowiki&gt;&lt;/code&gt;, and the deprecated placeholders &lt;code&gt;&lt;nowiki&gt;$[officename]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;$[officeversion]&lt;/nowiki&gt;&lt;/code&gt;. When the help is displayed at runtime, the &#039;&#039;Main Transformation Style Sheet&#039;&#039; &lt;tt&gt;main_transform.xsl&lt;/tt&gt; replaces the placeholder with the information from the configuration file.<br /> <br /> Do not translate placeholders, but transfer them unchanged. Do not use the product name directly but always a placeholder. Otherwise the help will be wrong for different brandings.<br /> <br /> <br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_SearchById.png&diff=230506 2013-08-28T16:50:19Z

<p>Regina: Regina uploaded a new version of &amp;quot;File:PootleGuide SearchById.png&amp;quot;: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_SearchById.png&diff=230505 2013-08-28T16:45:55Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_EmbeddedVariable.png&diff=230504 2013-08-28T16:42:06Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Technical_Helpers&diff=230503 2013-08-28T16:32:54Z

<p>Regina: /* Transforming the Style of the Built-in Help */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Technical Helpers}}<br /> __TOC__<br /> <br /> <br /> You will find, that it is a large problem in translating to be sure what part of the UI or the built-in help is shown in the current translation record and the other way round to find a specific string from the installed application in Pootle. The following sections show you some tools.<br /> <br /> ==Using an English User Interface Parallel==<br /> Because the user interface settings in Apache OpenOffice are bound to the user and not to the installation, you can generate a second user, who has an English interface. Then you can open Apache OpenOffice at the same time with an English user interface and with the UI in your language.<br /> <br /> ==== Windows ====<br /> * Download the English language pack and install it. Or the other way round, install an English version and a language pack for your language.<br /> * Create a folder that will contain the user settings for the &quot;English&quot; user, for example &quot;D:\AOOuser_English&quot;.<br /> * Find the file soffice.exe in your installation and create a link to it on your desktop. That should be possible with right click and &quot;Sent To&quot;.<br /> * Open the link to edit it. It should has a field with the link target like &quot;C:\Program Files\OpenOffice 4\program\soffice.exe&quot;.<br /> * Klick into this field and move the cursor to outmost right position and add&lt;br /&gt;&lt;tt&gt;-env:UserInstallation=file:///d:/AOOuser_English.&lt;/tt&gt;&lt;br /&gt;Notice that here a UNC notation with forward slashes is used.<br /> * Close dialog with OK.<br /> * Start OpenOffice with double-click on this link. Goto {{Menu|Tools|Options|Language Settings|Languages}} and set the User Interface to &quot;English (USA)&quot;.<br /> <br /> Dependent on the installation order it might be necessary to change your actual user settings back to your language.<br /> <br /> ===Other Operating Systems===<br /> &#039;&#039;For other operating systems this might be slightly different. Please add necessary descriptions here.&#039;&#039;<br /> <br /> <br /> == Search in the Source Code ==<br /> Translators generally do not have a local copy of the code, but sometimes want to lookup something. These tools might help you.<br /> === Opengrok ===<br /> Example: You see the string &quot;Purple Pipe&quot; as name of a color gradient and wants to know, which files contain this string.<br /> <br /> To search the code use http://opengrok.adfinis-sygroup.org/ That is as powerful tool for developers. For translators this short instruction might be sufficient:<br /> * Select &quot;aoo-trunk&quot; on the right side.<br /> * Enter the search term in the &quot;Full Search&quot; field. The wild cards * and ? are allowed, but not as first character. A phrase has to be enclosed with quotation marks. If you enter several words, they are automatically treated as been connected by AND.<br /> * In the field &quot;File Path&quot; you can enter a part of the path or filename, for example &#039;helpcontent2&#039; for all files of the built-in help. Or you use NOT to exclude those paths, you know to be irrelevant.<br /> {|<br /> |-<br /> | [[File:PootleGuide_OpenGrok.png|400px|thumb|left]]<br /> |-<br /> |}<br /> <br /> In the example you will find that the string &quot;Purple Pipe&quot; is contained in the file &lt;tt&gt;standard.sog&lt;/tt&gt;. Click on the search result to open the file in your browser.&lt;&#039;&#039;See {{bug|122790}}, why this string is not yet (August 2013) in Pootle.&#039;&#039;&gt;<br /> <br /> === ViewVC ===<br /> This tool provides a read access to all files of Apache-SVN. The tree of the OpenOffice project starts in http://svn.apache.org/viewvc/openoffice .<br /> <br /> You will notice, that this is similar to the tree view in the page &quot;Overview&quot; in Pootle. Click on the directory name to open that folder and move down in the tree, click on &quot;Parent directory&quot; to move up.<br /> <br /> A click on a file name gives you its revision log. To view the current file in the browser, click &quot;View&quot; of the top entry; use &quot;Download&quot; to save it to your PC. To go back, up in the tree, use the navigator line at top of the page.<br /> {|<br /> |-<br /> | [[File:PootleGuide_viewvc_localizesdf.png|400px|thumb|left]]<br /> |-<br /> |}<br /> <br /> The .po files for the user interface are based on &lt;tt&gt;localize.sdf&lt;/tt&gt; files. Each language has its own file. Find these files in http://svn.apache.org/viewvc/openoffice/trunk/extras/l10n/source/. These files are about 4MB - 13MB in size. &lt;&#039;&#039;As of August 2013, there are plans to get rid of the localize.sdf files and use .po files directly. Such change was already done in LibreOffice.&#039;&#039;&gt; <br /> <br /> The .po files for the built-in help are based on .xhp files. Find these files in http://svn.apache.org/viewvc/openoffice/trunk/main/helpcontent2/source/text/<br /> <br /> == Make Your Installation Verbose ==<br /> === Extended Tips ===<br /> Set the environment variable HELP_DEBUG=true. It depends on your operating system how to do it. Find details on environment variables for Apache OpenOffice in [[Environment_Variables]].<br /> &lt;div style=&quot;margin-left:3em&quot;&gt;<br /> &#039;&#039;&#039;Tip for Linux&#039;&#039;&#039;<br /> <br /> Find the shell script &lt;tt&gt;soffice&lt;/tt&gt; in your installation of AOO and open it in an editor. Add the lines<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> HELP_DEBUG=true<br /> export HELP_DEBUG<br /> &lt;/source&gt;<br /> A good place to add them is after the already existing environment variable SAL_ENABLE_FILE_LOCKING.<br /> &lt;/div&gt;<br /> <br /> Now your extended tips in AOO look like this<br /> <br /> [[File:PootleGuilde_ExtendedTipExample.png|300px|thumb|none]]<br /> <br /> Notice there is an additional part under the --- divider. The tip shows now the helpID of the item and the internal module. You can use the last part after the colon to search for it in Pootle, here search for CBX_PREVIEW for example.<br /> <br /> Using extended tips is not enabled in the defaults. Use one of these ways to show extended tips<br /> * Enable them in {{Menu|Tools|Options|OpenOffice|General}}<br /> * In the toolbar &quot;Standard&quot; set the icon &quot;What&#039;s this?&quot; to visible. Click the icon and hover with the mouse over an UI element. Click again to leave this mode.<br /> * Customize a toolbar and add the item &quot;Extended Help&quot; to it. Find it in the category &quot;Application&quot;. This command has no icon assigned. To connect an icon to the command or change the command name to e.g. &quot;Help+&quot; click on the button &quot;Modify&quot; in the customization dialog and select the corresponding item. With this command you can easily toggle between extended tips on/off. Use a similar way to assign a shortcut key to this command.<br /> <br /> === Transforming the Style of the Built-in Help ===<br /> {{bug|56321}} &quot;Instructions on Help review&quot; provides three tools to make the structure of the build-in help visible.[[File:PootleGuide_ExchangesDefaultCSS.png|400px|right]]<br /> <br /> ; allfiles.tree: It adds an entry &quot;All Help Documents for Debug Purpose&quot; to the &quot;Content&quot; page of the build-in help. This new section shows the helpfiles not by title but by filename and in the same hierarchical order as in Pootle.<br /> ; default.css: This file colors the help texts in a way, that you can easily see, what kind of content it is. The meaning of the colors is listed at top of the help page, see screenshot at the right margin.<br /> ; main_transform.xsl: This file causes, that in the build-in help the helpIDs are shown in addition to the text. With the information about file and location from Pootle, you can now easily identify the string in the help and see its context.<br /> <br /> To transform your help do this:<br /> # Get the newest versions of the files allfiles.tree, default.css, and main_transform.xsl from {{bug|56321}}.<br /> # Close your OpenOffice including the Quickstarter.<br /> # Locate the folder &quot;help&quot; in your installation. For my Windows 7 it is the path C:\Program Files\OpenOffice 4\help. For you it should be similar.<br /> # You should see a file main_transform.xsl in this folder. Rename it to e.g. main_transform.xsl.orig and copy the corresponding file form the issue here.<br /> # You should see subfolders that are named as the language codes. Open the folder of the language, for which you will produce the translation.<br /> # You should see some files with file extension .tree. Copy the file allfiles.tree here.<br /> # Locate the file default.css in this folder and rename it to e.g. default.css.orig. Copy the corresponding file from the issue here.<br /> # Start OpenOffice and open a help page. At top of the page you will see a short explanation about the meaning of the colors and styles.<br /> <br /> &lt;&#039;&#039;Some new files are missing in allfiles.tree. But I don&#039;t know yet, whether the file has to be updated manually or a script for generating the file exists.&#039;&#039;&gt;<br /> <br /> == Getting a KeyID-Build ==<br /> &lt;&#039;&#039;ToDO: Add screenshot&#039;&#039;&gt;<br /> &lt;&#039;&#039;ToDo: Consolidate with the existing page [[KeyID_Build]].&#039;&#039;&gt;<br /> <br /> A keyID-build is a special version, where each string in the UI has got a number in front of it, the keyID. To get these numbers a pseudo language &quot;kid&quot; is used. This pseudo language has its own localize.sdf file, same as all real languages. This file contains a database table. Each row is about a UI string. It connects the strings with the identifiers used in the source.<br /> <br /> A developer gets such a keyID-build by using the configure switch, e.g. &lt;code&gt;--with-lang=&quot;de kid&quot;&lt;/code&gt;. The setting in the example would build an English AOO (the default), a German AOO, and an AOO with keyIDs. <br /> <br /> If you want to use such a keyID-build and cannot build it yourself, ask on the mailing list. There is likely someone, who can build it for you, or perhaps a build bot can be configured to deliver it.<br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_ExchangesDefaultCSS.png&diff=230502 2013-08-28T16:26:19Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230501 2013-08-28T16:13:51Z

<p>Regina: /* Irrelevant Whitespace */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> <br /> ==Basics about the Built-in Help Format==<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example File: helpcontent2/source/text/swriter/guide.po, Location: words_count.xhp#par_id3149821.5.help.text, <br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ==Line Breaks and Whitespace==<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ==Strings Used in the Index of the Help==<br /> <br /> Look at the example File:helpcontent2/source/text/swriter/guide.po, Locations: words_count.xhp#bm_id3149686.help.text, [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> <br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> <br /> ==Embedded Content==<br /> The help format allows to embed content from one help file into another. When you read text in the help window, you will not notice this. Use the help manipulation described in the section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]] to make such embedding visible.<br /> <br /> Embedding is done by the elements &lt;tt&gt;embed&lt;/tt&gt; and &lt;tt&gt;embedvar&lt;/tt&gt;, for example &lt;code&gt;&lt;embedvar href=&quot;text/shared/guide/paintbrush.xhp#formatpaintbrush&quot;/&gt;&lt;/code&gt;. Such elements refer to a paragraph, section or variable in another file by the filename and the id value of the referenced part, &lt;tt&gt;formatpaintbrush&lt;/tt&gt; in the example. The id is shown in the manipulated help, so that you can search for it in Pootle by searching for &lt;tt&gt;id=&quot;&#039;&#039;your id&#039;&#039;&quot;&lt;/tt&gt; in the source text. For example search for id=&quot;formatpaintbrush&quot; to find the origin of the above mentioned embedded text fragment.<br /> <br /> ==Images==<br /> [[File:PootleGuide_ImageTag.png|600px|none]]<br /> Images are included by an &lt;tt&gt;image&lt;/tt&gt; element. Inside of it you see an &lt;tt&gt;alt&lt;/tt&gt; child element. It specifies an alternative text for the image. At a first glance it is confusing. But look at the colors in the source text. In the example you see, that only the word &lt;tt&gt;Icon&lt;/tt&gt; has to be translated.<br /> <br /> The image element may have a &lt;tt&gt;caption&lt;/tt&gt; child element, but that is currently not used.<br /> <br /> ==Extended Tooltips==<br /> The text for the [[../Technical_Helpers#Extended_Tips| extended tips]] are stored in the built-in help and therefore their text is in the project Apache OpenOffice 4.x Help although the text is shown in the UI.<br /> <br /> [[File:PootleGuide_ahelp.png|600px|none]]<br /> <br /> Extended tips are provided by an &lt;tt&gt;ahelp&lt;/tt&gt; element. It has a &lt;tt&gt;hid&lt;/tt&gt; attribute to specify the &#039;&#039;help identifier&#039;&#039;, which connects the text to the UI element.<br /> <br /> If you have set the environment variable &lt;tt&gt;HELP_DEBUG=true&lt;/tt&gt;, you see the extended tip itself in the upper part and the help identifier in the lower part of the tip.<br /> <br /> If you know the help identifier of an UI element, you can search for the related text in Pootle. But in contrast to the project Apache OpenOffice 4.x you do not search in &#039;&#039;location&#039;&#039; but in &#039;&#039;source text&#039;&#039;.<br /> <br /> Unfortunately, if the attribute is &lt;tt&gt;hid=&quot;.&quot;&lt;/tt&gt;, the help identifier is given earlier in the help file, in a branch attribute of a bookmark element for example. And such bookmark element has no content to translate and therefore no entry in the Pootle database.<br /> <br /> Example: Edit a chart and call the context menu. It has the item &#039;&#039;Data Ranges&#039;&#039;. The extended tooltip shows &lt;tt&gt;Opens the Data Ranges dialog where you can edit Data Range and Data Series.&lt;/tt&gt; and the help identifier &lt;tt&gt;uno.DataRanges&lt;/tt&gt;. Imagine the text has an error and you need to find the string in Pootle to correct it. Your search for &#039;&#039;DataRanges&#039;&#039; gets no result.<br /> <br /> In such cases you should search for the extended tip itself. If you use not only a single word but a longer part of the tip, the number of search results will be small.<br /> <br /> Sometimes the attribute &lt;code&gt;visibility=&quot;hidden&quot;&lt;/code&gt; is used. Translate the content nevertheless. The value &quot;hidden&quot; causes, that the text is only shown as extended tooltip and not in the help window.<br /> <br /> ==Switches==<br /> Switches are used to show only one of several alternative strings in the help window. Which content is shown is determined at runtime based on a condition. The &lt;tt&gt;switch&lt;/tt&gt; element chooses a paragraph or section, the &lt;tt&gt;switchinline&lt;/tt&gt; element chooses a fragment inside a paragraph.<br /> <br /> The type of condition is given by a &lt;tt&gt;select&lt;/tt&gt; attribute. Possible values are:<br /> ;sys: Operating system. Runtime conditions are WIN UNIX MAC<br /> ;appl: Application. Runtime conditions are WRITER CALC DRAW IMPRESS MATH BASIC CHART<br /> ;distrib, target, lang, ver: These conditions are currently not used.<br /> <br /> The different contents are given in case or caseinline elements. They have a select attribute too. It has one of the possible runtime condition as value. The default or defaultinline element is used, when the current runtime condition does not fulfill any of the other case or caseinline elements.<br /> <br /> In a usual help window you see only those texts, where the condition is fulfilled by your current runtime environment.<br /> [[File:PootleGuide_selectSysMAC.png|600px|none]]<br /> <br /> On a Windows or Linux system the user sees &lt;tt&gt;hold down Ctrl and&lt;/tt&gt;, on a MAC system the user sees &lt;tt&gt;hold down Command and&lt;/tt&gt;.<br /> <br /> [[File:PootleGuilde_switchSysWINUNIX.png|600px|none]]<br /> <br /> The user on a Windows system sees &lt;tt&gt;The scanner must support the TWAIN standard.&lt;/tt&gt; The user on a Linux system sees &lt;tt&gt;The scanner must support the SANE standard.&lt;/tt&gt; The user on a MAC system sees nothing.<br /> <br /> [[File:PootleGuide_SwitchAppImpressDefault.png|600px|none]]<br /> Calling the help from Impress the user sees &lt;tt&gt;Rename Slide&lt;/tt&gt;, calling it from Draw or another application but Impress the user sees&lt;tt&gt;Rename Page&lt;/tt&gt;.<br /> <br /> Being a translators you likely want to see each possible text. For that purpose you have to manipulate your installation as discribed in section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]].<br /> <br /> <br /> ==Links==<br /> [[File:PootleGuide_LinkWithoutNameAttribute.png|600px|none]]<br /> The &lt;tt&gt;link&lt;/tt&gt; element creates a hyperlink, similar to those known from webpages. The target URL is given in the &lt;tt&gt;href&lt;/tt&gt; attribute. The content of the link element provides the visible text of the link.<br /> <br /> [[File:PootleGuide LinkWithNameAttribute.png|600px|none]]<br /> According to the specification, a link element should have a &lt;tt&gt;name&lt;/tt&gt; attribute to fulfill accessibility requirements. And in contrast to all other elements, the value of the name attribute has to be translated, although it is inside the opening tag.<br /> <br /> ==Items==<br /> [[]]<br /> The &lt;tt&gt;item&lt;/tt&gt; element is used to characterize a part of the text. It is mostly used to provide a unique formatting for a class of objects. The class itself is given in the &lt;tt&gt;type&lt;/tt&gt; attribute. For translators the type=&quot;literal&quot; is relevant. It indicates, that the content should perhaps not be translated, for example because it is a book title or a Basic statement. In other cases it can be translated, for example for localized function names in Calc. So you have to examine the content carefully to decide whether a translation is needed.<br /> <br /> ==Placeholders==<br /> The help contains some placeholders. You will see current placeholders &lt;code&gt;&lt;nowiki&gt;%PRODUCTNAME&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;%PRODUCTVERSION&lt;/nowiki&gt;&lt;/code&gt;, and the deprecated placeholders &lt;code&gt;&lt;nowiki&gt;$[officename]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;$[officeversion]&lt;/nowiki&gt;&lt;/code&gt;. When the help is displayed at runtime, the &#039;&#039;Main Transformation Style Sheet&#039;&#039; &lt;tt&gt;main_transform.xsl&lt;/tt&gt; replaces the placeholder with the information from the configuration file.<br /> <br /> Do not translate placeholders, but transfer them unchanged. Do not use the product name directly but always a placeholder. Otherwise the help will be wrong for different brandings.<br /> <br /> <br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230500 2013-08-28T15:39:53Z

<p>Regina: intermediate, will be continued</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> <br /> ==Basics about the Built-in Help Format==<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example File: helpcontent2/source/text/swriter/guide.po, Location: words_count.xhp#par_id3149821.5.help.text, <br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ==Irrelevant Whitespace==<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ==Strings Used in the Index of the Help==<br /> <br /> Look at the example File:helpcontent2/source/text/swriter/guide.po, Locations: words_count.xhp#bm_id3149686.help.text, [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> <br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> <br /> ==Embedded Content==<br /> The help format allows to embed content from one help file into another. When you read text in the help window, you will not notice this. Use the help manipulation described in the section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]] to make such embedding visible.<br /> <br /> Embedding is done by the elements &lt;tt&gt;embed&lt;/tt&gt; and &lt;tt&gt;embedvar&lt;/tt&gt;, for example &lt;code&gt;&lt;embedvar href=&quot;text/shared/guide/paintbrush.xhp#formatpaintbrush&quot;/&gt;&lt;/code&gt;. Such elements refer to a paragraph, section or variable in another file by the filename and the id value of the referenced part, &lt;tt&gt;formatpaintbrush&lt;/tt&gt; in the example. The id is shown in the manipulated help, so that you can search for it in Pootle by searching for &lt;tt&gt;id=&quot;&#039;&#039;your id&#039;&#039;&quot;&lt;/tt&gt; in the source text. For example search for id=&quot;formatpaintbrush&quot; to find the origin of the above mentioned embedded text fragment.<br /> <br /> ==Images==<br /> [[File:PootleGuide_ImageTag.png|600px|none]]<br /> Images are included by an &lt;tt&gt;image&lt;/tt&gt; element. Inside of it you see an &lt;tt&gt;alt&lt;/tt&gt; child element. It specifies an alternative text for the image. At a first glance it is confusing. But look at the colors in the source text. In the example you see, that only the word &lt;tt&gt;Icon&lt;/tt&gt; has to be translated.<br /> <br /> The image element may have a &lt;tt&gt;caption&lt;/tt&gt; child element, but that is currently not used.<br /> <br /> ==Extended Tooltips==<br /> The text for the [[../Technical_Helpers#Extended_Tips| extended tips]] are stored in the built-in help and therefore their text is in the project Apache OpenOffice 4.x Help although the text is shown in the UI.<br /> <br /> [[File:PootleGuide_ahelp.png|600px|none]]<br /> <br /> Extended tips are provided by an &lt;tt&gt;ahelp&lt;/tt&gt; element. It has a &lt;tt&gt;hid&lt;/tt&gt; attribute to specify the &#039;&#039;help identifier&#039;&#039;, which connects the text to the UI element.<br /> <br /> If you have set the environment variable &lt;tt&gt;HELP_DEBUG=true&lt;/tt&gt;, you see the extended tip itself in the upper part and the help identifier in the lower part of the tip.<br /> <br /> If you know the help identifier of an UI element, you can search for the related text in Pootle. But in contrast to the project Apache OpenOffice 4.x you do not search in &#039;&#039;location&#039;&#039; but in &#039;&#039;source text&#039;&#039;.<br /> <br /> Unfortunately, if the attribute is &lt;tt&gt;hid=&quot;.&quot;&lt;/tt&gt;, the help identifier is given earlier in the help file, in a branch attribute of a bookmark element for example. And such bookmark element has no content to translate and therefore no entry in the Pootle database.<br /> <br /> Example: Edit a chart and call the context menu. It has the item &#039;&#039;Data Ranges&#039;&#039;. The extended tooltip shows &lt;tt&gt;Opens the Data Ranges dialog where you can edit Data Range and Data Series.&lt;/tt&gt; and the help identifier &lt;tt&gt;uno.DataRanges&lt;/tt&gt;. Imagine the text has an error and you need to find the string in Pootle to correct it. Your search for &#039;&#039;DataRanges&#039;&#039; gets no result.<br /> <br /> In such cases you should search for the extended tip itself. If you use not only a single word but a longer part of the tip, the number of search results will be small.<br /> <br /> Sometimes the attribute &lt;code&gt;visibility=&quot;hidden&quot;&lt;/code&gt; is used. Translate the content nevertheless. The value &quot;hidden&quot; causes, that the text is only shown as extended tooltip and not in the help window.<br /> <br /> ==Switches==<br /> Switches are used to show only one of several alternative strings in the help window. Which content is shown is determined at runtime based on a condition. The &lt;tt&gt;switch&lt;/tt&gt; element chooses a paragraph or section, the &lt;tt&gt;switchinline&lt;/tt&gt; element chooses a fragment inside a paragraph.<br /> <br /> The type of condition is given by a &lt;tt&gt;select&lt;/tt&gt; attribute. Possible values are:<br /> ;sys: Operating system. Runtime conditions are WIN UNIX MAC<br /> ;appl: Application. Runtime conditions are WRITER CALC DRAW IMPRESS MATH BASIC CHART<br /> ;distrib, target, lang, ver: These conditions are currently not used.<br /> <br /> The different contents are given in case or caseinline elements. They have a select attribute too. It has one of the possible runtime condition as value. The default or defaultinline element is used, when the current runtime condition does not fulfill any of the other case or caseinline elements.<br /> <br /> In a usual help window you see only those texts, where the condition is fulfilled by your current runtime environment.<br /> [[File:PootleGuide_selectSysMAC.png|600px|none]]<br /> <br /> On a Windows or Linux system the user sees &lt;tt&gt;hold down Ctrl and&lt;/tt&gt;, on a MAC system the user sees &lt;tt&gt;hold down Command and&lt;/tt&gt;.<br /> <br /> [[File:PootleGuilde_switchSysWINUNIX.png|600px|none]]<br /> <br /> The user on a Windows system sees &lt;tt&gt;The scanner must support the TWAIN standard.&lt;/tt&gt; The user on a Linux system sees &lt;tt&gt;The scanner must support the SANE standard.&lt;/tt&gt; The user on a MAC system sees nothing.<br /> <br /> [[File:PootleGuide_SwitchAppImpressDefault.png|600px|none]]<br /> Calling the help from Impress the user sees &lt;tt&gt;Rename Slide&lt;/tt&gt;, calling it from Draw or another application but Impress the user sees&lt;tt&gt;Rename Page&lt;/tt&gt;.<br /> <br /> Being a translators you likely want to see each possible text. For that purpose you have to manipulate your installation as discribed in section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]].<br /> <br /> <br /> ==Links==<br /> [[File:PootleGuide_LinkWithoutNameAttribute.png|600px|none]]<br /> The &lt;tt&gt;link&lt;/tt&gt; element creates a hyperlink, similar to those known from webpages. The target URL is given in the &lt;tt&gt;href&lt;/tt&gt; attribute. The content of the link element provides the visible text of the link.<br /> <br /> [[File:PootleGuide LinkWithNameAttribute.png|600px|none]]<br /> According to the specification, a link element should have a &lt;tt&gt;name&lt;/tt&gt; attribute to fulfill accessibility requirements. And in contrast to all other elements, the value of the name attribute has to be translated, although it is inside the opening tag.<br /> <br /> ==Items==<br /> [[]]<br /> The &lt;tt&gt;item&lt;/tt&gt; element is used to characterize a part of the text. It is mostly used to provide a unique formatting for a class of objects. The class itself is given in the &lt;tt&gt;type&lt;/tt&gt; attribute. For translators the type=&quot;literal&quot; is relevant. It indicates, that the content should perhaps not be translated, for example because it is a book title or a Basic statement. In other cases it can be translated, for example for localized function names in Calc. So you have to examine the content carefully to decide whether a translation is needed.<br /> <br /> ==Placeholders==<br /> The help contains some placeholders. You will see current placeholders &lt;code&gt;&lt;nowiki&gt;%PRODUCTNAME&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;%PRODUCTVERSION&lt;/nowiki&gt;&lt;/code&gt;, and the deprecated placeholders &lt;code&gt;&lt;nowiki&gt;$[officename]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;$[officeversion]&lt;/nowiki&gt;&lt;/code&gt;. When the help is displayed at runtime, the &#039;&#039;Main Transformation Style Sheet&#039;&#039; &lt;tt&gt;main_transform.xsl&lt;/tt&gt; replaces the placeholder with the information from the configuration file.<br /> <br /> Do not translate placeholders, but transfer them unchanged. Do not use the product name directly but always a placeholder. Otherwise the help will be wrong for different brandings.<br /> <br /> <br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_LinkWithNameAttribute.png&diff=230499 2013-08-28T15:38:10Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230498 2013-08-28T15:37:03Z

<p>Regina: (Zwischenspeicherung)</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> <br /> ==Basics about the Built-in Help Format==<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example File: helpcontent2/source/text/swriter/guide.po, Location: words_count.xhp#par_id3149821.5.help.text, <br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ==Irrelevant Whitespace==<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ==Strings Used in the Index of the Help==<br /> <br /> Look at the example File:helpcontent2/source/text/swriter/guide.po, Locations: words_count.xhp#bm_id3149686.help.text, [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> <br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> <br /> ==Embedded Content==<br /> The help format allows to embed content from one help file into another. When you read text in the help window, you will not notice this. Use the help manipulation described in the section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]] to make such embedding visible.<br /> <br /> Embedding is done by the elements &lt;tt&gt;embed&lt;/tt&gt; and &lt;tt&gt;embedvar&lt;/tt&gt;, for example &lt;code&gt;&lt;embedvar href=&quot;text/shared/guide/paintbrush.xhp#formatpaintbrush&quot;/&gt;&lt;/code&gt;. Such elements refer to a paragraph, section or variable in another file by the filename and the id value of the referenced part, &lt;tt&gt;formatpaintbrush&lt;/tt&gt; in the example. The id is shown in the manipulated help, so that you can search for it in Pootle by searching for &lt;tt&gt;id=&quot;&#039;&#039;your id&#039;&#039;&quot;&lt;/tt&gt; in the source text. For example search for id=&quot;formatpaintbrush&quot; to find the origin of the above mentioned embedded text fragment.<br /> <br /> ==Images==<br /> [[File:PootleGuide_ImageTag.png|600px|none]]<br /> Images are included by an &lt;tt&gt;image&lt;/tt&gt; element. Inside of it you see an &lt;tt&gt;alt&lt;/tt&gt; child element. It specifies an alternative text for the image. At a first glance it is confusing. But look at the colors in the source text. In the example you see, that only the word &lt;tt&gt;Icon&lt;/tt&gt; has to be translated.<br /> <br /> The image element may have a &lt;tt&gt;caption&lt;/tt&gt; child element, but that is currently not used.<br /> <br /> ==Extended Tooltips==<br /> The text for the [[../Technical_Helpers#Extended_Tips| extended tips]] are stored in the built-in help and therefore their text is in the project Apache OpenOffice 4.x Help although the text is shown in the UI.<br /> <br /> [[File:PootleGuide_ahelp.png|600px|none]]<br /> <br /> Extended tips are provided by an &lt;tt&gt;ahelp&lt;/tt&gt; element. It has a &lt;tt&gt;hid&lt;/tt&gt; attribute to specify the &#039;&#039;help identifier&#039;&#039;, which connects the text to the UI element.<br /> <br /> If you have set the environment variable &lt;tt&gt;HELP_DEBUG=true&lt;/tt&gt;, you see the extended tip itself in the upper part and the help identifier in the lower part of the tip.<br /> <br /> If you know the help identifier of an UI element, you can search for the related text in Pootle. But in contrast to the project Apache OpenOffice 4.x you do not search in &#039;&#039;location&#039;&#039; but in &#039;&#039;source text&#039;&#039;.<br /> <br /> Unfortunately, if the attribute is &lt;tt&gt;hid=&quot;.&quot;&lt;/tt&gt;, the help identifier is given earlier in the help file, in a branch attribute of a bookmark element for example. And such bookmark element has no content to translate and therefore no entry in the Pootle database.<br /> <br /> Example: Edit a chart and call the context menu. It has the item &#039;&#039;Data Ranges&#039;&#039;. The extended tooltip shows &lt;tt&gt;Opens the Data Ranges dialog where you can edit Data Range and Data Series.&lt;/tt&gt; and the help identifier &lt;tt&gt;uno.DataRanges&lt;/tt&gt;. Imagine the text has an error and you need to find the string in Pootle to correct it. Your search for &#039;&#039;DataRanges&#039;&#039; gets no result.<br /> <br /> In such cases you should search for the extended tip itself. If you use not only a single word but a longer part of the tip, the number of search results will be small.<br /> <br /> Sometimes the attribute &lt;code&gt;visibility=&quot;hidden&quot;&lt;/code&gt; is used. Translate the content nevertheless. The value &quot;hidden&quot; causes, that the text is only shown as extended tooltip and not in the help window.<br /> <br /> ==Switches==<br /> Switches are used to show only one of several alternative strings in the help window. Which content is shown is determined at runtime based on a condition. The &lt;tt&gt;switch&lt;/tt&gt; element chooses a paragraph or section, the &lt;tt&gt;switchinline&lt;/tt&gt; element chooses a fragment inside a paragraph.<br /> <br /> The type of condition is given by a &lt;tt&gt;select&lt;/tt&gt; attribute. Possible values are:<br /> ;sys: Operating system. Runtime conditions are WIN UNIX MAC<br /> ;appl: Application. Runtime conditions are WRITER CALC DRAW IMPRESS MATH BASIC CHART<br /> ;distrib, target, lang, ver: These conditions are currently not used.<br /> <br /> The different contents are given in case or caseinline elements. They have a select attribute too. It has one of the possible runtime condition as value. The default or defaultinline element is used, when the current runtime condition does not fulfill any of the other case or caseinline elements.<br /> <br /> In a usual help window you see only those texts, where the condition is fulfilled by your current runtime environment.<br /> [[File:PootleGuide_selectSysMAC.png|600px|none]]<br /> <br /> On a Windows or Linux system the user sees &lt;tt&gt;hold down Ctrl and&lt;/tt&gt;, on a MAC system the user sees &lt;tt&gt;hold down Command and&lt;/tt&gt;.<br /> <br /> [[File:PootleGuilde_switchSysWINUNIX.png|600px|none]]<br /> <br /> The user on a Windows system sees &lt;tt&gt;The scanner must support the TWAIN standard.&lt;/tt&gt; The user on a Linux system sees &lt;tt&gt;The scanner must support the SANE standard.&lt;/tt&gt; The user on a MAC system sees nothing.<br /> <br /> [[File:PootleGuide_SwitchAppImpressDefault.png|600px|none]]<br /> Calling the help from Impress the user sees &lt;tt&gt;Rename Slide&lt;/tt&gt;, calling it from Draw or another application but Impress the user sees&lt;tt&gt;Rename Page&lt;/tt&gt;.<br /> <br /> Being a translators you likely want to see each possible text. For that purpose you have to manipulate your installation as discribed in section [[../Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help| Transforming the Style of the Built-in Help]].<br /> <br /> <br /> ==Links==<br /> [[File:PootleGuide_LinkWithoutNameAttribute.png|600px|none]]<br /> The &lt;tt&gt;link&lt;/tt&gt; element creates a hyperlink, similar to those known from webpages. The target URL is given in the &lt;tt&gt;href&lt;/tt&gt; attribute. The content of the link element provides the visible text of the link.<br /> <br /> [[with name]]<br /> According to the specification, a link element should have a &lt;tt&gt;name&lt;/tt&gt; attribute to fulfill accessibility requirements. And in contrast to all other elements, the value of the name attribute has to be translated, although it is inside the opening tag.<br /> <br /> ==Items==<br /> [[]]<br /> The &lt;tt&gt;item&lt;/tt&gt; element is used to characterize a part of the text. It is mostly used to provide a unique formatting for a class of objects. The class itself is given in the &lt;tt&gt;type&lt;/tt&gt; attribute. For translators the type=&quot;literal&quot; is relevant. It indicates, that the content should perhaps not be translated, for example because it is a book title or a Basic statement. In other cases it can be translated, for example for localized function names in Calc. So you have to examine the content carefully to decide whether a translation is needed.<br /> <br /> ==Placeholders==<br /> The help contains some placeholders. You will see current placeholders &lt;code&gt;&lt;nowiki&gt;%PRODUCTNAME&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;%PRODUCTVERSION&lt;/nowiki&gt;&lt;/code&gt;, and the deprecated placeholders &lt;code&gt;&lt;nowiki&gt;$[officename]&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;$[officeversion]&lt;/nowiki&gt;&lt;/code&gt;. When the help is displayed at runtime, the &#039;&#039;Main Transformation Style Sheet&#039;&#039; &lt;tt&gt;main_transform.xsl&lt;/tt&gt; replaces the placeholder with the information from the configuration file.<br /> <br /> Do not translate placeholders, but transfer them unchanged. Do not use the product name directly but always a placeholder. Otherwise the help will be wrong for different brandings.<br /> <br /> <br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_LinkWithoutNameAttribute.png&diff=230497 2013-08-28T15:35:27Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_SwitchAppImpressDefault.png&diff=230496 2013-08-28T15:28:47Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuilde_switchSysWINUNIX.png&diff=230495 2013-08-28T15:26:59Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_selectSysMAC.png&diff=230494 2013-08-28T15:23:54Z

<p>Regina: Screenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Screenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_ahelp.png&diff=230493 2013-08-28T15:16:03Z

<p>Regina: Sreenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>Sreenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_ImageTag.png&diff=230491 2013-08-28T14:45:12Z

<p>Regina: Regina uploaded a new version of &amp;quot;File:PootleGuide ImageTag.png&amp;quot;: new version without spell-check marks.</p> <hr /> <div>SCreenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_ImageTag.png&diff=230490 2013-08-28T14:36:38Z

<p>Regina: SCreenshot. Author: Regina Henschel Category:Screenshots and Dialogs</p> <hr /> <div>SCreenshot. Author: Regina Henschel<br /> <br /> [[Category:Screenshots and Dialogs]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230473 2013-08-26T21:48:46Z

<p>Regina: /* Basics about the Built-in Help Format */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> ==Understanding the format of the help==<br /> <br /> ===Basics about the Built-in Help Format===<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms.<br /> <br /> Some content here is taken from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf) and adapted. The book itself refers to another translation tool, which was used for OpenOffice.org 2 and cannot be used directly.<br /> <br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> <br /> ;Child element: Element content can contain other (nested) elements. Such is called &#039;&#039;child element&#039;&#039;. You must copy the opening and closing tag of the child element exactly and translate the content of the child element.<br /> <br /> You must not translate anything inside a tag but only the element content. The only exception is the value of the name attribute of a link element.<br /> <br /> Example<br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ===Irrelevant Whitespace===<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ===Strings Used in the Index of the Help===<br /> Look at the example [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> == Extended tips ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Location inside the help&#039;&#039;&gt;<br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230470 2013-08-26T20:34:54Z

<p>Regina: /* Recognize Tags */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> ==Understanding the format of the help==<br /> <br /> ===Basics about the Built-in Help Format===<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translators need not know all details, but should have a basic understanding of some terms. Here a quotation from [http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/documentation/online_help/localization/LocalisationguideOOo2.pdf Localizing Documentation ] (pdf), page 7, so far as it is still relevant:<br /> <br /> &lt;div style=&quot;margin-left:2em&quot;&gt;<br /> ;Element: An XML element is a logical xml fragment that is surrounded by tags, e.g. &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;Paragraph Content&lt;/paragraph&gt;&lt;/code&gt;<br /> <br /> ;Tag: A tag is the delimiter of an element and is enclosed in brackets:&lt;code&gt;&lt;&gt;&lt;/code&gt;. Most elements have an opening tag at the beginning and a closing tag at the end. The opening tag may contain attributes, for example &lt;code&gt;&lt;paragraph role=&quot;heading&quot;&gt;&lt;/code&gt; in the example above. The closing tag always starts with a slash &lt;code&gt;/&lt;/code&gt; and does not contain attributes, for example &lt;code&gt;&lt;/paragraph&gt;&lt;/code&gt; in the example above. Some tags don&#039;t have any content, for example &lt;code&gt;&lt;nowiki&gt;&lt;br&gt;&lt;/br&gt;&lt;/nowiki&gt;&lt;/code&gt;. These are sometimes also written as one standalone tag, for example &lt;code&gt;&lt;nowiki&gt;&lt;br /&gt;&lt;/nowiki&gt;&lt;/code&gt;.<br /> <br /> ;Attribute: An attribute might appear in the opening or standalone tag of an element and is used to further specify the element, e.g. &lt;code&gt;role&lt;/code&gt; in the example above. An attribute always is associated with a value, e.g. &lt;code&gt;&quot;heading&quot;&lt;/code&gt; in the example above.<br /> &lt;/div&gt;<br /> <br /> You must not translate anything inside a tag but only the element content (besides one exception which is shown later).<br /> <br /> Example<br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the opening tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the closing tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphasized. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ===Irrelevant Whitespace===<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ===Strings Used in the Index of the Help===<br /> Look at the example [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> == Extended tips ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Location inside the help&#039;&#039;&gt;<br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230459 2013-08-26T19:55:11Z

<p>Regina: /* Irrelevant Whitespace */</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> ==Understanding the format of the help==<br /> <br /> ===Recognize Tags===<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translaters need not know all details. But you have to know, that there exists so named &quot;tags&quot;, which describe the structure of the help file. Such tag begins with &lt; and ends with &gt;. There are nearly alway a pair of them, a start tag with a keyword and some attribute=value parts and an end tag with /keyword. Between start tag and end tag is the content, which you have to translate. You must not translate anything inside a tag (besides one exception which is shown later).<br /> <br /> Example<br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the start tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the end tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphazised. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ===Irrelevant Whitespace===<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read. You can ignore these red wave-lines.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ===Strings Used in the Index of the Help===<br /> Look at the example [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> == Extended tips ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Location inside the help&#039;&#039;&gt;<br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Quality_Assurance&diff=230455 2013-08-26T19:52:48Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Quality Assurance (QA)}}<br /> <br /> __TOC__<br /> {{Attention| Please add further tips to ensure a high quality of the translations.}}<br /> ==Peer review==<br /> <br /> === Review Suggestions ===<br /> If you have got a Pootle account, you&#039;ll be able to accept or reject suggestions from other translators.<br /> * Select a project and your language.<br /> * To restrict the shown translations records to those with suggestions do one of these:<br /> ** Click on &quot;Review suggestions&quot; in the &quot;Overview&quot; tab page.<br /> ** Click on the number in the column &quot;Suggestions&quot; on the tree view in the &quot;Overview&quot; tab page<br /> ** Choose the filter &quot;Suggestions&quot; in the &quot;Translate&quot; tab page.<br /> : If you first choose a folder and then set a filter, the shown translation records are restricted to this folder.<br /> * Go through the suggestions one by one. Accept or reject the suggestion. If the suggestion is accepted, it is submitted. If it is rejected, the existing translation will not be changed. Click on &quot;Next string&quot; without action to skip a suggestion.<br /> <br /> === Checkbox &quot;Needs work&quot; ===<br /> Some teams want to have all new or modified translations reviewed. To make it different from suggestions from anonymous translators without account, they can agree to use the &quot;Needs work&quot; checkbox. In previous versions of Pootle this checkbox was labeled &quot;fuzzy&quot;. So you find instructions to organize review by marking changes as &quot;fuzzy&quot; and let the reviewer &quot;unfuzzy&quot; it after verifying that the translation is correct. To filter for these changes use the filter item &quot;Needs Work&quot;.<br /> <br /> ==Show Pootle Warnings==<br /> [[File:PootleGuide_OverviewDetails.png|250px|thumb|left]]<br /> <br /> Click on the left tab to switch to the Overview. Click on the &#039;&#039;Detail&#039;&#039; link to show, what Pootle considers to be an error.<br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_OverviewShowDetails.png|250px|thumb|left]]<br /> <br /> You see a list with check categories and corresponding number of errors. Find a description of the categories [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/pofilter_tests.html| here]. Please examine especially &lt;code&gt;XML tags&lt;/code&gt; -warnings very carefully. <br /> <br /> Click on the category or on the number to get the list of translation records. Be patient; click on &quot;continue&quot;, when your browser thinks that &quot;a script has stopped working&quot;.<br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_PlaceholderCheckFail.png|250px|thumb|left]]<br /> <br /> The translation record shows too, that a check failed.<br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_PlaceholderCheckExamineText.png|350px|thumb|left]]<br /> And in the screenshot you can see, that Pootle is right in this example.<br /> <br /> In case of a false positive warning, e.g. &quot;Repeated word&quot; warning for the English string &quot;Dot Dot Dash&quot; (which is a line style), you can click on the &quot;No entry&quot;-sign to remove this warning from the record. <br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_FilterTypCheck.png|450px|thumb|none]]<br /> <br /> The list of failed records is available too from the &quot;Translate&quot; tab page. Select the item &quot;Checks&quot; from the &quot;Filter by&quot;-drop-down-list at the bottom of the page. It is the last item in the list. Now you get a second drop-down-list to select the check category. The number in brackets tells you how many translation records failed the check.<br /> <br /> ==Check for Untranslated Strings==<br /> <br /> Sometimes it happens - I don&#039;t know the conditions – that the target string is copied verbatim from the source string and is not translated. Those records show not up as &quot;untranslated&quot; and you might miss, that they are still waiting for translation.<br /> <br /> You can find them by using the filter &quot;Check&quot; with the condition &quot;unchanged&quot;. In folder sbasic you will get a lot of false positive, because there a many lines of program code examples, which need to stay untranslated. But examine carefully the results in the other folders.<br /> <br /> ==Review Language Builds==<br /> <br /> A few weeks before the final release you will get a beta release in your language. Watch the localization mailing list for announcements. Encourage your local community to review the build carefully to catch all translation errors.<br /> <br /> You can build OpenOffice yourself or ask a community member to do it for you, to get a localized build. But prior to building, the translated strings from Pootle have to be reintegrated into trunk. So ask for this on the localization mailing list, if you need an intermediate localized build.<br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230427 2013-08-25T22:24:35Z

<p>Regina: /* Recognize Tags */ Image of syntaxhighlighting in Pootle</p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> ==Understanding the format of the help==<br /> <br /> ===Recognize Tags===<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translaters need not know all details. But you have to know, that there exists so named &quot;tags&quot;, which describe the structure of the help file. Such tag begins with &lt; and ends with &gt;. There are nearly alway a pair of them, a start tag with a keyword and some attribute=value parts and an end tag with /keyword. Between start tag and end tag is the content, which you have to translate. You must not translate anything inside a tag (besides one exception which is shown later).<br /> <br /> Example<br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the start tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the end tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> In the source text in Pootle you see [[File:PootleGuide_Syntaxhighlight.png|400px|none]]<br /> Notice, that Pootle uses different colors for the tags and for the actual text.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphazised. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ===Irrelevant Whitespace===<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. If they are between an end tag and a start tag, you can ignore them. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ===Strings Used in the Index of the Help===<br /> Look at the example [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> == Extended tips ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Location inside the help&#039;&#039;&gt;<br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_Syntaxhighlight.png&diff=230425 2013-08-25T22:17:29Z

<p>Regina: Screenshot. Author:Regina Henschel</p> <hr /> <div>Screenshot. Author:Regina Henschel</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Translation_Built-in_Help&diff=230415 2013-08-25T20:40:01Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Translation of the Built-in Help}}<br /> <br /> ==Understanding the format of the help==<br /> <br /> ===Recognize Tags===<br /> <br /> The format of the help is derived from XML and specified in the [http://www.openoffice.org/documentation/online_help/OOo2HelpAuthoring.pdf Understanding and Authoring OpenOffice 2.0 Online Help] (pdf) document. Translaters need not know all details. But you have to know, that there exists so named &quot;tags&quot;, which describe the structure of the help file. Such tag begins with &lt; and ends with &gt;. There are nearly alway a pair of them, a start tag with a keyword and some attribute=value parts and an end tag with /keyword. Between start tag and end tag is the content, which you have to translate. You must not translate anything inside a tag (besides one exception which is shown later).<br /> <br /> Example<br /> [https://translate.apache.org/de/aoo40help/translate.html#unit=12958811 String 12958811]<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> Choose &lt;emph&gt;Tools - Word Count&lt;/emph&gt;.<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;code&gt;&lt;emph&gt;&lt;/code&gt; is the start tag, &lt;code&gt;&lt;/emph&gt;&lt;/code&gt; is the end tag. Do not translate them. You have only to translate the parts &lt;tt&gt;Choose&lt;/tt&gt; and &lt;tt&gt;Tools - Word Count&lt;/tt&gt;.<br /> <br /> The tag pair &lt;code&gt;&lt;emph&gt; … &lt;/emph&gt;&lt;/code&gt; causes, that the content is emphazised. This is done by showing the content in bold.<br /> <br /> In the help you see &lt;tt&gt;Choose &#039;&#039;&#039;Tools - Word Count&#039;&#039;&#039;.&lt;/tt&gt;<br /> <br /> Sometimes Pootle shows you only the content, but in other cases you see the tags as well.<br /> <br /> ===Irrelevant Whitespace===<br /> Sometimes you see red wave-lines, see picture below. They belong to line breaks in the source file. If they are between an end tag and a start tag, you can ignore them. Such line breaks do not influence how the help text is shown, but are used by the developers to make the source text easier to read.<br /> <br /> The line breaks you see in Pootle depend on the width of the browser window and are irrelevant too. Write your text in the input field without any explicit line break. Texts which have to go to different paragraphs are separate records in Pootle.<br /> <br /> ===Strings Used in the Index of the Help===<br /> Look at the example [https://translate.apache.org/de/aoo40help/translate.html#unit=12958808 string 12958808].<br /> The help file has the content<br /> &lt;syntaxhighlight lang=&quot;xml&quot;&gt;<br /> &lt;bookmark xml-lang=&quot;en-US&quot; branch=&quot;index&quot; id=&quot;bm_id3149686&quot;&gt;<br /> &lt;bookmark_value&gt;words; counting in text&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;documents; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;text; number of words/characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;characters; counting&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;number of characters&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;counting words&lt;/bookmark_value&gt;<br /> &lt;bookmark_value&gt;word counts&lt;/bookmark_value&gt;<br /> &lt;/bookmark&gt;<br /> &lt;/syntaxhighlight&gt;<br /> You see in Pootle<br /> [[File:PootleGuide_BookmarkTag.png|799px|none]]<br /> <br /> The &lt;tt&gt;bookmark&lt;/tt&gt; element in connection with the attribute &lt;tt&gt;branch=&quot;index&quot;&lt;/tt&gt; means, that this is content to be shown in the &lt;tt&gt;Index&lt;/tt&gt; tab of the help. Each of the &lt;tt&gt;bookmark_value&lt;/tt&gt; elements determines an item for the index. If their is a semicolon, the left part is the main item and the right part is a subitem. Items in the index are sorted automatically, so you need not care of alphabetical order.<br /> == What must not be Translated==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;There are some examples in LibreOffice Wiki and on http://openoffice.apache.org/translate.html&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;show examples for each item&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;tag&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;placeholder&#039;&#039;&gt;<br /> <br /> &lt;&#039;&#039;StarBasic source code&#039;&#039;&gt;<br /> <br /> == Extended tips ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Location inside the help&#039;&#039;&gt;<br /> <br /> == Finding items ==<br /> &#039;&#039;&#039;ToDo&#039;&#039;&#039;<br /> <br /> &lt;&#039;&#039;Find an item by filename and paragraph ID.&#039;&#039;, link to Pootle_User_Guide/Technical_Helpers#Transforming_the_Style_of_the_Built-in_Help &#039;&#039;&gt;<br /> <br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=File:PootleGuide_BookmarkTag.png&diff=230414 2013-08-25T20:25:32Z

<p>Regina: Screenshot. Author: Regina Henschel</p> <hr /> <div>Screenshot. Author: Regina Henschel</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide&diff=230376 2013-08-22T13:01:12Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Pootle User Guide}}<br /> __NOTOC__<br /> <br /> [http://www.apache.org/| The Apache Software Foundation] runs a Pootle Translate service to allow its projects an easy, cooperative way to localize their products. This guide describes how to use Pootle in the Apache OpenOffice project. As of August 2013, already 40 languages (out of the 120+ languages OpenOffice supports) are maintained in Pootle and more coming soon.<br /> <br /> For an introduction to the localization process read http://openoffice.apache.org/translate.html and for a more general overview start at http://openoffice.apache.org/get-involved.html.<br /> <br /> ;Registration and Login: The chapter describes how to become a Translator.<br /> ;Overview Pootle UI: The chapter introduces you to the elements in the user interface of Pootle. <br /> ;Offline Translation: The chapter explains how to translate offline.<br /> ;Quality Assurance: The chapter provides tips to ensure a high quality of the translation.<br /> ;Releasing a Localized Build: The chapter describes the steps needed to provide a localized version of Apache OpenOffice.<br /> ;Technical Helpers: The chapter shows you helpers for the process of translation.<br /> ;Translation of the User Interface: The chapter lists tips and tricks for translating the user interface of Apache OpenOffice.<br /> ;Translation of the Built-in Help: The chapter lists tips and tricks for translating the built-in help of Apache OpenOffice.<br /> ;General Problems: The chapter gives you assistance in general problems, which might occur during the translating process.<br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Talk:Pootle_User_Guide&diff=230375 2013-08-22T12:51:19Z

<p>Regina: </p> <hr /> <div>The new Pootle User Guide is &quot;live&quot; now. But you will find a lot of &quot;ToDo&quot;s and empty sections. Please help to complete the guide and to correct all the errors.<br /> <br /> At the beginning of each page you find a template, that shows the TOC from the right sight. It is the same on every page and should therefore be easy to translate.<br /> <br /> At the end of the page is a list of languages. These are shown automatically in the left column. The links itself are dummies, but will you help to find the form, when you translate the content.<br /> <br /> I hope you find the new Pootle User Guide useful. [[User:Regina|Regina]] ([[User talk:Regina|talk]]) 12:51, 22 August 2013 (UTC)<br /> ----</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Registration_and_Login&diff=230374 2013-08-22T12:41:53Z

<p>Regina: </p> <hr /> <div><br /> {{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*Registration and Login<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> {{DISPLAYTITLE:Registration and Login}}<br /> <br /> ==Anyone may Translate==<br /> You need not to register or login for helping in translation. Anyone can make suggestions in Pootle. Those will be reviewed by committers and then stored into the database.<br /> <br /> Start with Pootle at https://translate.apache.org and choose your language and project in any order. The project &#039;&#039;&#039;Apache OpenOffice 4.x&#039;&#039;&#039; covers the strings, which can be seen in the user interface (UI), the project &#039;&#039;&#039;Apache OpenOffice 4.x Help&#039;&#039;&#039; covers the texts in the built-in help. Always choose the project with the highest version number.<br /> ==Registration==<br /> &lt;&#039;&#039;merged https://cwiki.apache.org/confluence/display/OOOUSERS/I%27m+a+new+Volunteer%2C+I+want+to+help! into this guide. Can it be removed on CWIKI?&#039;&#039;&gt;<br /> <br /> If you are seriously interested and will work collaboratively with the other translators, you can get a Pootle account.<br /> <br /> # Subscribe to the [http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public| localization mailing list]. Note: It&#039;s a public list and you will probably get many related mails, but it&#039;s a way to get in touch and communicate each other.<br /> # Introduce yourself on the list and find members in your language.<br /> # Become familiar with Pootle. If your language is missing on Pootle, ask on l10n@openoffice.apache.org to add it. We will react as soon as possible.<br /> # Ask for a Pootle account by sending an email:<br /> <br /> To: l10n@openoffice.apache.org<br /> Subject: New Pootle Account<br /> Body: <br /> Hello my name is ..... and .... <br /> Please create a Pootle account for me. I state that my contributions are under&lt;br /&gt; the Apache 2 license and I will work on ...&lt;your language&gt;...<br /> My preferred username is ...&lt;preferred username&gt;...<br /> <br /> The administrators of the Pootle server will contact you for username/password.<br /> <br /> All project committers have automatically a Pootle accout and can use their Apache username/password on Pootle.<br /> ==Login==<br /> To login at Pootle click on the log-in text, top right in the blue area. Afterward you will find a link to your account settings in this area.<br /> ==Maintain Translation==<br /> If you are willing to maintain the translation in the longer term, tell this on the mailing list and find collegues there. Add yourself to the list on https://cwiki.apache.org/confluence/display/OOOUSERS/Localization+Volunteers<br /> <br /> <br /> [[Category:Localization]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Online_Pootle_User_Interface&diff=230373 2013-08-22T12:41:10Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Overview to the Pootle Online User Interface}}<br /> <br /> == Tab page &quot;Overview&quot; ==<br /> The user interface of Pootle is localized. Therefore some screenshots here show non English texts. When you login, you can choose the language of the Pootle UI.<br /> <br /> [[File:PootleGuideA_QuickTranslateExample2.png|250px|thumb|right]]<br /> ;A: The summary text in the upper left area provides predefined filters; it is the so called &#039;&#039;Quick Translate&#039;&#039; mode. It shows only items, which need to be worked on.<br /> [[File:PootleGuideA_QuickTranslateExample1.png|250px|thumb|left]]<br /> <br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuideB_TreeView.png|250px|thumb]]<br /> <br /> ;B: The tree view follows the internal structure of the source code. Here you get access to all strings of a specific file; this is the so called &#039;&#039;Translate All&#039;&#039; mode. It shows all items, regardless of their translation status. Hover the green bar to see what percentage of the folder is already translated. There are about 440000 words in the built-in help and 90000 words in the UI to translate.<br /> <br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_SearchField.png|thumb]]<br /> <br /> ;C: For correcting a single wrong text, you will likely need the search. Here on the overview tab page it is in the right top corner and on the translation tab page you find it in the left bottom corner. It will be explained in detail in section [[#Search_Properties| Search Properties]].<br /> <br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_DownloadUpload.png|250px|thumb]]<br /> <br /> ;D: For [[#Off-line_Translation | off-line translation]] you can download and upload .po-files. Find the links in the right part.<br /> <br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_TabPageOverview.png|thumb]]<br /> <br /> Choosing any of the modes A-C you get a list of translation records in the translation tab page. To switch back to the overview click on the left tab, top left on the screen.<br /> <br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> == Tab Page &quot;Translate&quot; ==<br /> {{Documentation/Note|Most UI elements have got a tooltip. Those have information about shortcut keys in addition. So hover with the mouse and explore the UI.}}<br /> <br /> The tab page &quot;Translation&quot; shows a list of translation records. When you are logged in, you can set in your preferences, how many record lines are shown at a time. Click a record to open it, the other record will collapse automatically. Please be patient, after some seconds additional elements are shown. You might need to allow your browser to show &quot;unsafe&quot; sites.<br /> <br /> [[File:PootleGuide_TabPageTranslationWithMarkers.png|600px|none]]<br /> <br /> The area of the active translation record shows you<br /> <br /> ;E: the &#039;&#039;&#039;file name&#039;&#039;&#039; of the .po file, which contains the string.&lt;br /&gt; Such .po file collects basically the strings from one folder in the source code.<br /> <br /> ;F: the &#039;&#039;&#039;location&#039;&#039;&#039;, the exact position of the string in the source code.&lt;br /&gt; Left of the # sign you see the file name, right of it the identifier of the string.<br /> <br /> ;G: the &#039;&#039;&#039;Terminology&#039;&#039;&#039; with translation suggestions of single words.&lt;br /&gt;Read details on [[Pootle_Glossary_Guide]]. Ask the administrators in case you want to use such &#039;&#039;&#039;Glossary&#039;&#039;&#039; for your language.<br /> <br /> ;H: In case you have selected alternative languages as additional source text in the preferences of your account, or the translation target language is different from your locale, you see here the translations into those languages too. <br /> <br /> ;I: the original English text, the &#039;&#039;&#039;source&#039;&#039;&#039; text<br /> <br /> ;J: the input field to enter your translation, the &#039;&#039;&#039;target&#039;&#039;&#039; text<br /> <br /> ;K: a &#039;&#039;&#039;suggestion&#039;&#039;&#039; from another translator&lt;br /&gt;Hover the picture or avatar to see the name, click it to show the account information. <br /> <br /> ;L: already existing translations of similar strings&lt;br /&gt;Read details on [[Pootle_Glossary_Guide]]. Ask the administrators in case you want to use such &#039;&#039;&#039;Translation Memory&#039;&#039;&#039; for your language.<br /> <br /> ;M: a button to submit the suggestion.<br /> <br /> ;R: This is a link to the mobile version of Wikipedia. Mark a term on the screen and then click on icon &lt;tt&gt;W&lt;/tt&gt; to see its entry in the Wikipedia.<br /> <br /> In the footer, in the lower part of the user interface you get<br /> <br /> ;N: the &#039;&#039;&#039;search&#039;&#039;&#039;, see section [[#Search_and_Filter| Search and Filter]] for details<br /> <br /> ;O: the &#039;&#039;&#039;filter&#039;&#039;&#039; to restrict the set of shown translation records to special kinds, suggestions or untranslated e.g.<br /> <br /> ;P: a direct link to the current translation record.&lt;br /&gt;Copy it, if you will reference this special translation record in an email, for example.<br /> <br /> ;Q: the navigation area.&lt;br /&gt;Look at the tooltips to get further hints for navigation.<br /> <br /> If you do not see all elements in the footer, make your browser window wider.<br /> <br /> If you are logged in, you have some items more.<br /> <br /> [[File:PootleGuide_TranslateInCommiterViewWithMarkers.png|600px|thumb|none]]<br /> <br /> ;S: a text link to toggle the button between &#039;&#039;Suggest&#039;&#039; and &#039;&#039;Submit&#039;&#039;<br /> <br /> ;T: a checkbox to mark, that the translation &#039;&#039;&#039;needs work&#039;&#039;&#039;.&lt;br /&gt;This state was called &#039;&#039;Fuzzy&#039;&#039; in previous Pootle versions. You can use it as filter.<br /> <br /> ;U: Buttons to accept or reject suggestions<br /> <br /> ;V: a link to open an input field for a &#039;&#039;&#039;comment&#039;&#039;&#039;<br /> <br /> == Search and Filter ==<br /> <br /> ===Search Properties===<br /> [[File:PootleGuide_SearchFields.png|192px|right]]<br /> *The search is only executed on the current active set of files. Select the files in the &#039;&#039;Overview&#039;&#039; tab page and/or restrict the selection with the filter. To start with all files click the project name on the &#039;&#039;Overview&#039;&#039; tab page and then click on the tab &#039;&#039;Translate&#039;&#039;.<br /> *Only the fields &#039;&#039;Source Text&#039;&#039;, &#039;&#039;Target Text&#039;&#039;, &#039;&#039;Comments&#039;&#039;, and &#039;&#039;Locations&#039;&#039; are searchable. Combine them as you like. When you click into the search field a popup with check-boxes opens; you have to check at least one. The settings are remembered for your next search. <br /> *The short cut key Strg+Shift+S put the cursor into the search field without opening the popup.<br /> *Press enter key or click the magnifier icon to start search.<br /> *The search is not case sensitive, e.g. &#039;&#039;Page&#039;&#039; will find &#039;&#039;page&#039;&#039; too.<br /> *The search is not restricted to whole words, but will find part of words too, e.g. &quot;lign&quot; will find &quot;alignment&quot;.<br /> *There exists no explicit AND or OR or NOT. Two words which are separated by a blank, are treated as two terms and connected with AND.<br /> *Searching for exact phrases is not possible. e.g. &#039;&#039;line spacing&#039;&#039; cannot be searched as single phrase, but will be treated as search for &#039;&#039;line AND spacing&#039;&#039;.<br /> *The search uses UTF-8 coding, so non-Latin scripts can use it too.<br /> *The search term may have special characters like dot, colon, or tilde.<br /> *You cannot restrict the search to previous search results. Each search starts newly.<br /> *The search term must not start with a blank, otherwise you get no results at all.<br /> <br /> ===Using subset of files===<br /> To work on the whole set of files go to the &#039;&#039;Overview&#039;&#039; tab page, click on the project and then on the tab &#039;&#039;Translate&#039;&#039;.<br /> <br /> To work on a subset of files you can restrict your work to a subfolder or apply a filter. You can combine this two methods, first select the subfolder and then the filter.<br /> <br /> &#039;&#039;&#039;Subfolder&#039;&#039;&#039;<br /> <br /> To work on a subfolder go to the Overview tab page and<br /> * click on the number in the column &#039;&#039;total&#039;&#039; for the desired subfolder or<br /> * doubleclick the subfolder you are interested in, so that you see its content, and then click on the tab &#039;&#039;Translate&#039;&#039;.<br /> <br /> &#039;&#039;&#039;Filter on Overview Page&#039;&#039;&#039;<br /> <br /> To apply a filter starting on the Overview tab page<br /> * click on the text &quot;Continue translation&quot; or &quot;Review suggestions&quot;.<br /> * click on a number in the column &quot;Need translation&quot; or &quot;Suggestion&quot;.<br /> * click on the text &quot;Expand details&quot; and then click on one of the criteria text links or a number link.<br /> When you hover a link with the mouse you can see in the status bar of your browser, which filter it applies.<br /> <br /> &#039;&#039;&#039;Filter on Translate Page&#039;&#039;&#039;<br /> <br /> To apply a filter starting on the Translate tab page, open the Filter drop-down list and click on the filter name. In case of the filter &quot;Checks&quot; you get a second drop-down list to select the criterium.<br /> *&lt;tt&gt;All&lt;/tt&gt; shows all records. If you have selected a subfolder, it does not show all records of the database, but only those of the subfolder.<br /> *&lt;tt&gt;Translated&lt;/tt&gt; shows all already translated records, useful for fixing errors in submitted strings.<br /> *&lt;tt&gt;Incomplete&lt;/tt&gt; shows untranslated records and records with &quot;Need work&quot; checked.<br /> *&lt;tt&gt;Untranslated&lt;/tt&gt; shows only untranslated records.<br /> *&lt;tt&gt;Needs work&lt;/tt&gt; shows only records with &quot;Need work&quot; checked. This state is called &quot;fuzzy&quot;.<br /> *&lt;tt&gt;Suggenstions&lt;/tt&gt; shows suggestions, useful for review.<br /> *&lt;tt&gt;My Suggenstions&lt;/tt&gt; shows suggestions by the current translator. Translaters not logged in are tracked as &#039;&#039;nobody&#039;&#039;.<br /> *&lt;tt&gt;My submissions&lt;/tt&gt; shows submission by the current translator, only useful if you are logged in.<br /> *&lt;tt&gt;My overwritten submissions&lt;/tt&gt; shows changes on your submissions. There should have been a discussion in your team about those records or at least a comment should have been added.<br /> *&lt;tt&gt;Check&lt;/tt&gt; shows only records where Pootle has found a problem, see section [[#Show_Pootle_Warnings| Show Pootle Warnings ]] for details.<br /> <br /> <br /> [[Category:Localization]]<br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Offline_Translation&diff=230372 2013-08-22T12:40:18Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Offline Translation}}<br /> <br /> __TOC__<br /> <br /> == Download Files ==<br /> <br /> Before starting to translate offline, you should make sure to &#039;&#039;&#039;coordinate the translation activity&#039;&#039;&#039; with your team.<br /> <br /> If you want to translate offline, you need to download the files from Pootle and to upload them once translated. These options are available on the &quot;Overview&quot; tab page.<br /> [[File:PootleGuide_PrepairForDownload.png|300px|thumb|none]]<br /> <br /> You can download either the complete project files, or by folder, or single files. First select the folder in the tree-view on the left side of the &quot;Overview&quot; tab page, so that you see the content of the folder. Then click &quot;Download&quot;. You need to wait a little bit, because the .zip file is generated on demand. In the situation shown in the picture you would get a file &lt;tt&gt;aoo40help-de-helpcontent2-source-text-sdraw.zip&lt;/tt&gt;. Notice that the file name contains the path as it is shown on the picture.<br /> <br /> == Work Offline ==<br /> You can work with a preferred editor. Most commonly used editors by community are:<br /> <br /> * [http://www.poedit.net Poedit]<br /> <br /> * [http://www.omegat.org OmegaT]<br /> <br /> If you want to work with only fuzzy/untranslated strings, an extra step is needed to filter those strings from downloaded .po file.<br /> <br /> * Run [http://translate.sourceforge.net/wiki/toolkit/pofilter pofilter] which is a part of Translate Toolkit. You can download Translate Toolkit from [http://sourceforge.net/project/showfiles.php?group_id=91920&amp;package_id=97082 here]<br /> ** &#039;&#039;pofilter -t isfuzzy -t untranslated &lt;input file&gt; &lt;filtered file&gt;&#039;&#039;<br /> <br /> This will extract all strings which are fuzzy or untranslated.&lt;br /&gt;<br /> <br /> Once you finish working in filtered po file, you can merge it back into the original file using [http://translate.sourceforge.net/wiki/toolkit/pomerge pomerge] before uploading to Pootle.<br /> <br /> == Upload Translated Files ==<br /> Once translation is completed, you need to upload your work to Pootle.<br /> <br /> There are three options of upload. Anyone has the option &quot;suggest&quot;, logged in users have the additional options &quot;merge&quot; and &quot;overwrite&quot;.<br /> {|<br /> |-<br /> | [[File:PootleGuide_Upload_Anyone.png|250px|thumb]]<br /> | [[File:PootleGuide_Upload_Commiter.png|250px|thumb]]<br /> |-<br /> |}<br /> <br /> ;suggest: All changes are treated as suggestions.<br /> <br /> ;merge: Default option for logged in users. Previously untranslated strings are submitted and the modifications of already translated strings are marked as &#039;suggestion&#039;, which means they need a review before submission. If you make some modifications to existing translations (e.g., bug fixing), please make sure that they are reviewed and accepted by reviewer. Unless, the modifications won&#039;t be applied.<br /> <br /> ;overwrite: The uploaded file overwrites the existing file on Pootle. This option should be carefully used as it has possibility to loose existing data. If you make sure all the contents of your file are valid, you can choose &#039;overwrite&#039; option for quick upload.<br /> <br /> Note: During uploading, you should make sure that you&#039;re located in the right folder. You should upload a .zip file in the same folder that you downloaded it from. If you upload a file to a wrong location, please contact a Pootle administrator.<br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Quality_Assurance&diff=230371 2013-08-22T12:39:47Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Quality Assurance (QA)}}<br /> <br /> __TOC__<br /> {{Attention| Please add further tips to ensure a high quality of the translations.}}<br /> ==Peer review==<br /> <br /> === Review Suggestions ===<br /> If you have got a Pootle account, you&#039;ll be able to accept or reject suggestions from other translators.<br /> * Select a project and your language.<br /> * To restrict the shown translations records to those with suggestions do one of these:<br /> ** Click on &quot;Review suggestions&quot; in the &quot;Overview&quot; tab page.<br /> ** Click on the number in the column &quot;Suggestions&quot; on the tree view in the &quot;Overview&quot; tab page<br /> ** Choose the filter &quot;Suggestions&quot; in the &quot;Translate&quot; tab page.<br /> : If you first choose a folder and then set a filter, the shown translation records are restricted to this folder.<br /> * Go through the suggestions one by one. Accept or reject the suggestion. If the suggestion is accepted, it is submitted. If it is rejected, the existing translation will not be changed. Click on &quot;Next string&quot; without action to skip a suggestion.<br /> <br /> === Checkbox &quot;Needs work&quot; ===<br /> Some teams want to have all new or modified translations reviewed. To make it different from suggestions from anonymous translators without account, they can agree to use the &quot;Needs work&quot; checkbox. In previous versions of Pootle this checkbox was labeled &quot;fuzzy&quot;. So you find instructions to organize review by marking changes as &quot;fuzzy&quot; and let the reviewer &quot;unfuzzy&quot; it after verifying that the translation is correct. To filter for these changes use the filter item &quot;Needs Work&quot;.<br /> <br /> ==Show Pootle Warnings==<br /> [[File:PootleGuide_OverviewDetails.png|250px|thumb|left]]<br /> <br /> Click on the left tab to switch to the Overview. Click on the &#039;&#039;Detail&#039;&#039; link to show, what Pootle considers to be an error.<br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_OverviewShowDetails.png|250px|thumb|left]]<br /> <br /> You see a list with check categories and corresponding number of errors. Find a description of the categories [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/pofilter_tests.html| here]. Please examine especially &lt;code&gt;XML tags&lt;/code&gt; -warnings very carefully. <br /> <br /> Click on the category or on the number to get the list of translation records. Be patient; click on &quot;continue&quot;, when your browser thinks that &quot;a script has stopped working&quot;.<br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_PlaceholderCheckFail.png|250px|thumb|left]]<br /> <br /> The translation record shows too, that a check failed.<br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_PlaceholderCheckExamineText.png|350px|thumb|left]]<br /> And in the screenshot you can see, that Pootle is right in this example.<br /> <br /> In case of a false positive warning, e.g. &quot;Repeated word&quot; warning for the English string &quot;Dot Dot Dash&quot; (which is a line style), you can click on the &quot;No entry&quot;-sign to remove this warning from the record. <br /> &lt;br style=&quot;clear:both;&quot; /&gt;<br /> <br /> [[File:PootleGuide_FilterTypCheck.png|450px|thumb|none]]<br /> <br /> The list of failed records is available too from the &quot;Translate&quot; tab page. Select the item &quot;Checks&quot; from the &quot;Filter by&quot;-drop-down-list at the bottom of the page. It is the last item in the list. Now you get a second drop-down-list to select the check category. The number in brackets tells you how many translation records failed the check.<br /> <br /> ==Review language builds==<br /> <br /> A few weeks before the final release you will get a beta release in your language. Watch the localization mailing list for announcements. Encourage your local community to review the build carefully to catch all translation errors.<br /> <br /> You can build OpenOffice yourself or ask a community member to do it for you, to get a localized build. But prior to building, the translated strings from Pootle have to be reintegrated into trunk. So ask for this on the localization mailing list, if you need an intermediate localized build.<br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Release_Localized_Build&diff=230370 2013-08-22T12:38:58Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Release a Localized Build of Apache OpenOffice}}<br /> <br /> We have agreed to release a localized version of Apache OpenOffice, if the UI is 100% translated.<br /> <br /> And for long-term maintainability we also recommend that:<br /> * the UI is translated to 100% and<br /> * the help is translated to 100% too and<br /> * there is a small team (even just two members) to maintain the translation and ensure QA.<br /> <br /> <br /> <br /> When you are ready, write an issue in [https://issues.apache.org/ooo/enter_bug.cgi| Bugzilla] in the product &#039;&#039;Native-Language&#039;&#039;. Also write an issue, if you later on make changes to the translation and want them to be integrated into the next release.<br /> <br /> {{Documentation/Note|If you edit strings in Pootle you need to explicitly ask on the mailing list, for them to be integrated into OpenOffice. Integration is not automatic.}}<br /> <br /> {{Documentation/HelpNeeded|Please add information how to verify the technical correctness of the translation.}}<br /> <br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina https://wiki.openoffice.org/w/index.php?title=Pootle_User_Guide/Technical_Helpers&diff=230369 2013-08-22T12:38:18Z

<p>Regina: </p> <hr /> <div>{{Documentation/MasterTOC<br /> |booktitle=[[Pootle_User_Guide|Pootle User Guide]]<br /> |toccontent=*[[Pootle_User_Guide/Registration_and_Login|Registration and Login]]<br /> *[[Pootle_User_Guide/Online_Pootle_User_Interface|Overview Pootle UI]]<br /> *[[Pootle_User_Guide/Offline_Translation|Offline Translation]]<br /> *[[Pootle_User_Guide/Quality_Assurance|Quality Assurance]]<br /> *[[Pootle_User_Guide/Release_Localized_Build|Releasing a Localized Build]]<br /> *[[Pootle_User_Guide/Technical_Helpers|Technical Helpers]]<br /> *[[Pootle_User_Guide/Translation_AOO_User_Interface|Translation of the User Interface]]<br /> *[[Pootle_User_Guide/Translation_Built-in_Help|Translation of the Built-in Help]]<br /> *[[Pootle_User_Guide/General_Problems|General Problems]]<br /> }}<br /> <br /> {{DISPLAYTITLE:Technical Helpers}}<br /> __TOC__<br /> <br /> <br /> You will find, that it is a large problem in translating to be sure what part of the UI or the built-in help is shown in the current translation record and the other way round to find a specific string from the installed application in Pootle. The following sections show you some tools.<br /> <br /> ==Using an English User Interface Parallel==<br /> Because the user interface settings in Apache OpenOffice are bound to the user and not to the installation, you can generate a second user, who has an English interface. Then you can open Apache OpenOffice at the same time with an English user interface and with the UI in your language.<br /> <br /> ==== Windows ====<br /> * Download the English language pack and install it. Or the other way round, install an English version and a language pack for your language.<br /> * Create a folder that will contain the user settings for the &quot;English&quot; user, for example &quot;D:\AOOuser_English&quot;.<br /> * Find the file soffice.exe in your installation and create a link to it on your desktop. That should be possible with right click and &quot;Sent To&quot;.<br /> * Open the link to edit it. It should has a field with the link target like &quot;C:\Program Files\OpenOffice 4\program\soffice.exe&quot;.<br /> * Klick into this field and move the cursor to outmost right position and add&lt;br /&gt;&lt;tt&gt;-env:UserInstallation=file:///d:/AOOuser_English.&lt;/tt&gt;&lt;br /&gt;Notice that here a UNC notation with forward slashes is used.<br /> * Close dialog with OK.<br /> * Start OpenOffice with double-click on this link. Goto {{Menu|Tools|Options|Language Settings|Languages}} and set the User Interface to &quot;English (USA)&quot;.<br /> <br /> Dependent on the installation order it might be necessary to change your actual user settings back to your language.<br /> <br /> ===Other Operating Systems===<br /> &#039;&#039;For other operating systems this might be slightly different. Please add necessary descriptions here.&#039;&#039;<br /> <br /> <br /> == Search in the Source Code ==<br /> Translators generally do not have a local copy of the code, but sometimes want to lookup something. These tools might help you.<br /> === Opengrok ===<br /> Example: You see the string &quot;Purple Pipe&quot; as name of a color gradient and wants to know, which files contain this string.<br /> <br /> To search the code use http://opengrok.adfinis-sygroup.org/ That is as powerful tool for developers. For translators this short instruction might be sufficient:<br /> * Select &quot;aoo-trunk&quot; on the right side.<br /> * Enter the search term in the &quot;Full Search&quot; field. The wild cards * and ? are allowed, but not as first character. A phrase has to be enclosed with quotation marks. If you enter several words, they are automatically treated as been connected by AND.<br /> * In the field &quot;File Path&quot; you can enter a part of the path or filename, for example &#039;helpcontent2&#039; for all files of the built-in help. Or you use NOT to exclude those paths, you know to be irrelevant.<br /> {|<br /> |-<br /> | [[File:PootleGuide_OpenGrok.png|400px|thumb|left]]<br /> |-<br /> |}<br /> <br /> In the example you will find that the string &quot;Purple Pipe&quot; is contained in the file &lt;tt&gt;standard.sog&lt;/tt&gt;. Click on the search result to open the file in your browser.&lt;&#039;&#039;See {{bug|122790}}, why this string is not yet (August 2013) in Pootle.&#039;&#039;&gt;<br /> <br /> === ViewVC ===<br /> This tool provides a read access to all files of Apache-SVN. The tree of the OpenOffice project starts in http://svn.apache.org/viewvc/openoffice .<br /> <br /> You will notice, that this is similar to the tree view in the page &quot;Overview&quot; in Pootle. Click on the directory name to open that folder and move down in the tree, click on &quot;Parent directory&quot; to move up.<br /> <br /> A click on a file name gives you its revision log. To view the current file in the browser, click &quot;View&quot; of the top entry; use &quot;Download&quot; to save it to your PC. To go back, up in the tree, use the navigator line at top of the page.<br /> {|<br /> |-<br /> | [[File:PootleGuide_viewvc_localizesdf.png|400px|thumb|left]]<br /> |-<br /> |}<br /> <br /> The .po files for the user interface are based on &lt;tt&gt;localize.sdf&lt;/tt&gt; files. Each language has its own file. Find these files in http://svn.apache.org/viewvc/openoffice/trunk/extras/l10n/source/. These files are about 4MB - 13MB in size. &lt;&#039;&#039;As of August 2013, there are plans to get rid of the localize.sdf files and use .po files directly. Such change was already done in LibreOffice.&#039;&#039;&gt; <br /> <br /> The .po files for the built-in help are based on .xhp files. Find these files in http://svn.apache.org/viewvc/openoffice/trunk/main/helpcontent2/source/text/<br /> <br /> == Make Your Installation Verbose ==<br /> === Extended Tips ===<br /> Set the environment variable HELP_DEBUG=true. It depends on your operating system how to do it. Find details on environment variables for Apache OpenOffice in [[Environment_Variables]].<br /> &lt;div style=&quot;margin-left:3em&quot;&gt;<br /> &#039;&#039;&#039;Tip for Linux&#039;&#039;&#039;<br /> <br /> Find the shell script &lt;tt&gt;soffice&lt;/tt&gt; in your installation of AOO and open it in an editor. Add the lines<br /> &lt;source lang=&quot;bash&quot;&gt;<br /> HELP_DEBUG=true<br /> export HELP_DEBUG<br /> &lt;/source&gt;<br /> A good place to add them is after the already existing environment variable SAL_ENABLE_FILE_LOCKING.<br /> &lt;/div&gt;<br /> <br /> Now your extended tips in AOO look like this<br /> <br /> [[File:PootleGuilde_ExtendedTipExample.png|300px|thumb|none]]<br /> <br /> Notice there is an additional part under the --- divider. The tip shows now the helpID of the item and the internal module. You can use the last part after the colon to search for it in Pootle, here search for CBX_PREVIEW for example.<br /> <br /> Using extended tips is not enabled in the defaults. Use one of these ways to show extended tips<br /> * Enable them in {{Menu|Tools|Options|OpenOffice|General}}<br /> * In the toolbar &quot;Standard&quot; set the icon &quot;What&#039;s this?&quot; to visible. Click the icon and hover with the mouse over an UI element. Click again to leave this mode.<br /> * Customize a toolbar and add the item &quot;Extended Help&quot; to it. Find it in the category &quot;Application&quot;. This command has no icon assigned. To connect an icon to the command or change the command name to e.g. &quot;Help+&quot; click on the button &quot;Modify&quot; in the customization dialog and select the corresponding item. With this command you can easily toggle between extended tips on/off. Use a similar way to assign a shortcut key to this command.<br /> <br /> === Transforming the Style of the Built-in Help ===<br /> {{bug|56321}} &quot;Instructions on Help review&quot; provides three tools to make the structure of the build-in help visible.<br /> <br /> ; allfiles.tree: It adds an entry &quot;All Help Documents for Debug Purpose&quot; to the &quot;Content&quot; page of the build-in help. This new section shows the helpfiles not by title but by filename and in the same hierarchical order as in Pootle.<br /> ; default.css: This file colors the help texts in a way, that you can easily see, what kind of content it is.<br /> ; main_transform.xsl: This file causes, that in the build-in help the helpIDs are shown in addition to the text. With the information about file and location from Pootle, you can now easily identify the string in the help and see its context.<br /> <br /> To transform your help do this:<br /> # Get the newest versions of the files allfiles.tree, default.css, and main_transform.xsl from {{bug|56321}}.<br /> # Close your OpenOffice including the Quickstarter.<br /> # Locate the folder &quot;help&quot; in your installation. For my Windows 7 it is the path C:\Program Files\OpenOffice 4\help. For you it should be similar.<br /> # You should see a file main_transform.xsl in this folder. Rename it to e.g. main_transform.xsl.orig and copy the corresponding file form the issue here.<br /> # You should see subfolders that are named as the language codes. Open the folder of the language, for which you will produce the translation.<br /> # You should see some files with file extension .tree. Copy the file allfiles.tree here.<br /> # Locate the file default.css in this folder and rename it to e.g. default.css.orig. Copy the corresponding file from the issue here.<br /> # Start OpenOffice and open a help page. At top of the page you will see a short explanation about the meaning of the colors and styles.<br /> <br /> &lt;&#039;&#039;Some new files are missing in allfiles.tree. But I don&#039;t know yet, whether the file has to be updated manually or a script for generating the file exists.&#039;&#039;&gt;<br /> <br /> == Getting a KeyID-Build ==<br /> &lt;&#039;&#039;ToDO: Add screenshot&#039;&#039;&gt;<br /> &lt;&#039;&#039;ToDo: Consolidate with the existing page [[KeyID_Build]].&#039;&#039;&gt;<br /> <br /> A keyID-build is a special version, where each string in the UI has got a number in front of it, the keyID. To get these numbers a pseudo language &quot;kid&quot; is used. This pseudo language has its own localize.sdf file, same as all real languages. This file contains a database table. Each row is about a UI string. It connects the strings with the identifiers used in the source.<br /> <br /> A developer gets such a keyID-build by using the configure switch, e.g. &lt;code&gt;--with-lang=&quot;de kid&quot;&lt;/code&gt;. The setting in the example would build an English AOO (the default), a German AOO, and an AOO with keyIDs. <br /> <br /> If you want to use such a keyID-build and cannot build it yourself, ask on the mailing list. There is likely someone, who can build it for you, or perhaps a build bot can be configured to deliver it.<br /> <br /> [[Category:Localization]]<br /> <br /> [[de:DE/Pootle_User_Guide]]<br /> [[it:IT/Localizzazione/Pootle]]<br /> [[ja:JA/translation/Pootle_User_Guide]]<br /> [[ko:KO/Pootle 사용자 가이드]]<br /> [[nl:NL/Localisatie/Pootle gebruikersgids]]</div>

Regina