Help talk:Extension:Translate/Page translation example

This way of translating content makes the page output extremely verbose see for example https://www.mediawiki.org/w/index.php?title=Extension:Math&action=edit It's hard to read and to edit and it reduces the entropy significantly. This reverts the effort of the visual editor to keep the source readable. I think in principal there is no need to store all the translate tags and XML comments in the wikitext. Or is the general strategy to use the visual editor exclusively for editing? In that case I'd vote for making the new wikitext identical to docx, so that it can be edited with Microsoft Word if everything else crashes;-) --Physikerwelt (talk) 18:15, 1 November 2014 (UTC)
 * This comment is not related to the tutorial at all, is it? It seems a comment about Translate syntax.
 * Your point seems to be that the Translate marking should be possible in VisualEditor: that's 53974, which is blocked on 48891. --Nemo 18:25, 1 November 2014 (UTC)

"This page contains changes which are not marked for translation."
Hello. In the tutorial, it is written that After saving the page, you will see a link at the top of the page saying "Mark this page for translation" (or "This page contains changes which are not marked for translation." if you are not a translation administrator). Click on that link. I guess that the sentence "Click on that link" refers to the link "Mark this page for translation"? I tried to click on the two links included in the sentence "This page contains changes which are not marked for translation." and none of them lead me to the page shown in the picture. Best, Wikini (talk) 08:08, 9 June 2015 (UTC)
 * As step 1 says, the tutorial assumes you have rights configured. If you need to mark pages for translation, you need the pagetranslation permission (on this wiki, it's the "Translation administrators" group). --Nemo 14:49, 9 June 2015 (UTC)
 * Ok, thank you, I didn't got it. I guess this is included in the word "configured" of the first sentence (namely "This tutorial assumes that the Translate extension is already installed and configured")? My following question is: where to apply to be in the "Translation administrators" group? Best, Wikini (talk) 12:26, 10 June 2015 (UTC)
 * Yeah sorry, the beginning could be clearer; the expected audience is only specified in incoming links but not on the page itself, it seems. Will see if I can fix. For what wiki do you want translationadmin flag? On this wiki it's handled at Project:Requests, on other wikis ask the bureaucrats. --Nemo 14:34, 10 June 2015 (UTC)
 * Thanks! Wikini (talk) 15:18, 10 June 2015 (UTC)

How to edit a page with translation units on it
Please define what, precisely, a translation unit is. Supposedly we can rearrange and edit every single character around there delimiters whatever they are. "Translate tags" have the opening and closing tag, but what is this "translation unit" thing? It is is not clear. Is it to the left or the right of the marker? How does a translation unit relate to a translate tag, if at all? Like the description of tables and sections, it has always been true that an editor needs to know how to treat every single character of the wikitext.

What about tables? What about sections? And what about other markup? These things can be previewed, and corrected. Please tell me how to interpret the error page I get when I ruin that environment so badly I can't save my edits.

And please, there's no link from the effectively de-wikified, elite-priveleged only, pages to the help documentation for how to edit them. Cpiral (talk) 02:06, 10 September 2015 (UTC)


 * The glossary explains what a translation unit is. The reference manual goes into detail on how translation units are identified and more.
 * Generally, nothing goes bad if the translation administrator marked the page reasonably: you shouldn't bother to touch the tags. Can you link the page you were editing and tell what you were trying to do?
 * As for the help links, it would be the first extension adding custom help for itself on action=edit; please file the feature request for broader consideration. --Nemo 05:56, 10 September 2015 (UTC)


 * At Help:Search it's giving me "unbalanced translate tag" and showing me the entire page. But I'm only working on the insource: section.  I believe the translations administrator should remove translations from that page until it is stable.  For example, currently I'm trying to remove a bug that was documented as a feature. But the reason Help:Search is unstable is not only because of that syntax, but also because of the operators that are being added.  And CirrusSearch is in beta, and the Search documentation is nowhere to be found, and it needs lots of work.  Currently there are 130 translations units getting in the way.  So either document how to edit pages with translations on them, and leave out the cruft of administration (I've read some of your links, and learned a few things, but TO NO AVAIL), or reduce the number of units, or remove translations temporarily.  Thanks. Cpiral (talk) 06:40, 11 September 2015 (UTC)


 * There is no "insource" at Help:Search: I don't understand what you are talking about. The report you linked suggests you might be talking of Help:CirrusSearch. Please paste the text you are trying to save and I'll tell you what's the issue. --Nemo 06:57, 11 September 2015 (UTC)


 * I changed the formerly-off redirect Help:search to Help:cirrussearch, where it belongs per Special:version. Cpiral (talk) 01:45, 12 September 2015 (UTC)

insource:
This can pick up template arguments, URLs, links, html, etc.

It has two forms. They both search the wikitext, but one is an indexed-based search, and the other is based on a regex search.

Tip: Instead of running a bare insource:/regexp/, these return much much faster when you limit the regexp search-domain to the results of one or more index-based searches.

   

   

 

Any search without a namespace or prefix searches your default search domain, settable at Special:Search. It is commonly reset by power users to ALL namespaces, but if this occurs for a bare regexp search, it will probably incur an HTML timeout.

Regex are character-wise per-page searches.

All other search terms use an index. When using a regex, include other search terms to limit the regex search domain as much as possible.

To develop a new regexp, or refine a complex regexp, use  in any edit box. This limits the regexp search domain to the current pagename. Use  to test your regexp on a few pages.

Metacharacters
The use of a regexp to search for an exact string that includes non-alphanumeric characters is a basic search. It finds regular expression metacharacters literally, but you must "escape" them, usually one at a time with a backslash.

For example / matches a literal dash, dot, or square bracket.

But you can also safely "quote" any characters using double-quotes inside a regexp and this will neutralize all metacharacter meaning to perform a basic, exact-string search:

Inside double quotes you must use backslash-escape to escape the double-quote character, for example.

Inside the regexp you must use the backslash-escape to quote the slash character that is the closing delimiter.

The square-bracket notation (for creating your own character-class) also escapes metacharacters.

You can escape any metacharacter that happens to be included, except that the right square bracket must be escaped or a dash must be backslash escaped. them as just shown, or just the first position can be used:  or , either of which match a dot, dash or right square bracket.

For the actual meaning of the metacharacters see the [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-regexp-query.html#regexp-syntax explanation of the syntax].

For the formal definition see the [http://lucene.apache.org/core/4_8_1/core/org/apache/lucene/util/automaton/RegExp.html Lucene grammar for regular expressions].

For example, using metacharacters to find the usage of a template called Val having, inside the template call, an unnamed parameter containing a possibly signed, three to four digit number, possibly surrounded by space characters, AND on the same page, inside a template Val call, a named argument "fmt=commas" having any allowable spaces around it, (it could be the same template call, or a separate one):



It is fast because it uses two filters so that every page the regexp crawls has the highest possible potential.

Assuming your search domain is set to ALL, it searches the entire wiki, because it offers no namespace or prefix.