https://wiki.openoffice.org/w/api.php?action=feedcontributions&feedformat=atom&user=Deneb+alphaApache OpenOffice Wiki - User contributions [en]2026-06-04T00:30:53ZUser contributionsMediaWiki 1.35.14https://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156832IT/Documentation/How Tos/Regular Expressions in Writer2010-02-09T19:49:26Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
{{DISPLAYTITLE:Espressioni regolari in Writer}}<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il principio di funzionamento delle espressioni regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
Se non si vuole apprendere il funzionamento esatto delle espressioni regolari, ma si vuole soltanto servirsene, questi esempi potrebbero tornare utili. Inseriteli nel 'Campo di ricerca', assicurandovi che le espressioni regolari siano selezionate.<br />
<br />
* <b>colore|colori</b> trova <b>colore</b> e <b>colori</b><br />
* <b>sep.rate</b> trova <b>sep</b> seguito da un qualunque carattere e poi da <b>rate</b> - ad esempio <b>separate</b>, <b>seperate</b>, ma anche <b>sepXrate</b><br />
* <b>sep[ae]rate</b> trova <b>separate</b> e <b>seperate</b> - <b>[ae]</b> significa che sarà cercato sia <b>a</b> sia <b>e</b><br />
* <b>sapere?</b> trova <b>saper</b> e <b>sapere</b> - la <b>e</b> è opzionale perché seguita da un punto interrogativo<br />
* <b>s\></b> trova la <b>s</b> alla fine di una parola<br />
* <b>\<.</b> trova la prima lettera di una parola.<br />
* <b>^.</b> trova la prima lettera di un paragrafo.<br />
* <b>^$</b> trova un paragrafo vuoto<br />
<br />
<br />
== Espressioni regolari applicate in OpenOffice.org ==<br />
In OpenOffice.org, le espressioni regolari dividono il testo da ricercare in porzioni, per poi esaminare ogni porzione separatamente.<br />
<br />
<br />
In Writer, il testo è suddiviso in paragrafi. Nell'esempio, cercando ''' x.*z''', la '''x''' alla fine del paragrafo e la '''z''' all'inizio del secondo non saranno visualizzate tra i risultati (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3_it.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=File:Regex_howto_3_it.png&diff=156831File:Regex howto 3 it.png2010-02-09T19:13:11Z<p>Deneb alpha: utilizzo delle espressioni regolari</p>
<hr />
<div>utilizzo delle espressioni regolari</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156830IT/Documentation/How Tos/Regular Expressions in Writer2010-02-09T19:10:29Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
{{DISPLAYTITLE:Espressioni regolari in Writer}}<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il principio di funzionamento delle espressioni regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
Se non si vuole apprendere il funzionamento esatto delle espressioni regolari, ma si vuole soltanto servirsene, questi esempi potrebbero tornare utili. Inseriteli nel 'Campo di ricerca', assicurandovi che le espressioni regolari siano selezionate.<br />
<br />
* <b>colore|colori</b> trova <b>colore</b> e <b>colori</b><br />
* <b>sep.rate</b> trova <b>sep</b> seguito da un qualunque carattere e poi da <b>rate</b> - ad esempio <b>separate</b>, <b>seperate</b>, ma anche <b>sepXrate</b><br />
* <b>sep[ae]rate</b> trova <b>separate</b> e <b>seperate</b> - <b>[ae]</b> significa che sarà cercato sia <b>a</b> sia <b>e</b><br />
* <b>sapere?</b> trova <b>saper</b> e <b>sapere</b> - la <b>e</b> è opzionale perché seguita da un punto interrogativo<br />
* <b>s\></b> trova la <b>s</b> alla fine di una parola<br />
* <b>\<.</b> trova la prima lettera di una parola.<br />
* <b>^.</b> trova la prima lettera di un paragrafo.<br />
* <b>^$</b> trova un paragrafo vuoto<br />
<br />
<br />
== Espressioni regolari applicate in OpenOffice.org ==<br />
In OpenOffice.org, le espressioni regolari dividono il testo da ricercare in porzioni, per poi esaminare ogni porzione separatamente.<br />
<br />
<br />
In Writer, il testo è suddiviso in paragrafi. Ad esempio, ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3_it.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156554IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T23:36:45Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il principio di funzionamento delle espressioni regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
Se non si vuole apprendere il funzionamento esatto delle espressioni regolari, ma si vuole soltanto servirsene, questi esempi potrebbero tornare utili. Inseriteli nel 'Campo di ricerca', assicurandovi che le espressioni regolari siano selezionate.<br />
<br />
* <b>colore|colori</b> trova <b>colore</b> e <b>colori</b><br />
* <b>sep.rate</b> trova <b>sep</b> seguito da un qualunque carattere e poi da <b>rate</b> - ad esempio <b>separate</b>, <b>seperate</b>, ma anche <b>sepXrate</b><br />
* <b>sep[ae]rate</b> trova <b>separate</b> e <b>seperate</b> - <b>[ae]</b> significa che sarà cercato sia <b>a</b> sia <b>e</b><br />
* <b>sapere?</b> trova <b>saper</b> e <b>sapere</b> - la <b>e</b> è opzionale perché seguita da un punto interrogativo<br />
* <b>s\></b> trova la <b>s</b> alla fine di una parola<br />
* <b>\<.</b> trova la prima lettera di una parola.<br />
* <b>^.</b> trova la prima lettera di un paragrafo.<br />
* <b>^$</b> trova un paragrafo vuoto<br />
<br />
<br />
== Espressioni regolari applicate in OpenOffice.org ==<br />
In OpenOffice.org, le espressioni regolari dividono il testo da ricercare in porzioni per poi esaminare ogni porzione separatamente.<br />
<br />
<br />
In Writer, il testo è suddiviso in paragrafi. Ad esempio, ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156552IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T23:34:24Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il principio di funzionamento delle espressioni regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
Se non si vuole apprendere il funzionamento esatto delle espressioni regolari, ma si vuole soltanto servirsene, questi esempi potrebbero tornare utili. Inseriteli nel 'Campo di ricerca', assicurandovi che le espressioni regolari siano selezionate.<br />
<br />
* <b>colore|colori</b> trova <b>colore</b> e <b>colori</b><br />
* <b>sep.rate</b> trova <b>sep</b> seguito da un qualunque carattere e poi da <b>rate</b> - ad esempio <b>separate</b>, <b>seperate</b>, ma anche <b>sepXrate</b><br />
* <b>sep[ae]rate</b> trova <b>separate</b> e <b>seperate</b> - <b>[ae]</b> significa che sarà cercato sia <b>a</b> sia <b>e</b><br />
* <b>sapere?</b> trova <b>saper</b> e <b>sapere</b> - la <b>e</b> è opzionale perché seguita da un punto interrogativo<br />
* <b>s\></b> trova la <b>s</b> alla fine di una parola<br />
* <b>\<.</b> trova la prima lettera di una parola.<br />
* <b>^.</b> trova la prima lettera di un paragrafo.<br />
* <b>^$</b> trova un paragrafo vuoto<br />
<br />
<br />
== Espressioni regolari applicate in OpenOffice.org ==<br />
In OpenOffice.org, le espressioni regolari dividono il testo da ricercare in porzioni per poi esaminare ogni porzione separatamente.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156551IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T23:29:11Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il principio di funzionamento delle espressioni regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
Se non si vuole apprendere il funzionamento esatto delle espressioni regolari, ma si vuole soltanto servirsene, questi esempi potrebbero tornare utili. Inseriteli nel 'Campo di ricerca', assicurandovi che le espressioni regolari siano selezionate.<br />
<br />
* <b>colore|colori</b> trova <b>colore</b> e <b>colori</b><br />
* <b>sep.rate</b> trova <b>sep</b> seguito da un qualunque carattere e poi <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, ma anche <b>sepXrate</b><br />
* <b>sep[ae]rate</b> trova <b>separate</b> e <b>seperate</b> - <b>[ae]</b> significa che sarà cercato sia <b>a</b> sia <b>e</b><br />
* <b>sapere?</b> trova <b>saper</b> e <b>sapere</b> - la <b>e</b> è opzionale perché seguita da un punto interrogativo<br />
* <b>s\></b> trova la <b>s</b> alla fine di una parola<br />
* <b>\<.</b> trova la prima lettera di una parola.<br />
* <b>^.</b> trova la prima lettera di un paragrafo.<br />
* <b>^$</b> trova un paragrafo vuoto<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156488IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T19:24:34Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il principio di funzionamento delle espressioni regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
Se non si vuole apprendere il funzionamento esatto delle espressioni regolari, ma si vuole soltanto servirsene, questi esempi potrebbero tornare utili. Inseriteli nella 'Campo di ricerca', assicurandovi che le espressioni regolari siano selezionate.<br />
<br />
* <b>color|colour</b> finds <b>color</b> and <b>colour</b><br />
* <b>sep.rate</b> finds <b>sep</b> then any character then <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, and indeed <b>sepXrate</b><br />
* <b>sep[ae]rate</b> finds <b>separate</b> and <b>seperate</b> - <b>[ae]</b> means either an <b>a</b> or an <b>e</b><br />
* <b>changed?</b> finds <b>change</b> and <b>changed</b> - the <b>d</b> is optional because it is followed by a question mark<br />
* <b>s\></b> finds the <b>s</b> at the end of a word<br />
* <b>\<.</b> finds the first letter of a word.<br />
* <b>^.</b> finds the first letter of a paragraph.<br />
* <b>^$</b> finds an empty paragraph<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156478IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T14:18:21Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il principio di funzionamento delle espressionii regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
If you don't want to find out exactly how regular expressions work, but just want to get a job done, you might find these common examples useful. Enter them in the 'Search for' box, and make sure that regular expressions are selected.<br />
<br />
* <b>color|colour</b> finds <b>color</b> and <b>colour</b><br />
* <b>sep.rate</b> finds <b>sep</b> then any character then <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, and indeed <b>sepXrate</b><br />
* <b>sep[ae]rate</b> finds <b>separate</b> and <b>seperate</b> - <b>[ae]</b> means either an <b>a</b> or an <b>e</b><br />
* <b>changed?</b> finds <b>change</b> and <b>changed</b> - the <b>d</b> is optional because it is followed by a question mark<br />
* <b>s\></b> finds the <b>s</b> at the end of a word<br />
* <b>\<.</b> finds the first letter of a word.<br />
* <b>^.</b> finds the first letter of a paragraph.<br />
* <b>^$</b> finds an empty paragraph<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156477IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T14:16:11Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
Digitando ''' xxx''' nel box '''Sostituisci con''' e cliccando il bottone '''Sostituisci tutto''', il testo diventerà '<b>xxx</b>', '<b>xxx</b>nore', ''''<b>xxx</b>'''ugio', ''''<b>xxx</b>'''iovanni' <br />
<br />
<br />
Tutto ciò potrà sembrare poco utile ma mostra il princiopio di funzionamento delle espressionii regolari. Tali funzioni saranno spiegate meglio attraverso altri esempi di uso della funzionalità '''Trova e sostituisci'''.<br />
<br />
== Quello che c'è da sapere sulle espressioni regolari ==<br />
If you don't want to find out exactly how regular expressions work, but just want to get a job done, you might find these common examples useful. Enter them in the 'Search for' box, and make sure that regular expressions are selected.<br />
<br />
* <b>color|colour</b> finds <b>color</b> and <b>colour</b><br />
* <b>sep.rate</b> finds <b>sep</b> then any character then <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, and indeed <b>sepXrate</b><br />
* <b>sep[ae]rate</b> finds <b>separate</b> and <b>seperate</b> - <b>[ae]</b> means either an <b>a</b> or an <b>e</b><br />
* <b>changed?</b> finds <b>change</b> and <b>changed</b> - the <b>d</b> is optional because it is followed by a question mark<br />
* <b>s\></b> finds the <b>s</b> at the end of a word<br />
* <b>\<.</b> finds the first letter of a word.<br />
* <b>^.</b> finds the first letter of a paragraph.<br />
* <b>^$</b> finds an empty paragraph<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156475IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T13:54:19Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
Dalla finestra, scegliere '''Più Opzioni''' e selezionare la voce '''Espressioni regolare'''<br />
<br />
Nella casella di ricerca inserire '''s.g '''- il punto significa 'ogni singolo carattere'.<br />
<br />
<br />
Cliccando il bottone Cerca tutto saranno evidenziate tutte la parole che contengono una '''s''' seguita da un carattere qualsiasi il cui successore sia però una '''g''', ad esempio ''''sig'''' o '<b>sig</b>nore' o '''seg'''ugio' o ''''s giovanni'''' (in questo ultimo esempio una '''s''' è seguita da uno '''spazio''' che a sua volta è seguito da una '''g''' - lo spazio è un carattere).<br />
<br />
<br />
If you type''' xxx''' into the '''Replace with''' box, and click the '''Replace All''' button, these become '<b>xxx</b>', 'hot<b>xxx</b>', 'b'''xxx'''e', 'you'''xxx'''og' <br />
<br />
<br />
That may not be very useful, but it shows the principle. We'll continue to use the '''Find and Replace''' dialog to explain in more detail.<br />
<br />
== The least you need to know about regular expressions ==<br />
If you don't want to find out exactly how regular expressions work, but just want to get a job done, you might find these common examples useful. Enter them in the 'Search for' box, and make sure that regular expressions are selected.<br />
<br />
* <b>color|colour</b> finds <b>color</b> and <b>colour</b><br />
* <b>sep.rate</b> finds <b>sep</b> then any character then <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, and indeed <b>sepXrate</b><br />
* <b>sep[ae]rate</b> finds <b>separate</b> and <b>seperate</b> - <b>[ae]</b> means either an <b>a</b> or an <b>e</b><br />
* <b>changed?</b> finds <b>change</b> and <b>changed</b> - the <b>d</b> is optional because it is followed by a question mark<br />
* <b>s\></b> finds the <b>s</b> at the end of a word<br />
* <b>\<.</b> finds the first letter of a word.<br />
* <b>^.</b> finds the first letter of a paragraph.<br />
* <b>^$</b> finds an empty paragraph<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156467IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T09:45:41Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== Un semplice esempio ==<br />
Se non si ha molta dimestichezza con le espressioni regolari, si consiglia di fare pratica in Writer piuttosto che in Calc.<br />
<br />
In Writer, aprire il menu di dialogo '''Trova e sostituisci''' dal menu Modifica.<br />
<br />
On the dialog, choose '''More Options''' and tick the '''Regular Expressions''' box<br />
<br />
In the Search box enter '''r.d '''- the dot here means 'any single character'.<br />
<br />
<br />
Clicking the Find All button will now find all the places where an '''r''' is followed by another character followed by a '''d''', for instance ''''red'''' or 'hot<b>rod</b>' or 'b'''rid'''e' or 'you'''r d'''og' (this last example is '''r''' followed by a '''space''' followed by '''d''' - the space is a character).<br />
<br />
<br />
If you type''' xxx''' into the '''Replace with''' box, and click the '''Replace All''' button, these become '<b>xxx</b>', 'hot<b>xxx</b>', 'b'''xxx'''e', 'you'''xxx'''og' <br />
<br />
<br />
That may not be very useful, but it shows the principle. We'll continue to use the '''Find and Replace''' dialog to explain in more detail.<br />
<br />
== The least you need to know about regular expressions ==<br />
If you don't want to find out exactly how regular expressions work, but just want to get a job done, you might find these common examples useful. Enter them in the 'Search for' box, and make sure that regular expressions are selected.<br />
<br />
* <b>color|colour</b> finds <b>color</b> and <b>colour</b><br />
* <b>sep.rate</b> finds <b>sep</b> then any character then <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, and indeed <b>sepXrate</b><br />
* <b>sep[ae]rate</b> finds <b>separate</b> and <b>seperate</b> - <b>[ae]</b> means either an <b>a</b> or an <b>e</b><br />
* <b>changed?</b> finds <b>change</b> and <b>changed</b> - the <b>d</b> is optional because it is followed by a question mark<br />
* <b>s\></b> finds the <b>s</b> at the end of a word<br />
* <b>\<.</b> finds the first letter of a word.<br />
* <b>^.</b> finds the first letter of a paragraph.<br />
* <b>^$</b> finds an empty paragraph<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156465IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T09:24:13Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1_it.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
All'apertura della finestra di dialogo occorre controllare lo stato dell'opzione delle espressioni regolari, come impostazione predefinita è disabilitata.<br />
<br />
== un semplice esempio ==<br />
If you have little or no experience of regular expressions, you may find it easiest to study them in Writer rather than say Calc.<br />
<br />
In Writer, bring up the '''Find and Replace''' dialog from the Edit menu.<br />
<br />
On the dialog, choose '''More Options''' and tick the '''Regular Expressions''' box<br />
<br />
In the Search box enter '''r.d '''- the dot here means 'any single character'.<br />
<br />
<br />
Clicking the Find All button will now find all the places where an '''r''' is followed by another character followed by a '''d''', for instance ''''red'''' or 'hot<b>rod</b>' or 'b'''rid'''e' or 'you'''r d'''og' (this last example is '''r''' followed by a '''space''' followed by '''d''' - the space is a character).<br />
<br />
<br />
If you type''' xxx''' into the '''Replace with''' box, and click the '''Replace All''' button, these become '<b>xxx</b>', 'hot<b>xxx</b>', 'b'''xxx'''e', 'you'''xxx'''og' <br />
<br />
<br />
That may not be very useful, but it shows the principle. We'll continue to use the '''Find and Replace''' dialog to explain in more detail.<br />
<br />
== The least you need to know about regular expressions ==<br />
If you don't want to find out exactly how regular expressions work, but just want to get a job done, you might find these common examples useful. Enter them in the 'Search for' box, and make sure that regular expressions are selected.<br />
<br />
* <b>color|colour</b> finds <b>color</b> and <b>colour</b><br />
* <b>sep.rate</b> finds <b>sep</b> then any character then <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, and indeed <b>sepXrate</b><br />
* <b>sep[ae]rate</b> finds <b>separate</b> and <b>seperate</b> - <b>[ae]</b> means either an <b>a</b> or an <b>e</b><br />
* <b>changed?</b> finds <b>change</b> and <b>changed</b> - the <b>d</b> is optional because it is followed by a question mark<br />
* <b>s\></b> finds the <b>s</b> at the end of a word<br />
* <b>\<.</b> finds the first letter of a word.<br />
* <b>^.</b> finds the first letter of a paragraph.<br />
* <b>^$</b> finds an empty paragraph<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=File:Regex_howto_1_it.png&diff=156464File:Regex howto 1 it.png2010-02-07T09:20:31Z<p>Deneb alpha: posizione della casella di controllo delle espressioni regolari</p>
<hr />
<div>posizione della casella di controllo delle espressioni regolari</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=IT/Documentation/How_Tos/Regular_Expressions_in_Writer&diff=156463IT/Documentation/How Tos/Regular Expressions in Writer2010-02-07T08:59:43Z<p>Deneb alpha: Created page with 'fr:Documentation/FR/Expressions_Regulieres_dans_Writer nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer == Introduzione == In pratica, le espressioni regolari …' (checkpoint save)</p>
<hr />
<div>[[fr:Documentation/FR/Expressions_Regulieres_dans_Writer]]<br />
[[nl:Documentation/nl/How_Tos/Reguliere_expressies_in_Writer]]<br />
<br />
== Introduzione ==<br />
In pratica, le espressioni regolari sono un modo intelligente per trovare e sostituire del testo (come per i caratteri 'jolly'). Le espressioni regolari possono essere sia potenti sia complesse, ed un utente inesperto può facilmente commettere errori. Descriviamo l'uso delle espressioni regolari in OpenOffice.org al fine di essere abbastanza chiari per i principianti, analizzando dettagliatamente gli aspetti che possono creare confusione negli utenti più esperti.<br />
<br />
<br />
Un utilizzo tipico di espressioni regolari è cercare del testo in un documento di Writer; per esempio per individuare tutte le occorrenze di '''uomo''' o '''donna''' nel documento, è possibile cercare usando un'espressione regolare che trovi entrambe le parole.<br />
<br />
<br />
Le espressioni regolari sono molto comuni in alcuni settori dell'informatica, e sono spesso note come regex o regexp. Non tutte le regex sono scritte allo stesso modo - quindi, una lettura del manuale è una scelta ragionevole.<br />
<br />
<br />
== Quando utilizzare espressioni regolari in OOo ==<br />
In Writer:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Modifica - Modifiche - comando Accetta o annulla (Tabella dei filtri)<br />
<br />
<br />
In Calc:<br />
<br />
*Modifica - finestra Cerca e sostituisci<br />
<br />
*Dati - Filtro - Filtro standard e Filtro speciale<br />
<br />
*Alcune funzioni come SOMMA.SE, CERCA<br />
<br />
<br />
In Base:<br />
<br />
*Comando Trova record<br />
<br />
<br />
Le finestre di dialogo visualizzate quando si utilizzano questi comandi danno generalmente la possibilità di utilizzare le espressioni regolari (per impostazione predefinita questa funzionalità è disattivata). Ad esempio<br />
<br />
<center>[[Image:Regex_howto_1.png|posizione della casella di controllo delle espressioni regolari]]</center><br />
<br />
<br />
You should check the status of the regular expression option each time you bring up the dialog, as it defaults to 'off'.<br />
<br />
== A simple example ==<br />
If you have little or no experience of regular expressions, you may find it easiest to study them in Writer rather than say Calc.<br />
<br />
In Writer, bring up the '''Find and Replace''' dialog from the Edit menu.<br />
<br />
On the dialog, choose '''More Options''' and tick the '''Regular Expressions''' box<br />
<br />
In the Search box enter '''r.d '''- the dot here means 'any single character'.<br />
<br />
<br />
Clicking the Find All button will now find all the places where an '''r''' is followed by another character followed by a '''d''', for instance ''''red'''' or 'hot<b>rod</b>' or 'b'''rid'''e' or 'you'''r d'''og' (this last example is '''r''' followed by a '''space''' followed by '''d''' - the space is a character).<br />
<br />
<br />
If you type''' xxx''' into the '''Replace with''' box, and click the '''Replace All''' button, these become '<b>xxx</b>', 'hot<b>xxx</b>', 'b'''xxx'''e', 'you'''xxx'''og' <br />
<br />
<br />
That may not be very useful, but it shows the principle. We'll continue to use the '''Find and Replace''' dialog to explain in more detail.<br />
<br />
== The least you need to know about regular expressions ==<br />
If you don't want to find out exactly how regular expressions work, but just want to get a job done, you might find these common examples useful. Enter them in the 'Search for' box, and make sure that regular expressions are selected.<br />
<br />
* <b>color|colour</b> finds <b>color</b> and <b>colour</b><br />
* <b>sep.rate</b> finds <b>sep</b> then any character then <b>rate</b> - eg <b>separate</b>, <b>seperate</b>, and indeed <b>sepXrate</b><br />
* <b>sep[ae]rate</b> finds <b>separate</b> and <b>seperate</b> - <b>[ae]</b> means either an <b>a</b> or an <b>e</b><br />
* <b>changed?</b> finds <b>change</b> and <b>changed</b> - the <b>d</b> is optional because it is followed by a question mark<br />
* <b>s\></b> finds the <b>s</b> at the end of a word<br />
* <b>\<.</b> finds the first letter of a word.<br />
* <b>^.</b> finds the first letter of a paragraph.<br />
* <b>^$</b> finds an empty paragraph<br />
<br />
<br />
== How regular expressions are applied in OpenOffice.org ==<br />
OpenOffice.org regular expressions appear to divide the text to be searched into portions and examine each portion separately.<br />
<br />
<br />
In Writer, text appears to be divided into paragraphs. For example ''' x.*z''' will not match '''x''' at the end of a paragraph with '''z''' beginning the next paragraph (''' x.*z''' means '''x''' then any or no characters then '''z'''). Paragraphs seem to be treated separately (although we discuss some special cases at the end of this HowTo).<br />
<br />
<br />
<center>[[Image:Regex_howto_3.png|the scope of regular expressions]]</center><br />
<br />
<br />
In addition Writer considers each table cell and each text frame separately. Text frames are examined after all the other text / table cells on all pages have been examined.<br />
<br />
<br />
In the Find & Replace dialog, regular expressions may be used in the <b>Search for</b> box. In general they may <b>not</b> be used in the <b>Replace</b> with box. The exceptions are discussed later.<br />
<br />
<br />
== Literal characters ==<br />
If your regular expression contains characters other than the so-called 'special characters' '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>''' then those characters are matched literally. <br />
<br />
<br />
''For example:'' '''red''' matches '''red''' '''red'''raw and F'''red'''die.<br />
<br />
<br />
OpenOffice.org allows you to choose whether you care if a character is 'UPPER CASE' or 'lower case'. If you tick the box to 'match case' on the '''Find and Replace''' dialog, then '''red''' will not match '''Red''' or F'''RED'''<nowiki>; if you un-tick that box then the case is ignored and both will be matched.</nowiki><br />
<br />
<br />
== Special characters ==<br />
The special characters are '''<nowiki>. ^ $ * + ? \ [ ( { |</nowiki>'''<br />
<br />
<br />
They have special meanings in a regular expression, as we're about to describe.<br />
<br />
<br />
If you wish to match one of these characters literally, place a backslash ''''<nowiki>\</nowiki>'''' before it. <br />
<br />
<br />
''For example:'' to match '''$100''' use '''\$100''' - the '''\$''' is taken to mean '''$''' .<br />
<br />
<br />
== Single character match . ? ==<br />
The dot '<b>.</b>' special character stands for any single character (except newline).<br />
<br />
<br />
''For example:'' '''r.d''' matches '<b>red</b>' and 'hot<b>rod</b>' and 'b<b>rid</b>e' and 'you<b>r d</b>og' <br />
<br />
<br />
The question mark '<b>?</b>' special character means 'match zero or one of the preceding character' - or 'match the preceding character if it is found'.<br />
<br />
<br />
''For example:'' '''rea?d''' matches '<b>red</b>' and '<b>read</b>' - '<b>a?</b>' means 'match a single a if there is one'.<br />
<br />
<br />
Special characters can be used in combination with each other. A dot followed by a question mark means 'match zero or one of any single chacter'.<br />
<br />
<br />
''For example:'' '''star.?ing''' matches '<b>staring</b>', '<b>starring</b>', '<b>starting</b>', and '<b>starling</b>', but not '<b>startling</b>'<br />
<br />
== Repeating match + * {m,n} ==<br />
The plus <b>'+'</b> special character means 'match one or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>re+d</b> matches <b>'red'</b> and <b>'reed'</b> and <b>'reeeeed'</b> - <b>e+</b> means match one or more <b>e</b>'s.<br />
<br />
<br />
The star <b>'<nowiki>*</nowiki>'</b> special character means 'match zero or more of the preceding character'.<br />
<br />
<br />
''For example:'' <b>rea*d</b> matches <b>'red'</b> and <b>'read'</b> and <b>'reaaaaaaad'</b> - <b>'a*'</b> means match zero or more <b>a</b>'s .<br />
<br />
<br />
A common use for <b>'<nowiki>*</nowiki>'</b> is after the dot character - ie <b>'<nowiki>.*</nowiki>'</b> which means 'any or no characters'.<br />
<br />
''For example:'' <b>rea.*d</b> matches <b>'read'</b> and <b>'reaXd'</b> and <b>'reaYYYYd'</b> but not - <b>'red'</b> or <b>'reXd'</b><br />
<br />
Use the star <b>'<nowiki>*</nowiki>'</b> with caution; it will grab everything it can:<br />
<br />
<br />
''For example:'' <b>'r.*d'</b> matches <b>'red'</b> but in Writer if your paragraph is actually 'The referee showed him the red card again' the match found is <b>'referee showed him the red card'</b> - that is, the first <b>'r'</b> and the last possible <b>'d'</b>. Regular expressions are greedy by nature.<br />
<br />
<br />
You may specify how many times you wish the match to be repeated, with curly brackets <b>{ }</b>. For example <b>a{1,4}rgh!</b> will match <b>argh!</b>, <b>aargh!</b>, <b>aaargh!</b> and <b>aaaargh!</b> - in other words between 1 and 4 <b>a</b>'s then <b>rgh!</b>.<br />
<br />
Also note that <b>a{3}rgh!</b> will match precisely 3 <b>a</b>'s, ie <b>aaargh!</b>, and <b>a{2,}rgh!</b> (with a comma) will match at least 2 <b>a</b>'s, for example <b>aargh!</b> and <b>aaaaaaaargh!</b>.<br />
<br />
== Positional match ^ $ \< \> ==<br />
The circumflex <b>'^'</b> special character means 'match at the beginning of the text'.<br />
<br />
The dollar <b>'$'</b> special character means 'match at the end of the text'.<br />
<br />
<br />
Remember that OpenOffice.org regular expressions divide up the text to be searched - each paragraph in Writer is examined separately.<br />
<br />
''For example:'' <b>^red</b> matches <b>'red'</b> at the start of a paragraph (<b>red</b> night shepherd's delight).<br />
<br />
''For example:'' <b>red$</b> matches <b>'red'</b> at the end of a paragraph (he felt himself go <b>red</b>)<br />
<br />
''For example:'' <b>^red$</b> matches inside a table cell that contains just <b>'red'</b><br />
<br />
<br />
In addition a hard line break (entered by Shift-Enter) is considered the beginning / end of text, and will allow a <b>^</b> or <b>$</b> match.<br />
<br />
<br />
The backslash <b>'\'</b> special character gives special meaning to the character pairs <b>'\<'</b> and <b>'\>'</b>, namely 'match at the beginning of a word', and 'match at the end of a word'<br />
<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches red at the beginning of a word (she went <b>red</b>der than he did).<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches red at the end of a word (although neither of them ca<b>red</b> much.)<br />
<br />
<br />
The test used to define the beginning/end of a word seems to be that the previous/next character is a space, underscore (_), tab, newline, paragraph mark or any non-alphanumeric character.<br />
<br />
''For example:'' <b><nowiki>\<red</nowiki></b> matches 'person@<b>red</b>iton.com'<br />
<br />
''For example:'' <b><nowiki>red\></nowiki></b> matches 'I said, "No-one da<b>red</b>" '<br />
<br />
<br />
== Alternative matches | [...] ==<br />
The pipe character '<b>|</b>' is a special character which allows the expression either side of the '<b>|</b>' to match.<br />
<br />
<br />
''For example:'' <b>red|blue</b> matches <b>'red'</b> and <b>'blue'</b> <br />
<br />
<br />
Unfortunately, certain expressions when used ''after'' a pipe are not evaluated. This is so far known to affect '''^''' and backreferences, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=46165 issue 46165]<br />
<br />
<br />
''For example:'' <b>^red|blue</b> matches paragraphs beginning with <b>'red'</b> and any occurrence of <b>'blue'</b>, but <b>blue|^red</b> incorrectly matches only any occurrence of <b>'blue'</b>, failing to match paragraphs beginning with <b>'red'</b><br />
<br />
<br />
The open square brackets character <b>[</b> is a special character. Characters enclosed in square brackets are treated as alternatives - any one of them may match. You can also include ranges of characters, such as '''a-z''' or '''0-9''', rather than typing in '''abcdefghijklmnopqrstuvwxyz''' or '''0123456789'''<br />
<br />
<br />
''For example:'' '''<nowiki>r[eo]d </nowiki>'''matches''' 'red' '''and''' 'rod'''' but not ''''rid''''<br />
<br />
''For example: '''''<nowiki>[m-p]ut</nowiki>''' matches ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
''For example: '''''<nowiki>[hm-p]ut</nowiki>''' matches ''''hut'''' and ''''mut'''' and ''''nut'''' and ''''out'''' and ''''put''''<br />
<br />
<br />
Special characters within alternative match square brackets do not have the same special meanings. The only characters which do have special meanings are <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b>, and the meanings are:<br />
<br />
* <b>]</b> - a closing square bracket ends the alternative match set <b><nowiki>[abcdef]</nowiki></b><br />
* <b>-</b> - a hyphen indicates a range of characters, as we've seen, eg <b><nowiki>[0-9]</nowiki></b><br />
* <b>^</b> - if the caret is the first character in the square brackets, it negates the search. ''For example'' <b><nowiki>[^a-dxyz]</nowiki></b> matches any character except <b>abcdxyz</b>.<br />
* <b><nowiki>\</nowiki></b> - the backslash is used to allow <b>]</b>, <b>-</b>, <b>^</b> and <b><nowiki>\</nowiki></b> to be used literally in square brackets, and to allow hexadecimal codes. ''For example'', <b>\]</b> stands for a literal closing square bracket, so <b>[[\]a]</b> will match an opening square bracket <b>[</b>, a closing square bracket <b>]</b> or an <b>a</b>. <b>\\</b> stands for a literal backslash. <b>\x0009</b> stands for a tab character.<br />
<br />
Just to re-emphasise: these are the meanings of these characters inside square brackets, and any other characters are treated literally. ''For example'' <b>[\t ]</b> will match a '<b>t</b>' or a space - <b>not</b> a tab or a space. Use <b>[\x0009 ]</b> to match a tab or a space.<br />
<br />
== POSIX bracket expressions [:alpha:] [:digit:] etc.. ==<br />
There is much confusion in the OpenOffice.org community about these. The Help itself is also far from clear.<br />
<br />
There are a number of 'POSIX bracket expressions' (sometimes called 'POSIX character classes') available in OpenOffice.org regular expressions, of the form <b>[:classname:]</b> which allow a match with any of the characters in that class. For instance <b><nowiki>[:digit:]</nowiki></b> stands for any of the digits <b>0123456789</b>.<br />
<br />
These (by definition) may <b>only appear inside the square brackets</b> of an alternative match - so a valid syntax would be <b><nowiki>[abc[:digit:]]</nowiki></b>, which should match '''a''', '''b''', '''c''', or any digit '''0-9'''. A correct syntax to match just any one digit would be <b><nowiki>[[:digit:]]</nowiki></b>.<br />
<br />
Unfortunately this does not work as it should! The correct syntax does not work at all, but currently an incorrect syntax <b><nowiki>([:digit:])</nowiki></b> will actually match a digit, as long as it is <b>outside</b> the square brackets of an alternative match. (''Obviously this is unsatisfactory, and is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=64368 issue 64368]'').<br />
<br />
The POSIX bracket expressions available are listed below. Note that the exact definition of each depends on ''locale'' - for example in a different language other characters may be considered 'alphabetic letters' in [:alpha:]. The meanings given here apply generally to English-speaking locales (and do not take into account any Unicode issues).<br />
<br />
;<b><nowiki>[:digit:]</nowiki></b> : stands for any of the digits <b>0123456789</b>. This is equivalent to <b>0-9</b>.<br />
<br />
;<b><nowiki>[:space:]</nowiki></b> : should stand for any whitespace character, including tab; however as currently implemented it stands simply for a space character. Note that the Help is currently misleading here. (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=41706 issue 41706]'').<br />
<br />
;<b><nowiki>[:print:]</nowiki></b> : should stand for any printable character; however as currently implemented it does not match the single quote nor the double quote characters <b>‘ ’ “ ”</b> (and some others such as <b>« »</b>). It matches space, but does not match tab (this latter is expected/defined behaviour). (''This is the subject of [http://qa.openoffice.org/issues/show_bug.cgi?id=83290 issue 83290]'').<br />
<br />
;<b><nowiki>[:cntrl:]</nowiki></b> : stands for a control character. As far as a user is concerned, OpenOffice.org documents have very few control characters; tab and hard_line_break are both matched, but paragraph_mark is not.<br />
<br />
;<b><nowiki>[:alpha:]</nowiki></b> : stands for a letter (including a letter with an accent). For example in the phrase (often used in English, and here given with accents as in the original language) '<b>déjà vu</b>' all 6 letters will match.<br />
<br />
;<b><nowiki>[:alnum:]</nowiki></b> : stands for a character that satisfies either <b>[:alpha:]</b> or <b>[:digit:]</b><br />
<br />
;<b><nowiki>[:lower:]</nowiki></b> : stands for a lowercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
;<b><nowiki>[:upper:]</nowiki></b> : stands for an uppercase letter (including a letter with an accent). The case matching does not work unless the <b>Match case</b> box is ticked; if this box is ''not'' ticked this expression is equivalent to <b>[:alpha:]</b>.<br />
<br />
<br />
There seems to be little consistency in any implementation of POSIX bracket expressions (OOo or elsewhere). One approach is simply to use straightforward character classes - so instead of <b><nowiki>[[:digit:]]</nowiki></b> you use <b><nowiki>[0-9]</nowiki></b> for example.<br />
<br />
<br />
== Grouping (...) and backreferences \x $x ==<br />
Round brackets '''( )''' may be used to group terms. <br />
<br />
<br />
''For example:'' '''red(den)?''' will find '<b>red</b>' and '<b>redden</b>'; here '''(den)?''' means 'one or zero of <b>den</b>'.<br />
<br />
''For example:'' '''(blue|black)bird''' will find both '<b>bluebird</b>' and '<b>blackbird</b>'.<br />
<br />
<br />
Each group enclosed in round brackets is also defined as a reference, and can be referred to later in the same expression using a 'backreference'. In the 'Search for' box, backreferences are written '<b>\1</b>', '<b>\2</b>', etc.; in the 'Replace with' box they are written '<b>$1</b>', '<b>$2</b>', etc.<br />
<br />
'<b>\1</b>' or '<b>$1</b>' stands for 'whatever matched in the first round brackets'; '<b>\2</b>' or '<b>$2</b>' stands for 'whatever matched in the second round brackets'; and so on.<br />
<br />
<br />
''For example:'' '''(blue|black) \1bird''' in the 'Search for' box will find both '<b>blue bluebird</b>' and '<b>black blackbird</b>', because '<b>\1</b>' stands for either '''blue''' or '''black''', whichever we found. Therefore '<b>black bluebird</b>' does '''not''' match.<br />
<br />
<br />
'''Backreferences in the 'Replace with' box only work from [[OOoRelease24|OOo2.4]] onwards'''. The use of $1 rather than \1 is consistent with perl syntax, and more particularly with the ICU regex engine, which may at some time replace the existing OOo regex engine, thus resolving many issues.<br />
<br />
<br />
''For example:'' '''(gr..n)(blu.)''' in the 'Search for' box will find '<b>greenblue</b>'; if the 'Replace with' box has '''$2$1''' the replacement will be '<b>bluegreen</b>'.<br />
<br />
<br />
When regular expressions are selected, to replace text with the literal character '<b>$</b>' you must now use '<b>\$</b>'; similarly for '<b>\</b>' use '<b>\\</b>'.<br />
<br />
<br />
''For example:'' '''(1..)''' in the 'Search for' box and '''\$$1''' in the 'Replace with' box replaces '<b>100</b>' with '<b>$100</b>', and '<b>150</b>' with '<b>$150</b>'.<br />
<br />
<br />
'''$0''' in the 'Replace with' box replaces with the entire text found.<br />
<br />
== Tabs, newlines, paragraphs \t \n $ ==<br />
The character pair <b>'\t'</b> has special meaning - it stands for a '''tab''' character.<br />
<br />
<br />
''For example:'' '''\tred''' will match a '''tab''' character followed by the word '<b>red</b>'.<br />
<br />
<br />
In Writer a '''newline''' may be entered by pressing Shift-Enter. A newline character is thereby inserted into the text, and the following text starts on a new line. This is not the same as a new paragraph; click ''View-Non printing characters'' to see the difference.<br />
<br />
<br />
The OOo regular expression behaviour when matching paragraph marks and newline characters is 'unusual'. This is partly because regular expressions in other software usually deal with ordinary plain text, whereas OOo regular expressions divide the text at paragraph marks. For whatever reason, this is what you can do:<br />
<br />
<br />
* '''\n''' will match a newline (Shift-Enter) if it is entered in the Search box. In this context it is simply treated like a character, and can be replaced by say a '''space''', or nothing. The regular expression '''red\n''' will match '''red''' followed by a newline character - and if replaced simply by say '''blue''' the newline will also be replaced. The regular expression '''red$''' will match '<b>red</b>' when it is followed by a newline. In this case, replacing with '<b>blue</b>' will only replace '<b>red</b>' - and will leave the newline intact.<br />
* '''red\ngreen''' will match '<b>red</b>' followed by a newline followed by '<b>green</b>'; replacing with say '<b>brown</b>' will remove the newline. However neither '''red.green''' nor '''red.*green''' will match here - the dot '''.''' does not match newline.<br />
* '''$''' on its own will match a paragraph mark - and can be replaced by say a '<b>space</b>', or indeed nothing, in order to merge two paragraphs together. Note that '''red$''' will match '<b>red</b>' at the end of a paragraph, and if you replace it with say a '''space''', you simply get a '''space''' where '<b>red</b>' was - and the paragraphs are unaffected - the paragraph mark is not replaced. It may help to regard '''$''' on its own as a special syntax, unique to OOo.<br />
* '''^$''' will match an empty paragraph, which can be replaced by say nothing, in order to remove the empty paragraph. Note that '''^red$''' matches a paragraph with only ''''red'''' in it - replacing this with nothing leaves an empty paragraph - the paragraph marks at either end are not replaced. It may help to regard '''^$''' on its own as a special syntax, unique to OOo. Unfortunately, because OOo has taken over this syntax, it seems you cannot use '''^$''' to find empty cells in a table (nor empty Calc cells).<br />
* If you wish to replace every newline with a paragraph mark, firstly you will search for '''\n''' with Find All to select the newlines. Then in the Replace box you enter '''\n''', which in the Replace box stands for a paragraph mark; then choose Replace. This is somewhat bizarre, but at least now you know. Note that \r is interpreted as a literal 'r', not a carriage return.<br />
<br />
<br />
To replace paragraph marks - as used to give lines a certain length in some html documents, for instance - with "normal" automatically wrapped lines and paragraphs, the following 3 steps should help. Don't forget to choose More Options and tick the Regular Expressions box for this procedure.<br />
<br />
1. So as not to lose "normal" paragraph marks at the end of "normal" paragraphs, replace two consecutive paragraph marks using a sequence of characters not occurring anywhere else in the text, like "*****" to replace an empty paragraph - this makes it easy to find and reinstate later. You do this by putting '''^$''' in the Find box and "*****" in the Replace box. (If you're only dealing with a limited chunk of text, don't forget to check "current selection only" under "more options" in the Find and Replace box.) <br />
<br />
2. Search for the remaining line-end paragraph marks by putting '''$''' in the Find box. To replace the mark with a "space" just type a '''space''' in the Replace dialogue. <br />
<br />
3. Now that the text is ready for normal line-wrapping, put back the "normal" paragraph marks by typing "*****" in the Find box and '''\n''' in the Replace box. (Remember to check "current selection only" where appropriate!)<br />
<br />
Before you try this, create a test document to practise on.<br />
<br />
This is a good sequence to make into a macro. You can find macro suggestions on this OOo forum page: [http://www.oooforum.org/forum/viewtopic.phtml?t=3641 "replacing hard paragraphs"].<br />
<br />
(This procedure also helps deal indirectly with line-break problems.)<br />
<br />
== Hexadecimal codes \xXXXX ==<br />
The character sequence ' <b>\x</b> then a 4 digit hexadecimal number ' stands for the character with that code.<br />
<br />
''For example:'' <b>\x002A</b> stands for the star character '<b>*</b>'.<br />
<br />
Hexadecimal codes can be seen on the ''''Insert-Special Character'''' dialog.<br />
<br />
<br />
== The 'Replace with' box \t \n & $1 $2 ==<br />
Users are sometimes confused with what can be done using the 'Replace with' box in a Find & Replace dialog.<br />
<br />
In general, regular expressions '''do not work''' in the 'Replace with' box. The characters you type replace the found text literally. <br />
<br />
The four constructs that do work are:<br />
<br />
* '''\t''' inserts a tab, replacing the text found.<br />
* '''\n''' inserts a paragraph mark, replacing the text found. This may be unexpected, because '''\n''' in the 'Search for' box means 'newline'! In some operating systems it is possible to use unicode input to directly type a newline character (U+000A) in the 'Replace with' box, providing a workaround, but this is not universal.<br />
* '''$1''', '''$2''', etc are backreferences, which (from OOo2.4) insert text groups found. See under [[#Grouping (...) and backreferences \x $x|Grouping and backreferences]]. '''$0''' inserts the entire text found.<br />
* '''&''' also inserts the entire text found.<br />
<br />
''For example'' if you searched for '''bird|berry''', you would would find either '<b>bird</b>' or '<b>berry</b>'; now to replace with '''black&''' would give you either '<b>blackbird</b>' or '<b>blackberry</b>'.<br />
<br />
== Troubleshooting OOo regular expressions ==<br />
If you are new to regular expressions, please realise that they can be tricky - if you are not getting the results you expect, you might need to check that you understand well enough. Try to keep regular expressions as simple and unambitious as possible.<br />
<br />
<br />
Here are some further points of interest with OOo regular expressions:<br />
<br />
* If you find an unexpected behaviour, please check in the relevant section in this HowTo - many of the behaviour issues have been documented here.<br />
* Regular expressions are 'greedy' - that is they will match as much text as they can. Consider using curly and square brackets; ''for example'' <b>[^ ]{1,5}\></b> matches 1 to 5 non-space characters at the end of a word.<br />
* Please be careful when using the '''Replace All''' button. There are a few rare occasions when this will give unexpected results. For example to remove the first character of every paragraph you might 'Search for' <b>^.</b> and 'Replace with' nothing; clicking 'Replace All' now will wipe out *all* your text, instead of just the first character of each paragraph. [http://qa.openoffice.org/issues/show_bug.cgi?id=82473 Issue 82473] discusses this. The workaround is to 'Find All', then 'Replace'; perhaps the safest way is not to use the 'Replace All' button at all with regular expressions.<br />
<br />
<br />
== Tips and Tricks ==<br />
Here are some examples that may be useful:<br />
<br />
<tt>'''\<([^ ]+)[ ]+\1'''</tt><br />
: finds duplicate words separated by spaces (note that there is a space before each <b>]</b>)<br />
<br />
<tt>'''\<[:alpha:]*\>'''</tt><br />
: finds any word in the whole document (notice:the check box regular expression must by checkt)<br />
<br />
<tt>'''\<[1-9][0-9]*\>'''</tt><br />
<br />
: finds decimal numbers<br />
<br />
<tt>'''\<0[0-7]*\>'''</tt><br />
: finds octal (base 8) numbers<br />
<br />
<tt>'''\<0x[A-Fa-f0-9]+\>'''</tt><br />
: finds hexadecimal (base 16) numbers<br />
<br />
<tt>'''[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-z]{2,6}'''</tt><br />
: finds <u>most</u> email addresses (there is no perfect regular expression - this is a practical solution)<br />
<br />
{{Documentation/SeeAlso|<br />
* [http://www.icu-project.org/userguide/regexp.html The ICU regular expression package], a candidate to replace the existing OOo regular expression engine (see: [[Regexp]]).<br />
* [http://www.OOoNinja.com/2007/12/example-regular-expressions-for-writer.html Example regular expressions] (OpenOffice.org Ninja)<br />
* [http://www.OOoNinja.com/2007/12/backreferences-in-replacements-new.html Backreferences in substitutions] (OpenOffice.org Ninja)<br />
* [http://www.oooninja.com/2007/12/powerful-text-matching-with-regular.html Guide to regular expressions in OpenOffice.org] (OpenOffice.org Ninja)<br />
* [http://openoffice.blogs.com/openoffice/2009/11/searching-and-replacing-paragraph-returns-carriage-returns-tabs-and-other-special-characters-in-open.html Searching and replacing paragraph returns (carriage returns), tabs, and other special characters] (Solveig Haugland's blog)<br />
}}<br />
<br />
[[Category:Documentation/Reference]]<br />
[[Category:Documentation/How Tos/Writer]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145879Education Project/Welcome it2009-11-04T17:14:50Z<p>Deneb alpha: /* Where start ? */</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONARE ==<br />
<br />
Presto sarete in grado di aiutare il progetto facendo donazioni individuali o aziendali per il progetto con l'obiettivo di favorire lo sviluppo di infrastrutture per sostenere la longevità del progetto.<br />
<br />
== STRUMENTI DI RICERCA su EDUCAZIONE ed OpenOffice.org ==<br />
<br />
Forniamo strumenti con OpenOffice.org adattati alla vostra pedagogia. <br />
<br />
Ogni volta che possiamo, cerchiamo di fornirne.<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Da dove iniziare? ==<br />
=== PARTECIPARE AL PROGETTO ===<br />
<br />
<br />
Seguire i passi sottostanti:<br />
<br />
Andare su http://education.openoffice.org <= esattamente questo sito...<br />
<br />
'''Se non avete un account di accesso, crearne uno è obbligatorio ( in alto a destra )'''<br />
<br />
'''Convalidare tutti i passaggi che permettono di collegarsi al progetto Educazione''' ( confermare la mail di sottoscrizione e così via )<br />
<br />
'''Accedere''' con la password scelta,<br />
<br />
'''=> Clicca su on Membership, poi su Request project membership / role'''<br />
<br />
'''Infine, clicca su "Submit Request" ed attendi che il responsabile del progetto accetti la tua richiesta'''<br />
<br />
E' tutto :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Basta iscriversi a dev@education.openoffice.org (altamente raccomandato) su : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Gli archivi sono estremamente importanti e sono utili per recuperare qualcosa discusso molto tempo fa.<br />
<br />
=== WEB ===<br />
<br />
Informazioni correte sono reperibili nel sito del progetto Educazione: [1] http://education.openoffice.org<br />
<br />
Troverai: collegamenti per l'area di scambio FIXME (aggiungere alcuni di essi)<br />
<br />
<br />
=== WIKI ===<br />
<br />
Informazioni aggiornate sono reperibili nel nostro wiki: [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Pagine wiki localizzate: <br />
<br />
Pagina francese: <br />
<br />
Svizzera ( attualmente in tedesco) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(altro ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Comunica con noi! <br />
<br />
Abbiamo un canale IRC in cui è possibile contattarci<br />
<br />
Il server è irc.freenode.net<br />
Il canaleè #education.openoffice.org<br />
<br />
Ci vediamo :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS ( elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145878Education Project/Welcome it2009-11-04T16:58:30Z<p>Deneb alpha: /* STRUMENTI DI RICERCA su EDUCAZIONE ed OpenOffice.org */</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONARE ==<br />
<br />
Presto sarete in grado di aiutare il progetto facendo donazioni individuali o aziendali per il progetto con l'obiettivo di favorire lo sviluppo di infrastrutture per sostenere la longevità del progetto.<br />
<br />
== STRUMENTI DI RICERCA su EDUCAZIONE ed OpenOffice.org ==<br />
<br />
Forniamo strumenti con OpenOffice.org adattati alla vostra pedagogia. <br />
<br />
Ogni volta che possiamo, cerchiamo di fornirne.<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
E' tutto :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Basta iscriversi a dev@education.openoffice.org (altamente raccomandato) su : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Gli archivi sono estremamente importanti e sono utili per recuperare qualcosa discusso molto tempo fa.<br />
<br />
=== WEB ===<br />
<br />
Informazioni correte sono reperibili nel sito del progetto Educazione: [1] http://education.openoffice.org<br />
<br />
Troverai: collegamenti per l'area di scambio FIXME (aggiungere alcuni di essi)<br />
<br />
<br />
=== WIKI ===<br />
<br />
Informazioni aggiornate sono reperibili nel nostro wiki: [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Pagine wiki localizzate: <br />
<br />
Pagina francese: <br />
<br />
Svizzera ( attualmente in tedesco) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(altro ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Comunica con noi! <br />
<br />
Abbiamo un canale IRC in cui è possibile contattarci<br />
<br />
Il server è irc.freenode.net<br />
Il canaleè #education.openoffice.org<br />
<br />
Ci vediamo :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS ( elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145877Education Project/Welcome it2009-11-04T16:58:04Z<p>Deneb alpha: /* STRUMENTI DI RICERCA su EDUCAZIONE ed OpenOffice.org */</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONARE ==<br />
<br />
Presto sarete in grado di aiutare il progetto facendo donazioni individuali o aziendali per il progetto con l'obiettivo di favorire lo sviluppo di infrastrutture per sostenere la longevità del progetto.<br />
<br />
== STRUMENTI DI RICERCA su EDUCAZIONE ed OpenOffice.org ==<br />
<br />
Forniamo strumenti con OpenOffice.org adattati alla vostra pedagogia. <br />
Ogni volta che possiamo, cerchiamo di fornirne<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
E' tutto :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Basta iscriversi a dev@education.openoffice.org (altamente raccomandato) su : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Gli archivi sono estremamente importanti e sono utili per recuperare qualcosa discusso molto tempo fa.<br />
<br />
=== WEB ===<br />
<br />
Informazioni correte sono reperibili nel sito del progetto Educazione: [1] http://education.openoffice.org<br />
<br />
Troverai: collegamenti per l'area di scambio FIXME (aggiungere alcuni di essi)<br />
<br />
<br />
=== WIKI ===<br />
<br />
Informazioni aggiornate sono reperibili nel nostro wiki: [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Pagine wiki localizzate: <br />
<br />
Pagina francese: <br />
<br />
Svizzera ( attualmente in tedesco) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(altro ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Comunica con noi! <br />
<br />
Abbiamo un canale IRC in cui è possibile contattarci<br />
<br />
Il server è irc.freenode.net<br />
Il canaleè #education.openoffice.org<br />
<br />
Ci vediamo :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS ( elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145876Education Project/Welcome it2009-11-04T16:57:31Z<p>Deneb alpha: /* SEARCH TOOLS about EDUCATION and OpenOffice.org */</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONARE ==<br />
<br />
Presto sarete in grado di aiutare il progetto facendo donazioni individuali o aziendali per il progetto con l'obiettivo di favorire lo sviluppo di infrastrutture per sostenere la longevità del progetto.<br />
<br />
== STRUMENTI DI RICERCA su EDUCAZIONE ed OpenOffice.org ==<br />
<br />
Forniamo strumenti con OpenOffice.org adattati alla vostra pedagogia. <br />
Ogni volta che possiamo, cerchiamo di fornirne<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
E' tutto :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Basta iscriversi a dev@education.openoffice.org (altamente raccomandato) su : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Gli archivi sono estremamente importanti e sono utili per recuperare qualcosa discusso molto tempo fa.<br />
<br />
=== WEB ===<br />
<br />
Informazioni correte sono reperibili nel sito del progetto Educazione: [1] http://education.openoffice.org<br />
<br />
Troverai: collegamenti per l'area di scambio FIXME (aggiungere alcuni di essi)<br />
<br />
<br />
=== WIKI ===<br />
<br />
Informazioni aggiornate sono reperibili nel nostro wiki: [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Pagine wiki localizzate: <br />
<br />
Pagina francese: <br />
<br />
Svizzera ( attualmente in tedesco) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(altro ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Comunica con noi! <br />
<br />
Abbiamo un canale IRC in cui è possibile contattarci<br />
<br />
Il server è irc.freenode.net<br />
Il canaleè #education.openoffice.org<br />
<br />
Ci vediamo :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS ( elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145875Education Project/Welcome it2009-11-04T16:53:09Z<p>Deneb alpha: /* DONATE */</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONARE ==<br />
<br />
Presto sarete in grado di aiutare il progetto facendo donazioni individuali o aziendali per il progetto con l'obiettivo di favorire lo sviluppo di infrastrutture per sostenere la longevità del progetto.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
E' tutto :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Basta iscriversi a dev@education.openoffice.org (altamente raccomandato) su : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Gli archivi sono estremamente importanti e sono utili per recuperare qualcosa discusso molto tempo fa.<br />
<br />
=== WEB ===<br />
<br />
Informazioni correte sono reperibili nel sito del progetto Educazione: [1] http://education.openoffice.org<br />
<br />
Troverai: collegamenti per l'area di scambio FIXME (aggiungere alcuni di essi)<br />
<br />
<br />
=== WIKI ===<br />
<br />
Informazioni aggiornate sono reperibili nel nostro wiki: [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Pagine wiki localizzate: <br />
<br />
Pagina francese: <br />
<br />
Svizzera ( attualmente in tedesco) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(altro ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Comunica con noi! <br />
<br />
Abbiamo un canale IRC in cui è possibile contattarci<br />
<br />
Il server è irc.freenode.net<br />
Il canaleè #education.openoffice.org<br />
<br />
Ci vediamo :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS ( elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145874Education Project/Welcome it2009-11-04T16:32:17Z<p>Deneb alpha: </p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
E' tutto :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Basta iscriversi a dev@education.openoffice.org (altamente raccomandato) su : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Gli archivi sono estremamente importanti e sono utili per recuperare qualcosa discusso molto tempo fa.<br />
<br />
=== WEB ===<br />
<br />
Informazioni correte sono reperibili nel sito del progetto Educazione: [1] http://education.openoffice.org<br />
<br />
Troverai: collegamenti per l'area di scambio FIXME (aggiungere alcuni di essi)<br />
<br />
<br />
=== WIKI ===<br />
<br />
Informazioni aggiornate sono reperibili nel nostro wiki: [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Pagine wiki localizzate: <br />
<br />
Pagina francese: <br />
<br />
Svizzera ( attualmente in tedesco) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(altro ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Comunica con noi! <br />
<br />
Abbiamo un canale IRC in cui è possibile contattarci<br />
<br />
Il server è irc.freenode.net<br />
Il canaleè #education.openoffice.org<br />
<br />
Ci vediamo :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS ( elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145872Education Project/Welcome it2009-11-04T16:21:54Z<p>Deneb alpha: </p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Informazioni aggiornate sono reperibili nel nostro wiki: [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Pagine wiki localizzate: <br />
<br />
Pagina francese: <br />
<br />
Svizzera ( attualmente in tedesco) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(altro ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Comunica con noi! <br />
<br />
Abbiamo un canale IRC in cui è possibile contattarci<br />
<br />
Il server è irc.freenode.net<br />
Il canaleè #education.openoffice.org<br />
<br />
Ci vediamo :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145869Education Project/Welcome it2009-11-04T16:11:32Z<p>Deneb alpha: </p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== RIUNIONI PERIODICHE SU IRC ===<br />
<br />
<br />
Teniamo riunioni periodiche IRC, e tutti i log sono pubblici.<br />
<br />
Li troverai qui: http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
Se si desidera partecipare, si prega di dare visitare: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (elenco ) ===<br />
* [http://education.openoffice.org Sito principale]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project Il wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Log] degli incontri IRC passati<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings incontri IRC di Educazione]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Progetti in incubazione]<br />
<br />
=== Gruppo EDUCAZIONE ===<br />
<br />
'''[[Education_Project/Team | Clicca qui per scoprire chi siamo e molto altro]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145868Education Project/Welcome it2009-11-04T15:24:46Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Avere delle linee guida nei loro progetti è motivante<br />
** Lavorare direttamente con sviluppatori professionisti di alto livello è motivante<br />
** Contribuiscono ad un progetto reale ed eccitante<br />
** Visibilità e credibilità: buoni contributi e codice a sorgente aperto sono premesse per un buon lavoro nel futuro<br />
** Possono valorizzare la loro esperienza<br />
<br />
<br />
* '''Il progetto OpenOffice.org''' vuole ...<br />
** avere nuovi sviluppatori e contributori<br />
** il progresso, perché nuovi occhi significano nuove visioni e nuove soluzioni<br />
** contribuire ad un effetto sociale: condividere la conoscenza<br />
** coinvolgere più professori e studenti a partecipare e collaborare a progetti con codice sorgente aperto<br />
<br />
== I NOSTRI SPONSOR ==<br />
<br />
(qualche candidato ? :-) )<br />
<br />
<br />
<br />
== PARTNERS sono organizzazioni senza scopo di lucro ==<br />
<br />
Se sei una scuola e vuoi collaborare, ti invitiamo ad aggiungerti alla lista:<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== Cosa puoi fare per aiutarci? ==<br />
<br />
HAI UN SUGGERIMENTO? VUOI FARE O PROPORRE QUALCOSA?<br />
<br />
Fallo !! ...e guarda sotto cosa si adatta meglio alle tue esigenze!<br />
<br />
<br />
<br />
== CONTRIBUIRE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== REGULAR IRC MEETINGS ===<br />
<br />
<br />
We hold regular IRC meetings, and all logs are public.<br />
<br />
You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (summary ) ===<br />
* [http://education.openoffice.org The main website]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project The Wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Logs] of previous Education IRC Meetings<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings Education IRC meetings]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Incubator projects]<br />
<br />
=== EDUCATION Team ===<br />
<br />
'''[[Education_Project/Team | Click Here to know who we are, and more]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145867Education Project/Welcome it2009-11-04T15:15:20Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''Per gli insegnanti'''<br />
<br />
** Visibilità<br />
** Mantenere il contatto con la realtà dei progetti industriali<br />
** Contatti diretti con progetti di alto livello<br />
** condivisione della conoscenza con altri insegnanti e professionisti<br />
<br />
<br />
* '''Per gli studenti'''<br />
<br />
** Have some guidance in their project works is motivating<br />
** Work directly with high level Professional developers is motivating<br />
** They contribute for a real and exciting Project<br />
** Visibility and credibility : good conributions, and open sourced code are a promise for a good job in the future<br />
** Can valorize their experience<br />
<br />
<br />
* '''The OpenOffice.org Project''' will ...<br />
** win new developers, and contributors<br />
** progress because new eyes means new visions, and new solutions<br />
** contribute to a social effect: share the knowledge <br />
** involve more professors and students to participate, and collaborate for OpenSource project<br />
<br />
== OUR SPONSORS ==<br />
<br />
(any candidate ? :-) )<br />
<br />
<br />
<br />
== PARTNERS are non profit Organisations ==<br />
<br />
If you are a school, and want to support us, please add you in the list :<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== What can you do to help us ? ==<br />
<br />
DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?<br />
<br />
Just do it !! ...and see below what fits at the best to your needs !<br />
<br />
<br />
<br />
== CONTRIBUTE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== REGULAR IRC MEETINGS ===<br />
<br />
<br />
We hold regular IRC meetings, and all logs are public.<br />
<br />
You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (summary ) ===<br />
* [http://education.openoffice.org The main website]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project The Wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Logs] of previous Education IRC Meetings<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings Education IRC meetings]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Incubator projects]<br />
<br />
=== EDUCATION Team ===<br />
<br />
'''[[Education_Project/Team | Click Here to know who we are, and more]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145866Education Project/Welcome it2009-11-04T15:11:03Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea basata su [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Clicca qui per visitare la pagina wiki dei propositi del progetto Educazione]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''I benefici''' ==<br />
<br />
* '''For the Teachers'''<br />
<br />
** Visibility<br />
** Keep the contact with the reality of Industrial Projects<br />
** direct contacts with high level projects<br />
** Share their knowledge with other Teachers and Professional<br />
<br />
<br />
* '''For the Students'''<br />
<br />
** Have some guidance in their project works is motivating<br />
** Work directly with high level Professional developers is motivating<br />
** They contribute for a real and exciting Project<br />
** Visibility and credibility : good conributions, and open sourced code are a promise for a good job in the future<br />
** Can valorize their experience<br />
<br />
<br />
* '''The OpenOffice.org Project''' will ...<br />
** win new developers, and contributors<br />
** progress because new eyes means new visions, and new solutions<br />
** contribute to a social effect: share the knowledge <br />
** involve more professors and students to participate, and collaborate for OpenSource project<br />
<br />
== OUR SPONSORS ==<br />
<br />
(any candidate ? :-) )<br />
<br />
<br />
<br />
== PARTNERS are non profit Organisations ==<br />
<br />
If you are a school, and want to support us, please add you in the list :<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== What can you do to help us ? ==<br />
<br />
DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?<br />
<br />
Just do it !! ...and see below what fits at the best to your needs !<br />
<br />
<br />
<br />
== CONTRIBUTE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== REGULAR IRC MEETINGS ===<br />
<br />
<br />
We hold regular IRC meetings, and all logs are public.<br />
<br />
You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (summary ) ===<br />
* [http://education.openoffice.org The main website]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project The Wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Logs] of previous Education IRC Meetings<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings Education IRC meetings]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Incubator projects]<br />
<br />
=== EDUCATION Team ===<br />
<br />
'''[[Education_Project/Team | Click Here to know who we are, and more]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145865Education Project/Welcome it2009-11-04T15:09:22Z<p>Deneb alpha: (checkpoint save)</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Propositi del progetto Educazione'''</div> ===<br />
<br />
Idea based on [[Efforts | Propositi]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Click Here to visit Education Project Effort wiki page]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''The Benefits''' ==<br />
<br />
* '''For the Teachers'''<br />
<br />
** Visibility<br />
** Keep the contact with the reality of Industrial Projects<br />
** direct contacts with high level projects<br />
** Share their knowledge with other Teachers and Professional<br />
<br />
<br />
* '''For the Students'''<br />
<br />
** Have some guidance in their project works is motivating<br />
** Work directly with high level Professional developers is motivating<br />
** They contribute for a real and exciting Project<br />
** Visibility and credibility : good conributions, and open sourced code are a promise for a good job in the future<br />
** Can valorize their experience<br />
<br />
<br />
* '''The OpenOffice.org Project''' will ...<br />
** win new developers, and contributors<br />
** progress because new eyes means new visions, and new solutions<br />
** contribute to a social effect: share the knowledge <br />
** involve more professors and students to participate, and collaborate for OpenSource project<br />
<br />
== OUR SPONSORS ==<br />
<br />
(any candidate ? :-) )<br />
<br />
<br />
<br />
== PARTNERS are non profit Organisations ==<br />
<br />
If you are a school, and want to support us, please add you in the list :<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== What can you do to help us ? ==<br />
<br />
DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?<br />
<br />
Just do it !! ...and see below what fits at the best to your needs !<br />
<br />
<br />
<br />
== CONTRIBUTE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== REGULAR IRC MEETINGS ===<br />
<br />
<br />
We hold regular IRC meetings, and all logs are public.<br />
<br />
You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (summary ) ===<br />
* [http://education.openoffice.org The main website]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project The Wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Logs] of previous Education IRC Meetings<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings Education IRC meetings]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Incubator projects]<br />
<br />
=== EDUCATION Team ===<br />
<br />
'''[[Education_Project/Team | Click Here to know who we are, and more]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145864Education Project/Welcome it2009-11-04T15:08:32Z<p>Deneb alpha: </p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* accogliere gli studenti<br />
** proporgli la metodologia (trovare la documentazione)<br />
** insegnargli (per le conoscenze di base e di autonomia)<br />
** laboratori ( come la pratica in aula )<br />
** leggere e spiegare il codice insieme<br />
** studenti tutor (spingerli alla soluzione giusta, aumentare la loro autonomia)<br />
** gestione del progetto e line guida<br />
<br />
* lavorare in sinergia tra mondo professionale e professori universitari/docenti<br />
** configurazione del progetto<br />
** avviare progetti di ricerca e sviluppo <br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Education Project Effort '''</div> ===<br />
<br />
Idea based on [[Efforts | Efforts]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Click Here to visit Education Project Effort wiki page]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''The Benefits''' ==<br />
<br />
* '''For the Teachers'''<br />
<br />
** Visibility<br />
** Keep the contact with the reality of Industrial Projects<br />
** direct contacts with high level projects<br />
** Share their knowledge with other Teachers and Professional<br />
<br />
<br />
* '''For the Students'''<br />
<br />
** Have some guidance in their project works is motivating<br />
** Work directly with high level Professional developers is motivating<br />
** They contribute for a real and exciting Project<br />
** Visibility and credibility : good conributions, and open sourced code are a promise for a good job in the future<br />
** Can valorize their experience<br />
<br />
<br />
* '''The OpenOffice.org Project''' will ...<br />
** win new developers, and contributors<br />
** progress because new eyes means new visions, and new solutions<br />
** contribute to a social effect: share the knowledge <br />
** involve more professors and students to participate, and collaborate for OpenSource project<br />
<br />
== OUR SPONSORS ==<br />
<br />
(any candidate ? :-) )<br />
<br />
<br />
<br />
== PARTNERS are non profit Organisations ==<br />
<br />
If you are a school, and want to support us, please add you in the list :<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== What can you do to help us ? ==<br />
<br />
DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?<br />
<br />
Just do it !! ...and see below what fits at the best to your needs !<br />
<br />
<br />
<br />
== CONTRIBUTE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== REGULAR IRC MEETINGS ===<br />
<br />
<br />
We hold regular IRC meetings, and all logs are public.<br />
<br />
You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (summary ) ===<br />
* [http://education.openoffice.org The main website]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project The Wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Logs] of previous Education IRC Meetings<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings Education IRC meetings]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Incubator projects]<br />
<br />
=== EDUCATION Team ===<br />
<br />
'''[[Education_Project/Team | Click Here to know who we are, and more]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project&diff=145858Education Project2009-11-04T10:08:48Z<p>Deneb alpha: </p>
<hr />
<div>{| align=center style="margin-left: 15px; border:1px solid #aaaaaa; background-color:#f9f9f9; padding:5px; font-size: 95%;" class=box<br />
|--- <br />
!align=center style="background:#ccccff;" |'''''[[http://education.openoffice.org/ Education project]]'''''<br />
|-<br />
|[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
|-<br />
|<br />
'''''Categories:'''''<br />
* [[:Category:Education]]<br />
|-<br />
|'''[http://education.openoffice.org/ Education project: the official site]'''<br />
<br />
<div class="plainlinks"> ''[{{SERVER}}{{localurl:Template:Education|action=edit}} edit] this model.''</div><br />
|}<br />
<br />
<br />
<br />
=== Welcome to the Education project ! ===<br />
<br />
<br><br />
<div align="left" style="color:blue; font-size:18px"> '''[English] Howto Start ''' [[Education_Project/Welcome en | '''Click here''' to read the English version]]</div><br />
<br><br />
<div align="left" style="color:blue; font-size:18px"> '''[Français] Pour bien commencer''' [[Education_Project/Bienvenue fr | - Cliquer ici pour lire la version française ]] </div><br />
<br><br />
<br />
<div align="left" style="color:blue; font-size:18px">'''[German] Wie man anfängt''' [[Education_Project/Willkommen de | '''Hier klicken''' und die deutschsprachige Version lesen]]</div><br />
<br><br />
<div align="left" style="color:blue; font-size:18px"> ''' [Bengali] কি করে যোগদান করবেন ''' [[Education_Project/Welcome bn | '''ক্লিক করুন''' বাংলায় পড়ার জন্য]]</div><br />
<br><br />
<div align="left" style="color:blue; font-size:18px"> ''' [中文] 如何开始 ''' 阅读中文版请[[Education_Project/Welcome zh |'''点击这里''']]</div><br />
<br><br />
<div align="left" style="color:blue; font-size:18px"> ''' [Italian] Per iniziare '''<br />
[[Education_Project/Welcome it | clicca qui per leggere la versione italiana]] </div><br />
<br><br />
<div align="left" style="color:green; font-size:18px"> ''' [Japanese] ( to be translated in your locale) ''' </div><br />
<br><br />
<big>translate the welcome and add your locale !! </big><br />
<br />
<br><br><br />
<br />
=== The Education project Team ===<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Team | ==> Click here to know who we are]]''' </div><br />
<br><br />
<br><br />
<br />
<div align="left" style="color:blue; font-size:18px">'''Page under construction. You are welcome to contribute :-) '''</div><br />
<br />
If you have urgent questions, or need informations, please join us on our IRC chat channel.<br />
<br />
<pre><br />
Server is : irc.freenode.net <br />
<br />
Channel is #education.openoffice.org (english)<br />
<br />
Please remember the #<br />
<br />
See you on the IRC chat :-)<br />
</pre><br />
<br />
<br />
Or subscribe to the mailing list: dev@education.openoffice.org<br />
<br />
=> [[http://education.openoffice.org/servlets/ProjectMailingListList Subscribe to the mailing list]]<br />
<br />
=== Short News from the subprojects ===<br />
<br />
This is the place to provide updates and news about projects under the Education Project. To create a news item simply set the project name in bold before the news content. Please write in English only and add the latest item over the last one.<br />
<br />
* [http://2009.rmll.info/?lang=en LSM 2009 (Nantes, France)]<br />
* Solutions Linux 2009 ( Paris France)<br />
* Rencontres de l'ORME 2009<br />
* Eric Bachard will represent Education Project at [http://www.fosdem.org/2009/schedule/devroom/openofficeorg FOSDEM 2009 OpenOffice.org DevRoom]<br />
* Mathieu Lalanne will represent Education Project at [http://www.montpel-libre.fr/index.php?2008/10/16/6-le-3-decembre-prochaine-install-party-et-salon-sur-les-technologies-de-l-information-et-de-la-communication-a-dideris Live eTic 2008] Montpelier France) the 3rd December 2008<br />
* Education Project will be present at [http://www.educatice.com/ Educatice 2008 (Paris France)], 25th to 28th November 2008<br />
* Rakesh Pandit workout has been accepted at [https://foss.in/ FOSS.in, Bangalore India] (25th to 28th November )<br />
* [http://http://jm2l.linux-azur.org J2ML , Nice France] ( 15th of November )<br />
* [http://fsoss.senecac.on.ca/2008/ FSOSS 2008], at Seneca College ( Toronto, Canada ) 23rd 24th Ocbtober<br />
* Education Project was represented at '''Journée travaill collaboratif at Ecole Normale Supérieure (rue d'Ulm), Paris France'''<br />
* '''Education Project''' is invited at '''Paris Capitale du Libre''' by the '''SCEREN''' (thanks to Jean-Pierre Archambault) <br />
* Presentation about '''Education Project''' and '''OPLC''' at '''Epitech Paris''', 24th September (thanks to Pierre Pasteau for the invitation)<br />
* ( ericb September 14th 2008 ) Two new Domain devs for the Education Project : congratulation to Pierre Pasteau and Rakesh Pandit !<br />
* (rbircher December 13th 2007) '''Project Switzerland''' We start searching people for a association in Switzerland<br />
* (rbircher December 10th 2007) '''Website:''' Nicolas Jeudy working on the layout<br />
<br />
<br><br />
<br><br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Education Project Effort '''</div> ===<br />
<br />
Idea based on [[Efforts | Efforts]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Click Here to visit Education Project Effort wiki page]]''' </div><br />
<br />
<br />
<br><br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Projects Students are working on '''</div> ===<br />
<br />
[FIXME] : add the projects in progress, to retrieve easely who does what<br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Education Project ClassRoom'''</div> ===<br />
<br />
Idea based on [[Education_Courses | Education Courses]] ...<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_ClassRoom | ==> Click Here to visit Education Project ClassRoom wiki page]]''' </div><br />
<br />
<br />
<br><br />
<br />
=== Todo ===<br />
<br />
<div align="left" style="color:blue; font-size:18px">'''List in construction. You can help us complete it and improve on it '''</div><br />
<br />
( Brainstorming in progress )<br />
<br />
* Revamp http://education.openoffice.org<br />
* Make the page static <br />
* Organize the wiki page<br />
* Create new entries : locales ? / tools ? / Success stories ? / Partners ?<br />
<br />
* Resources : ask an entry for every school present on the site ? (annually ?) <br />
<br />
* QA : define default owner for education project issues<br />
<br />
* Be present and visible (please complete the list) :<br />
<br />
* PCIE/EDCL : http://www.pcie.tm.fr/<br />
<br />
<br />
* '''Recent Issues''' <br />
<div align="left" style="color:red; font-size:18px">'''Urgent'''</div><br />
<br />
<br />
1) Installation / Usability <br />
<br />
* OpenOffice.org installation , mainly under Microsoft Windows, is problematic ( unique registration, ...etc)<br />
* Installation in a rightless environment<br />
<br />
2) Compatibility <br />
<br />
Again, with MS Office <br />
(examples, precise case, writing of a guide avoiding issues, find the most known of them .. )<br />
<br />
3) Maths<br />
<br />
* formulas alignments<br />
<br />
This is an incredibly well known and important default. Some migrations failed just because of this "detail".<br />
<br />
See the sadly well known issue 972 , and referenced in IssueZilla since may 2001 (yes 2001 !) <br />
URL : http://qa.openoffice.org/issues/show_bug.cgi?id=972<br />
<br />
4) Unclassified<br />
<br />
* '''Suggestions of amelioration'''<br />
<br />
Maxima<br />
<br />
Use Maxima in OpenOffice.org ?<br />
<br />
Partial answer : as soon as I'll have the answer to "how interface" OpenOffice.org and Application written in Lisp ( Maxima is written in Lisp ), I promise I'll take the task over.<br />
<br />
Update: I got some infos from Eike Rathke and Kendy. Playing with fork() exec() wait() .. stay tuned.<br />
<br />
[[User:Ericb|Ericb]] 12:07, 25 December 2007 (CET)<br />
<br />
Suggestion: instead of trying to do this by hand, use the Expect library; an Expect module for OOo would be really useful.<br />
<br />
* '''Success stories'''<br />
<br />
Any positive success story of installation and /or use in your school, interests us.<br />
<br />
Initiation to OpenOffice.org use<br />
<br />
'''Be extremely careful is recommended, only the French Eductional system is described below'''<br />
<br />
Which formations could concern OpenOffice.org ? <br />
<br />
- type de formation : secondary, profesional formations ?<br />
- concerned courses: Maths ? Physics ? ( Other ? )<br />
<br />
URL of reference : http://info.sio2.be/calcooo/index.php ( French, sorry )<br />
<br />
Plan (translated from French ): <br />
<pre><br />
1. Introduction to a Spreadsheet use with OpenOffice.org (mise à jour 07/01/2006)<br />
<br />
2. Use of Calc functions (last update 17/01/2006)<br />
<br />
3. The alternative with the Spreadsheet (last update 12/01/2006)<br />
<br />
4. Create diagrams using OpenOffice.org Calc<br />
<br />
5. Improved study of Mathematical diagrams ( last update 16/05/2006)<br />
<br />
Share your opinion whith this course. <br />
</pre><br />
<br />
For every part, it could be interesting to define :<br />
<br />
The relevant concerned programs<br />
<br />
- the plan of the lesson<br />
<br />
- the prerequisites of the lesson<br />
<br />
- the objectives, well justified in the referential of the program<br />
<br />
- the estimated time for the lesson<br />
<br />
* '''Pedagogical notes creation'''<br />
<br />
Target: ''' create pedagogical notes for the existing tools, improving the role of OpenOffice.org''' :<br />
<br />
Every teacher will certainly have a personal way, but to obtain something consistent, it will be to follow a common skeleton, everybody is invited to improve.<br />
<br />
Example:<br />
<br />
* The pedagogical frame of use: public / level <br />
<br />
* prerequisites,<br />
<br />
* the place in the progression, <br />
<br />
* the time of the sequence..etc<br />
<br />
* objectives,<br />
<br />
* the place dans le referential of the program,<br />
<br />
* limits .. (thanks to improve and complete the list)<br />
<br />
<br />
* '''Mutualisation of documents''' : ADD A LICENSE FOR THE CONTENT <br />
<br />
[http://eric.bachard.free.fr/Education/Resources/Education_template.sxw Example of downloadable document with licence]<br />
<br />
* '''Suggestions for academical correspondents'''<br />
<br />
<br><br />
<br />
- '''recent the schools using OpenOffice.org''' ( write a list on the Wiki ? )<br />
<br />
- '''inform''' people managing / to be aware of the project existence '''and invite them to join us''' (Education Project, dev@education.openoffice.org list)<br />
<br />
- '''keep the list of known issues up to date''' , and define a '''list of priorities''' : we need to concentrate our efforts to the correction of such issues !<br />
- '''participate''', if possiblee, to events who can involve OpenOffice.org project in your academy'''<br />
- '''recent''' such events<br />
- '''recent existing tools and documents''', who bring a value added the pedagogical interest OpenOffice.org to be used ( next step : put them on the site, for download, but define precisely how do that "before" )<br />
- '''be visible'''<br />
<br />
== <div align="left" style="color:blue; font-size:18px">'''Regular Events '''</div> ==<br />
<br />
There are many events where the OpenOffice.org Education Project is represented. <br />
<br />
Feel free to add the one you did.<br />
<br />
=== Events 2009 ===<br />
<br />
[[Education_Project/Events 2009]]<br />
<br />
=== Events 2008 ===<br />
<br />
[[Education_Project/Events 2008]]<br />
<br />
<br />
FIXME: add rules for people representing the Education Project<br />
<br />
<br />
=== Localisation projects ===<br />
<br />
Below you will find all sub-projects of the main education project. <br />
<br />
Those sub-projects are a good place to find :<br />
*resources in your own language, <br />
*documentation related to your educational system<br />
*a good starting point to build a bridge between OOo development and education in your own country.<br />
*that you bring into it !<br />
<br />
Join us :<br />
<br />
==== fr : Education Project in French ====<br />
<br />
For French speaking countries : [[fr-EDUCATION]]<br />
<br />
Switzerland project ( german only at this time ) : [[Project_EDUCATION-ch]]<br />
<br />
=== <font color=blue>List of schools participating to the Effort </font>===<br />
<br />
<br />
Canada <br />
<br />
* [http://www.senecac.on.ca/ '''Seneca College''' ] will provide students and professors working on OpenOffice.org (work in progress: [[Education_Project/Effort/Seneca | dedicated wiki page for Seneca College contributions]] )<br />
<br />
France <br />
<br />
Engineers schools or University<br />
<br />
* [http://www.ec-nantes.fr/ '''Ecole Centrale Nantes'''] (students and professors) (work in progress: [[Education_Project/Effort/Ecole_Centrale_Nantes | dedicated wiki page for Ecole Centrale Nantes contributions]] )<br />
<br />
* [http://www.utbm.fr '''UTBM'''] ( students and one professor)<br />
<br />
* [http://www.epitech.eu/ '''Epitech'''] (students)<br />
<br />
<br />
Secondary<br />
<br />
* Collège Le Trion Samer (other contributions to the Project)<br />
<br />
=== <font color=blue>Linux Distributions participating to the Effort </font>===<br />
<br />
<br />
Complete me :-)<br />
<br />
=== Improve me ===<br />
<br />
'''FIXME'''<br />
<br />
* Define tabs for every country ? <br />
<br />
* Define arrays for all schools, including Schools logos, contacts for every ... etc ?<br />
<br />
'''please complete the list, and define/add contacts'''<br />
<br />
French schools already contacted : <br />
<br />
* INSA Lyon [http://www.insa-lyon.fr/ INSA Lyon]<br />
* INSA Toulouse [http://www.insa-toulouse.fr/ INSA Toulouse]<br />
* IUT Blagnac [http://www.iut-blagnac.fr/ IUT Blagnac]<br />
* ENSEEIHT [http://www.enseeiht.fr ENSEEIHT]<br />
<br />
=== Projects in progress === <br />
<br />
=== Improve the OOo Impress part for TabletPC uses (Ecole Centrale de Nantes) ===<br />
The team of students of the ECN :<br />
* Guillaume Arfaoui<br />
* Frédéric Gelot<br />
* Olivier Girardot<br />
* Sashi Juganaikloo<br />
* Florent Rouvière<br />
* Pierre-Jean Parot<br />
* Aude Quintana<br />
<br />
and the teacher leading this project Morgan Magnin managed (with many help) to add drawing features on the slideshow and sd modules, in order to be able to draw on an impress presentation during the slideshow, changing colors and stroke width easily. <br />
<br />
These changes make OpenOffice.org even more relevant to use in a TabletPC environment. <br />
<br />
You can find more informations on the project on the blog dedicated to the project (French) [https://pedagogie.ec-nantes.fr/tablet-pc/ TabletPC]<br />
<br />
=== Volunteers to revamp the site ===<br />
<br />
* Raphael Bircher<br />
* Nicolas JEUDY<br />
<br />
==== brainstorming ====<br />
<br />
* [[Education_revamp_site | brainstorm for education project website]]<br />
* [[Education_Webconcept | Webconcept for education project website]]*<br />
<br />
=== IRC channel === <br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">All informations are now available at '''[[Education_IRC_meetings]]''' wiki page.</div><br />
<br />
<br />
Proposal : have regular IRC meetings ? <br />
<br />
'''First IRC meeting scheduled for the week 12th - 17th of November 2007'''<br />
<br />
<br />
Proposed : <br />
<br />
'''server : irc.freenode.net Channel : #education.openoffice.org '''<br />
<br />
Done :<br />
<br />
Register the channel : Chanserv is set as guard , mode secure On, Topiclock is on<br />
Define operators / tasks / Action Items<br />
<br />
+ complete the list on OpenOffice.org wiki page<br />
<br />
=== Courses ===<br />
<br />
FIXME : needs rework <br />
<br />
This section has been moved to : [[Education Courses]]<br />
<br />
=== Whatever ===<br />
<br />
FIXME : complete :-)<br />
<br />
<font color=blue>[http://wiki.ooo4kids.org/index.php/Main_Page '''Main OOo4Kids page''']</font><br />
<br />
[[Education_Project/OOo4Kids | OOo4Kids(old)]]<br />
<br />
[[Category:Education]]<br />
<br />
[[Category:Project]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145857Education Project/Welcome it2009-11-04T10:07:43Z<p>Deneb alpha: </p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* welcome students<br />
** propose them methodology ( find documentation)<br />
** teach them (for basic knowledge and autonomy) <br />
** work shops ( like the practice in ClassRoom )<br />
** read and explain code together<br />
** mentor students (drive them to the right solution, and raise their autonomy)<br />
** project management and guidance<br />
<br />
* work for synergy between professional world and university professors / teachers <br />
** project setup<br />
** start research and development oriented projects<br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Education Project Effort '''</div> ===<br />
<br />
Idea based on [[Efforts | Efforts]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Click Here to visit Education Project Effort wiki page]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''The Benefits''' ==<br />
<br />
* '''For the Teachers'''<br />
<br />
** Visibility<br />
** Keep the contact with the reality of Industrial Projects<br />
** direct contacts with high level projects<br />
** Share their knowledge with other Teachers and Professional<br />
<br />
<br />
* '''For the Students'''<br />
<br />
** Have some guidance in their project works is motivating<br />
** Work directly with high level Professional developers is motivating<br />
** They contribute for a real and exciting Project<br />
** Visibility and credibility : good conributions, and open sourced code are a promise for a good job in the future<br />
** Can valorize their experience<br />
<br />
<br />
* '''The OpenOffice.org Project''' will ...<br />
** win new developers, and contributors<br />
** progress because new eyes means new visions, and new solutions<br />
** contribute to a social effect: share the knowledge <br />
** involve more professors and students to participate, and collaborate for OpenSource project<br />
<br />
== OUR SPONSORS ==<br />
<br />
(any candidate ? :-) )<br />
<br />
<br />
<br />
== PARTNERS are non profit Organisations ==<br />
<br />
If you are a school, and want to support us, please add you in the list :<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== What can you do to help us ? ==<br />
<br />
DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?<br />
<br />
Just do it !! ...and see below what fits at the best to your needs !<br />
<br />
<br />
<br />
== CONTRIBUTE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== REGULAR IRC MEETINGS ===<br />
<br />
<br />
We hold regular IRC meetings, and all logs are public.<br />
<br />
You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (summary ) ===<br />
* [http://education.openoffice.org The main website]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project The Wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Logs] of previous Education IRC Meetings<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings Education IRC meetings]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Incubator projects]<br />
<br />
=== EDUCATION Team ===<br />
<br />
'''[[Education_Project/Team | Click Here to know who we are, and more]]'''<br />
<br />
[[Category:Education]]</div>Deneb alphahttps://wiki.openoffice.org/w/index.php?title=Education_Project/Welcome_it&diff=145856Education Project/Welcome it2009-11-04T09:59:14Z<p>Deneb alpha: Created page with '{{DISPLAYTITLE: Benvenuto}} Questo è il logo del progetto Educazione: Image:LaMouette-Degree_mini.jpg Autore : Ben Bois ( ben at hooboo dot com ) == '''Cos'è il proget…' (checkpoint save)</p>
<hr />
<div>{{DISPLAYTITLE: Benvenuto}}<br />
<br />
Questo è il logo del progetto Educazione:<br />
<br />
[[Image:LaMouette-Degree_mini.jpg]]<br />
<br />
Autore : Ben Bois ( ben at hooboo dot com )<br />
<br />
== '''Cos'è il progetto Educazione ?''' ==<br />
<br />
In OpenOffice.org tutto è un progetto. Tutti i siti internet si attengono a questa regola : <br />
http://$(project).OpenOffice.org <br />
<br />
ad esempio: http://education.openoffice.org<br />
<br />
Attualmente questo è un progetto in fase di incubazione. Ciò vuol dire che si è appena iniziato a realizzarlo e c'è ancora molto da fare prima di potergli assegnare lo stato di progetto.<br />
<br />
<br />
'''... Abbiamo bisogno di te !'''<br />
<br />
== '''L'idea''' ==<br />
<br />
L'idea: '''creare uno stretto legame tra il mondo dell'educazione ed il progetto OpenOffice.org''', puntando principalmente su <br />
* sinergia <br />
* visibilità <br />
* e sviluppo per tutti<br />
<br />
== '''La nostra missione''' == <br />
<br />
'''In 3 punti'''<br />
<br />
- '''Fornire un luogo per gli utenti OpenOffice.org nel contesto scolastico''': discutendo su come adattare OpenOffice.org all'insegnamento, alle proprie necessità, ecc... ( sono considerati tutti i livelli scolastici )<br />
<br />
- '''Fornire e promuovere strumenti''' di OpenOffice.org adatti per l'uso pedagogico<br />
<br />
- '''Scrivere codice insieme''' : possiamo insegnarti tutto sul codice di OpenOffice.org e su come aggiungere il tuo: basta leggere più avanti<br />
<br />
<br />
<br />
== '''Obiettivi per scrivere codice insieme''' ==<br />
<br />
* welcome students<br />
** propose them methodology ( find documentation)<br />
** teach them (for basic knowledge and autonomy) <br />
** work shops ( like the practice in ClassRoom )<br />
** read and explain code together<br />
** mentor students (drive them to the right solution, and raise their autonomy)<br />
** project management and guidance<br />
<br />
* work for synergy between professional world and university professors / teachers <br />
** project setup<br />
** start research and development oriented projects<br />
<br />
=== <div align="left" style="color:red; font-size:18px">'''Education Project Effort '''</div> ===<br />
<br />
Idea based on [[Efforts | Efforts]]<br />
<br />
<br />
<br />
<div align="left" style="color:blue; font-size:18px">''' [[Education_Project/Effort | ==> Click Here to visit Education Project Effort wiki page]]''' </div><br />
<br />
<br />
<br><br />
<br />
== '''The Benefits''' ==<br />
<br />
* '''For the Teachers'''<br />
<br />
** Visibility<br />
** Keep the contact with the reality of Industrial Projects<br />
** direct contacts with high level projects<br />
** Share their knowledge with other Teachers and Professional<br />
<br />
<br />
* '''For the Students'''<br />
<br />
** Have some guidance in their project works is motivating<br />
** Work directly with high level Professional developers is motivating<br />
** They contribute for a real and exciting Project<br />
** Visibility and credibility : good conributions, and open sourced code are a promise for a good job in the future<br />
** Can valorize their experience<br />
<br />
<br />
* '''The OpenOffice.org Project''' will ...<br />
** win new developers, and contributors<br />
** progress because new eyes means new visions, and new solutions<br />
** contribute to a social effect: share the knowledge <br />
** involve more professors and students to participate, and collaborate for OpenSource project<br />
<br />
== OUR SPONSORS ==<br />
<br />
(any candidate ? :-) )<br />
<br />
<br />
<br />
== PARTNERS are non profit Organisations ==<br />
<br />
If you are a school, and want to support us, please add you in the list :<br />
<br />
University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]<br />
<br />
<br />
<br />
== What can you do to help us ? ==<br />
<br />
DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?<br />
<br />
Just do it !! ...and see below what fits at the best to your needs !<br />
<br />
<br />
<br />
== CONTRIBUTE ==<br />
<br />
Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) , sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!<br />
<br />
With us, you can learn :<br />
<br />
* how the source code for OpenOffice.org is organized so that you can develop effectively<br />
* which tools are used in OpenOffice.org<br />
* how to build OpenOffice.org for your Operating System<br />
* how a new feature implementation is accepted and scheduled<br />
* how the QA is managed<br />
* how the component or module you want to understand and possibly contribute to functions<br />
* what to do if you want to add something<br />
* what to do if you want to create an extension<br />
* how to define applications for your students adapted to OpenOffice.org<br />
* how to become a Domain Developer for OpenOffice.org project<br />
<br />
Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !<br />
<br />
== DONATE ==<br />
<br />
Soon you'll be able to help the project by making individual or corporate donations to the project with the aim of furthering the development of infrastructure to sustain the project longevity.<br />
<br />
== SEARCH TOOLS about EDUCATION and OpenOffice.org ==<br />
<br />
We do provide tools using OpenOffice.org and adapted to your pedagogy. <br />
Every time we can, we try to provide <br />
<br />
<br />
<br />
<br />
== PROVIDE US EXPERTISE ==<br />
<br />
Are you using OpenOffice.org in your courses/studies ? Please :<br />
<br />
- let us know which School you represent<br />
- what you did<br />
- provide us pedagogical methods adapted to teaching<br />
<br />
<br />
<br />
== Where start ? ==<br />
=== JOIN THE PROJECT ===<br />
<br />
<br />
Thanks to respect the steps below :<br />
<br />
Go at http://education.openoffice.org <= exactly this site ...<br />
<br />
'''If you don't have a login, create one is mandatory ( on top right)'''<br />
<br />
'''Validate all the steps allowing to connect yourself to the Education Project''' ( confirm the subscription mail and so on )<br />
<br />
'''Log you in''' with the password you have choosen,<br />
<br />
'''=> Click on Membership, then on Request project membership / role'''<br />
<br />
'''Finaly, click on "Submit Request" and wait for a project Lead to accept your pending request'''<br />
<br />
That's it :-)<br />
<br />
=== MAILING LISTS ===<br />
<br />
Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]<br />
<br />
Archives are extremely important, and are usefull to retrieve something being discussed long time ago.<br />
<br />
=== WEB ===<br />
<br />
Fixed informations are on Education project website : [1] http://education.openoffice.org<br />
<br />
You'll find : links for tools, links for exchange area FIXME ( add some of them )<br />
<br />
<br />
=== WIKI ===<br />
<br />
Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
Localized wiki pages : <br />
<br />
French page : <br />
<br />
Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch<br />
<br />
(other ) : TODO <br />
<br />
<br />
=== IRC ===<br />
<br />
Discuss with us ! <br />
<br />
We have an IRC channel and you can meet us for true: <br />
<br />
Server is irc.freenode.net<br />
Channel is #education.openoffice.org<br />
<br />
See you :-)<br />
<br />
<br />
=== REGULAR IRC MEETINGS ===<br />
<br />
<br />
We hold regular IRC meetings, and all logs are public.<br />
<br />
You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]<br />
<br />
<br />
If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]<br />
<br />
<br />
=== LINKS (summary ) ===<br />
* [http://education.openoffice.org The main website]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project The Wiki]<br />
* [http://education.openoffice.org/servlets/ProjectMailingListList Mailing list]<br />
* [http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs Logs] of previous Education IRC Meetings<br />
* [http://wiki.services.openoffice.org/wiki/Education_IRC_meetings Education IRC meetings]<br />
* [http://www.utbm.fr University of Technology of Belfort Montbeliard]<br />
* [http://projects.openoffice.org/incubator.html Incubator projects]<br />
<br />
=== EDUCATION Team ===<br />
<br />
'''[[Education_Project/Team | Click Here to know who we are, and more]]'''<br />
<br />
[[Category:Education]]</div>Deneb alpha