taskSavannah Administration - Tasks: task #13284, In link markup with both url and...

 
 

task #13284: In link markup with both url and text, text superseeds actual given url

Submitted by:  Vincent Belaïche <vincentb1>
Submitted on:  Fri 08 Aug 2014 08:28:39 PM UTC  
 
Should Start On: Fri 08 Aug 2014 12:00:00 AM UTCShould be Finished on: Fri 08 Aug 2014 12:00:00 AM UTC
Category: SystemPriority: 5 - Normal
Status: NonePrivacy: Public
Percent Complete: 0%Assigned to: Assaf Gordon <agn>
Open/Closed: OpenEffort: 0.00

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Mon 10 Nov 2014 07:44:55 AM UTC, comment #6:

Hello,

My previous comment was just to add on the discussion about future of the markup language, not about the bug itself.

So, just to add this about the bug: I do not object either that the problem is closed without any action on savannah itself. However the trick of not using # in url text should be provided in the markup reminder recipes (also on gna! and puszcza...), please...

VBR,
Vincent.

Vincent Belaïche <vincentb1>
Mon 10 Nov 2014 07:40:43 AM UTC, comment #5:

Hello,

Thank you Assaf for the feedback. Just for my own information, is "common mark" what github is using (see https://guides.github.com/features/mastering-markdown/).

IMHO something like Emacs org-mode markup would definitely be the best choice. But I am not sure whether there is any PHP implementation thereof already existing.

Anyway, what you really need to support is:

  • All that savannah already has, of course.
  • a previewer !!!
  • code style both inline and as a block, language specific fontification for blocs is really a plus
  • it would be good if users could re-edit some comment and you can view or not comment history.

Vincent.

Vincent Belaïche <vincentb1>
Wed 29 Oct 2014 10:43:22 PM UTC, comment #4:

I don't have strong objections to closing without action, I guess, since I'm not going to fix it myself. As usual, though, I have to say that a wholesale switch of anything as fundamental as the markup from syntax X to syntax Y seems almost impossible to me. Supporting a new syntax in addition seems far more plausible.

thanks,
k

Karl Berry <karl>
Site Administrator
Wed 29 Oct 2014 07:22:42 PM UTC, comment #3:

Hello Vincent, Karl.

I was able to reproduce the bug, and an example of it is here:
https://savannah.gnu.org/task/index.php?13373

The bug happens with the comment part of the URL markup contains a hashmark.
As a temporary work-around, I'd recommend simply not including the hashmark in the URL markup, as so:
Which will be rendered as:
comment1

While it's possible to investigate the code (and perhaps even come up with a fix), IMHO it is not worth the trouble. The current MarkUp mechanism on GNU Savannah is very old and out-dated. Any time/effort invested would be better spent moving to newer, more stable markup variants (e.g. "common-mark"), which is definitely on my todo list.

Technically, it seems that a hashmark in the title part renders the following invalid HTML: a nested <a> tag, where the inner one is just a relative URL which points to the current page (which you've called "task_b" in your bug report)

Unless there's strong objection, I'm inclined to close this bug, and treat it as "wont-fix".

Comments welcomed,

- Assaf

Assaf Gordon <agn>
Site AdministratorIn charge of this item.
Wed 29 Oct 2014 06:41:34 PM UTC, comment #2:

oh, now i remember. you're not reporting a texinfo bug at all. you're reporting a savannah bug (the "task" tracker isn't really the right place, but whatever). ignore my last, sorry.

Assaf, can you look into this when you have a chance please? tx.

Karl Berry <karl>
Site Administrator
Wed 29 Oct 2014 06:39:39 PM UTC, comment #1:

Hi Vincent - sorry for the delay. also sorry, but i can't follow what you're describing as a bug from your description. your sample document doesn't use @url at all, and it's not clear to me exactly what arguments you are specifying, which is the crux of the matter.

http://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040url.html explains the intended behavior of the three possible arguments to @url (aka @uref) in the various output formats. can you check and if there's a potential problem, please give me a real sample document i can run, as you normally do?

thanks.

Karl Berry <karl>
Site Administrator
Fri 08 Aug 2014 08:28:39 PM UTC, original submission:

The description of the issue is in the attached document savannah_bug_p3.pdf

Vincent Belaïche <vincentb1>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #31872:  savannah_bug_p3.pdf added by vincentb1 (14kB - application/pdf)
file #31873:  savannah_bug.texi added by vincentb1 (1kB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by agn (Posted a comment)
  • -unavailable- added by karl (Posted a comment)
  • -unavailable- added by vincentb1 (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 29 Oct 2014 07:22:42 PM UTCagnCategoryApproved Projects to be Reviewed=>System
      Assigned toNone=>agn
    Wed 29 Oct 2014 06:39:39 PM UTCkarlCategoryNone=>Approved Projects to be Reviewed
    Fri 08 Aug 2014 08:28:39 PM UTCvincentb1Attached File-=>Added savannah_bug_p3.pdf, #31872
      Attached File-=>Added savannah_bug.texi, #31873

    Back to the top


    Powered by Savane 3.1-cleanup