GNOME Bugzilla – Bug 735180
Typo
Last modified: 2014-09-19 14:08:37 UTC
In src/tracker-utils/tracker-info.c:65 "Instead of looking up a file name, treat the FILE arguments as actual IRIs (e.g. <file:///path/to/some/file.txt>)" It should be "URI", not "IRI".
(In reply to comment #0) > In src/tracker-utils/tracker-info.c:65 > > "Instead of looking up a file name, treat the FILE arguments as actual IRIs > (e.g. <file:///path/to/some/file.txt>)" > > It should be "URI", not "IRI". Hi there. Actually, it shouldn't be URI at all. If anything it should be IRI or URN. The difference is that IRI allows for UTF-8 "URNs", where as URN is supposed to be ASCII encoded. Given that so many terminals these days (and most of Tracker internally) deals with UTF-8 strings, it is more correct to allow and use IRI for the command line than URI. Having said all that, I don't think we're very consistent in some places and I dare say the command line tools could all do with being updated/fixed accordingly.
Ah, I didn't know IRI was an actual thing. Sorry about that. Maybe you should at least add a translator comment to explain what it's supposed to mean?
(In reply to comment #2) > Ah, I didn't know IRI was an actual thing. Sorry about that. Maybe you should > at least add a translator comment to explain what it's supposed to mean? Are you a translator? If so, I would be happy for you to copy/paste/add a comment as you see fit! :)
I am. I would need to understand what IRI is first. :) What is it an acronym for?
https://wiki.gnome.org/TranslationProject/DevGuidelines/Use%20comments https://en.wikipedia.org/wiki/Internationalized_resource_identifier
Thanks André. Aleksander, I also have a link which might be of interest: http://blog.4psa.com/url-urn-uri-iri-why-so-many/
(In reply to comment #4) > I am. I would need to understand what IRI is first. :) > > What is it an acronym for? Quoting from the article I linked to: "IRI (International Resource Identifier) is a generalization of the URI. While URI supports only ASCI encoding, IRI fully supports international characters. In practice, UTF-8 is the most popular encoding used for IRI." Since tracker-info is used on UTF-8 based terminals and we heavily use UTF-8 internally in Tracker, I would say it's currently correct as-is. I will mark as NOTABUG. Feel free to re-open if you have a counter argument. Thanks for reporting the bug ;)
Did you add a comment? :-) If you didn't should I reopen this report or file a new one?
(In reply to comment #8) > Did you add a comment? :-) > > If you didn't should I reopen this report or file a new one? So, the bug is about IRI being a typo, which it isn't. But! :) if you want a comment I can do that. But I wonder why it's needed here? Finally, I don't know think I can commit any fix or change here while we're in hard code freeze :/
It's needed because IRIs isn't as well known as URIs and translators a) will think it's a typo and/or b) need to find out how to translate it (yes, sometimes acronyms have local variants, like NATO is OTAN in French).
(In reply to comment #9) > Finally, I don't know think I can commit any fix or change here while we're in > hard code freeze :/ So I just asked to release team members who confirmed that adding a comment doesn't break hard code freeze. Go ahead. :)
Alexandre, thanks I've pushed a fix, let me know if you think the fix is not sufficient ;)
Perfect, thanks.