Changes between Version 1 and Version 2 of 1.1/InterTrac

Timestamp:

Nov 13, 2014, 3:19:22 AM (10 years ago)

Author:

Ryan J Ollos

Comment:

Removed documentation for compat attribute. Refs #11823.

1.1/InterTrac

@@ -60 +60 @@
 when moving the cursor over an InterTrac links.
 
-Finally, the `.compat` option can be used to activate or disable
-a ''compatibility'' mode:
- * If the targeted Trac is running a version below [trac:milestone:0.10 0.10] 
-   ([trac:r3526 r3526] to be precise), then it doesn't know how to dispatch an InterTrac 
-   link, and it's up to the local Trac to prepare the correct link. 
-   Not all links will work that way, but the most common do. 
-   This is called the compatibility mode, and is `false` by default. 
- * If you know that the remote Trac knows how to dispatch InterTrac links, 
-   you can explicitly disable this compatibility mode and then ''any'' 
-   TracLinks can become an InterTrac link.
-
 Now, given the above configuration, one could create the following links:
  * to this InterTrac page:
@@ -83 +72 @@
    * `trac:changeset:1912` trac:changeset:1912
    * `[T1912]` [T1912]
- * to the log range [3300:3330]: '''(Note: the following ones need `trac.compat=false`)'''
+ * to the log range [3300:3330]:
    * `trac:log:@3300:3330` trac:log:@3300:3330  
    * `[trac 3300:3330]` [trac 3300:3330] 
- * 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'')
+ * 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'')
 
 The generic form `intertrac_prefix:module:id` is translated