Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

• Username
• Password
• Remember me

• Sign in using OpenID
• Remember me

• Forgot your password?
• Apply for membership

2-category 2-category-theory abelian-categories adjoint algebra algebraic algebraic-geometry algebraic-topology analysis analytic-geometry arithmetic arithmetic-geometry book bundles calculus categorical categories category category-theory chern-weil-theory cohesion cohesive-homotopy-type-theory cohomology colimits combinatorics complex complex-geometry computable-mathematics computer-science constructive cosmology deformation-theory descent diagrams differential differential-cohomology differential-equations differential-geometry digraphs duality elliptic-cohomology enriched fibration foundation foundations functional-analysis functor gauge-theory gebra geometric-quantization geometry graph graphs gravity grothendieck group group-theory harmonic-analysis higher higher-algebra higher-category-theory higher-differential-geometry higher-geometry higher-lie-theory higher-topos-theory homological homological-algebra homotopy homotopy-theory homotopy-type-theory index-theory integration integration-theory internal-categories k-theory lie-theory limits linear linear-algebra locale localization logic mathematics measure measure-theory modal modal-logic model model-category-theory monad monads monoidal monoidal-category-theory morphism motives motivic-cohomology nlab noncommutative noncommutative-geometry number-theory of operads operator operator-algebra order-theory pages pasting philosophy physics pro-object probability probability-theory quantization quantum quantum-field quantum-field-theory quantum-mechanics quantum-physics quantum-theory question representation representation-theory riemannian-geometry scheme schemes set set-theory sheaf simplicial space spin-geometry stable-homotopy-theory stack string string-theory superalgebra supergeometry svg symplectic-geometry synthetic-differential-geometry terminology theory topology topos topos-theory tqft type type-theory universal variational-calculus

1. • CommentRowNumber1.
   • CommentAuthorRodMcGuire
   • CommentTimeSep 28th 2013
   • PermaLink
   Author: RodMcGuire
   Format: MarkdownItexBoth the nLab and nForum are happy to accept some invisible Unicode characters that may cause problems. One example so far is the [U+200E left-to-right mark](http://en.wikipedia.org/wiki/Left-to-right_mark) which is mentioned [here](http://nforum.mathforge.org/discussion/5288/geometric-type-theory/?Focus=42051#Comment_42051) in the nForum where a Unicode LRM was probably introduced by copying and pasting. I don't understand enough of how nLab or nForum work to give a good solution but I would like something like the Unicode LRM character to be translated into `‎` in the editor so that it is visible. Then again if that happened then the current software would work fine as shown below. Maybe instead whatever URL delimiting tests that work for `‎` should be extended to Unicode LRMs. The current operation seems to be: | source | * | rendition | url string | |----------------|---------------------------------|---|----------------------------------------- | `[qux](http://w.com)` | * | [qux](http://w.comf‎) | http://w.com%e2%80%8e | | `[foo](http://x.com‎)` | | [foo](http://x.com‎) | http://x.com | | `[bar](http://y.com‎)` | | [bar](http://y.com‎) | http://y.com%e2%80%8e | where the `*` in the first line indicates that the source URL is terminated by an invisible Unicode LRM. I have no idea why `&ltm;` is not incorporated into a URL while the equivalent `‎` is.

   Both the nLab and nForum are happy to accept some invisible Unicode characters that may cause problems. One example so far is the U+200E left-to-right mark which is mentioned here in the nForum where a Unicode LRM was probably introduced by copying and pasting.

   I don’t understand enough of how nLab or nForum work to give a good solution but I would like something like the Unicode LRM character to be translated into ‎ in the editor so that it is visible. Then again if that happened then the current software would work fine as shown below. Maybe instead whatever URL delimiting tests that work for ‎ should be extended to Unicode LRMs.

   The current operation seems to be:

   source	*	rendition	url string
   [qux](http://w.com)	*	qux	http://w.com%e2%80%8e
   [foo](http://x.com‎)		‎foo	http://x.com
   [bar](http://y.com‎)		bar	http://y.com%e2%80%8e

   where the * in the first line indicates that the source URL is terminated by an invisible Unicode LRM.

   I have no idea why &ltm; is not incorporated into a URL while the equivalent ‎ is.

2. • CommentRowNumber2.
   • CommentAuthorTobyBartels
   • CommentTimeSep 29th 2013
   • PermaLink
   Author: TobyBartels
   Format: MarkdownItex>I have no idea why `‎` is not incorporated into a URL while the equivalent `‎` is. Weird.

   I have no idea why ‎ is not incorporated into a URL while the equivalent ‎ is.

   Weird.

3. • CommentRowNumber3.
   • CommentAuthorRodMcGuire
   • CommentTimeOct 31st 2013
   • (edited Oct 31st 2013)
   • PermaLink
   Author: RodMcGuire
   Format: MarkdownItexThe invisible LRM problem just [showed up in the nCafe](http://golem.ph.utexas.edu/category/2013/10/the_hott_approach_to_physics.html#c044859), so this issue is common to all 3 sites.

   The invisible LRM problem just showed up in the nCafe, so this issue is common to all 3 sites.

4. • CommentRowNumber4.
   • CommentAuthorRodMcGuire
   • CommentTimeNov 12th 2013
   • PermaLink
   Author: RodMcGuire
   Format: MarkdownItexA LRM showed up in [this nForum thread](http://nforum.mathforge.org/discussion/3322/univalence/?Focus=43141#Comment_43141) Urs says: > Those LRMs come from copying the green URLs in Google’s result list! > One can fix it by removing what looks like “pdf” at the end with the backspace key and then re-typing “pdf” (and pre-fixing the url with its “http://”). > Maybe this didn’t always used to be this way with Google. I do this fixing a lot lately.

   A LRM showed up in this nForum thread

   Urs says:

   Those LRMs come from copying the green URLs in Google’s result list!

   One can fix it by removing what looks like “pdf” at the end with the backspace key and then re-typing “pdf” (and pre-fixing the url with its “http://”).

   Maybe this didn’t always used to be this way with Google. I do this fixing a lot lately.