| 7 |   | An InterTrac link can be seen as a scoped TracLinks. | 
          
          
            | 8 |   | It is used for referring to a Trac resource  | 
          
          
            | 9 |   | (Wiki page, changeset, ticket, ...) located in another | 
          
          
            | 10 |   | Trac environment. | 
          
          
            | 11 |   |  | 
          
          
            | 12 |   | == List of Active InterTrac Prefixes == | 
          
          
            | 13 |   |  | 
          
          
            | 14 |   | [[InterTrac]] | 
          
          
            | 15 |   |  | 
          
          
            | 16 |   | == Link Syntax == | 
          
          
            | 17 |   |  | 
          
          
            | 18 |   | Simply use the name of the other Trac environment as a prefix,  | 
          
          
            | 19 |   | followed by a colon, ending with the resource located in the other environment. | 
          
          
            |   | 7 | Simply use the name of the other Trac environment as a prefix, followed by a colon, ending with the resource located in the other environment: | 
          
        
        
          
            | 32 |   | For convenience, there's also some alternative short-hand form,  | 
          
          
            | 33 |   | where one can use an alias as an immediate prefix  | 
          
          
            | 34 |   | for the identifier of a ticket, changeset or report: | 
          
          
            | 35 |   | (e.g. `#T234`, `[T1508]`, `[trac 1508]`, ...) | 
          
          
            |   | 19 | If the InterTrac link is enclosed in square brackets, like `[th:WikiExtrasPlugin]`, the InterTrac prefix is removed in the displayed link like a normal link resolver would be. For example, the above would be displayed as `WikiExtrasPlugin`. | 
          
        
        
          
            | 58 |   | The `.title` information will be used for providing an useful tooltip | 
          
          
            | 59 |   | when moving the cursor over an InterTrac links. | 
          
          
            | 60 |   |  | 
          
          
            | 61 |   | Finally, the `.compat` option can be used to activate or disable | 
          
          
            | 62 |   | a ''compatibility'' mode: | 
          
          
            | 63 |   |  * If the targeted Trac is running a version below milestone:0.10  | 
          
          
            | 64 |   |    (r3526 to be precise), then it doesn't know how to dispatch an InterTrac  | 
          
          
            | 65 |   |    link, and it's up to the local Trac to prepare the correct link.  | 
          
          
            | 66 |   |    Not all links will work that way, but the most common do.  | 
          
          
            | 67 |   |    This is called the compatibility mode, and is `true` by default.  | 
          
          
            | 68 |   |  * If you know that the remote Trac knows how to dispatch InterTrac links,  | 
          
          
            | 69 |   |    you can explicitely disable this compatibility mode and then ''any''  | 
          
          
            | 70 |   |    TracLinks can become an InterTrac link. | 
          
          
            |   | 40 | The `.title` information is used in a tooltip, ie when hovering the cursor over an InterTrac link. | 
          
        
        
          
            | 84 |   |  * to the log range [3300:3330]: '''(Note: the following ones need `trac.compat=false`)''' | 
          
          
            | 85 |   |    * `trac:log:@3300:3330` trac:log:@3300:3330   | 
          
          
            | 86 |   |    * `[trac 3300:3330]` [trac 3300:3330]  | 
          
          
            | 87 |   |  * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (''since 0.11; note that the ''remote'' Trac has to run 0.11 for this to work'') | 
          
          
            |   | 56 |  * to the log range [3300:3330]: | 
          
          
            |   | 57 |    * `trac:log:@3300:3330` trac:log:@3300:3330 | 
          
          
            |   | 58 |    * `[trac 3300:3330]` [trac 3300:3330] | 
          
          
            |   | 59 |    * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (note that the ''remote'' Trac has to run Trac >= 0.11 for this to work'') | 
          
        
        
          
            | 89 |   | The generic form `intertrac_prefix:module:id` is translated | 
          
          
            | 90 |   | to the corresponding URL `<remote>/module/id`, shorthand links | 
          
          
            | 91 |   | are specific to some modules (e.g. !#T234 is processed by the | 
          
          
            | 92 |   | ticket module) and for the rest (`intertrac_prefix:something`), | 
          
          
            | 93 |   | we rely on the TracSearch#quickjump facility of the remote Trac. | 
          
          
            |   | 61 | The generic form `intertrac_prefix:module:id` is translated to the corresponding URL `<remote>/module/id`. Shorthand links are specific to some modules (e.g. !#T234 is processed by the ticket module). For the rest (`intertrac_prefix:something`), we rely on the [TracSearch#quickjump quick jump] facility of the remote Trac. | 
          
          
            |   | 62 |  | 
          
          
            |   | 63 | == List of Active InterTrac Prefixes | 
          
          
            |   | 64 |  | 
          
          
            |   | 65 | The following InterTrac prefixes are available on this site: | 
          
          
            |   | 66 |  | 
          
          
            |   | 67 | [[InterTrac]] |