{"action":"created","issue":{"url":"https://api.github.com/repos/tbeu/ModelicaSpecification/issues/726","repository_url":"https://api.github.com/repos/tbeu/ModelicaSpecification","labels_url":"https://api.github.com/repos/tbeu/ModelicaSpecification/issues/726/labels{/name}","comments_url":"https://api.github.com/repos/tbeu/ModelicaSpecification/issues/726/comments","events_url":"https://api.github.com/repos/tbeu/ModelicaSpecification/issues/726/events","html_url":"https://github.com/tbeu/ModelicaSpecification/issues/726","id":372286643,"node_id":"MDU6SXNzdWUzNzIyODY2NDM=","number":726,"title":"Improve and clarify common macros for Text display","user":{"login":"modelica-trac-importer","id":22202507,"node_id":"MDQ6VXNlcjIyMjAyNTA3","avatar_url":"https://avatars1.githubusercontent.com/u/22202507?v=4","gravatar_id":"","url":"https://api.github.com/users/modelica-trac-importer","html_url":"https://github.com/modelica-trac-importer","followers_url":"https://api.github.com/users/modelica-trac-importer/followers","following_url":"https://api.github.com/users/modelica-trac-importer/following{/other_user}","gists_url":"https://api.github.com/users/modelica-trac-importer/gists{/gist_id}","starred_url":"https://api.github.com/users/modelica-trac-importer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/modelica-trac-importer/subscriptions","organizations_url":"https://api.github.com/users/modelica-trac-importer/orgs","repos_url":"https://api.github.com/users/modelica-trac-importer/repos","events_url":"https://api.github.com/users/modelica-trac-importer/events{/privacy}","received_events_url":"https://api.github.com/users/modelica-trac-importer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"tbeu","id":5444067,"node_id":"MDQ6VXNlcjU0NDQwNjc=","avatar_url":"https://avatars0.githubusercontent.com/u/5444067?v=4","gravatar_id":"","url":"https://api.github.com/users/tbeu","html_url":"https://github.com/tbeu","followers_url":"https://api.github.com/users/tbeu/followers","following_url":"https://api.github.com/users/tbeu/following{/other_user}","gists_url":"https://api.github.com/users/tbeu/gists{/gist_id}","starred_url":"https://api.github.com/users/tbeu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tbeu/subscriptions","organizations_url":"https://api.github.com/users/tbeu/orgs","repos_url":"https://api.github.com/users/tbeu/repos","events_url":"https://api.github.com/users/tbeu/events{/privacy}","received_events_url":"https://api.github.com/users/tbeu/received_events","type":"User","site_admin":false},"assignees":[{"login":"tbeu","id":5444067,"node_id":"MDQ6VXNlcjU0NDQwNjc=","avatar_url":"https://avatars0.githubusercontent.com/u/5444067?v=4","gravatar_id":"","url":"https://api.github.com/users/tbeu","html_url":"https://github.com/tbeu","followers_url":"https://api.github.com/users/tbeu/followers","following_url":"https://api.github.com/users/tbeu/following{/other_user}","gists_url":"https://api.github.com/users/tbeu/gists{/gist_id}","starred_url":"https://api.github.com/users/tbeu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tbeu/subscriptions","organizations_url":"https://api.github.com/users/tbeu/orgs","repos_url":"https://api.github.com/users/tbeu/repos","events_url":"https://api.github.com/users/tbeu/events{/privacy}","received_events_url":"https://api.github.com/users/tbeu/received_events","type":"User","site_admin":false}],"milestone":null,"comments":8,"created_at":"2018-10-21T07:11:03Z","updated_at":"2018-10-21T07:12:44Z","closed_at":null,"author_association":"COLLABORATOR","body":"**Reported by beutlich on 10 Jan 2017 10:48 UTC**\nIn section 18.6.5.5 ist is stated that `%par` is replaced by the value of parameter par when the text is to be rendered. Having `%par` as macro makes it impossible to display a parameter value immediately followed by a non-word boundary character (e.g., `%parm`). I noticed that Dymola also supports macros with trailing `%`, which e.g., would display `%par%m` as expected. This optional `%` postfix should be standardized.\n\n----\n\nMigrated-From: https://trac.modelica.org/Modelica/ticket/2148"},"comment":{"url":"https://api.github.com/repos/tbeu/ModelicaSpecification/issues/comments/431644890","html_url":"https://github.com/tbeu/ModelicaSpecification/issues/726#issuecomment-431644890","issue_url":"https://api.github.com/repos/tbeu/ModelicaSpecification/issues/726","id":431644890,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMTY0NDg5MA==","user":{"login":"modelica-trac-importer","id":22202507,"node_id":"MDQ6VXNlcjIyMjAyNTA3","avatar_url":"https://avatars1.githubusercontent.com/u/22202507?v=4","gravatar_id":"","url":"https://api.github.com/users/modelica-trac-importer","html_url":"https://github.com/modelica-trac-importer","followers_url":"https://api.github.com/users/modelica-trac-importer/followers","following_url":"https://api.github.com/users/modelica-trac-importer/following{/other_user}","gists_url":"https://api.github.com/users/modelica-trac-importer/gists{/gist_id}","starred_url":"https://api.github.com/users/modelica-trac-importer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/modelica-trac-importer/subscriptions","organizations_url":"https://api.github.com/users/modelica-trac-importer/orgs","repos_url":"https://api.github.com/users/modelica-trac-importer/repos","events_url":"https://api.github.com/users/modelica-trac-importer/events{/privacy}","received_events_url":"https://api.github.com/users/modelica-trac-importer/received_events","type":"User","site_admin":false},"created_at":"2018-10-21T07:12:44Z","updated_at":"2018-10-21T07:12:44Z","author_association":"COLLABORATOR","body":"**Comment by volker&#46;beuter on 11 Jan 2017 08:49 UTC**\nReplying to [comment:8 henrikt]:\n> Besides the problem with parameters named `name`, it must also be clear what to do with `\"%xyz\"` in the presence of parameters `x` and `xy`.  Shortest or longest match?\n\nRegardless which separation character we use, i.e. if we write `%(par)m`, `%{par}m` or `%'par'm` I propose to specify that the parameter name has to be enclosed into a pair of that separation characters whenever a character legal in a parameter name (i.e. letter, digit or unserscore) follows. It that way we get rid of the question of shortest or longest match. It is a bit more typing in some cases, but it is a big gain in clarity. When you look at the source text you immediately know the name of the parameter designated here without having to look up what parameters are defined. This also prevents changing the display unintentionally when some new parameter which is a prefix of some existing parameter is introduced.\nIt is not only clearer from the user's point of view, but I guess also easier to implement without matching.\n> \n> We could then specify that before any parameter substitutions, `%name` is substituted by the component name, regardless of what follows.\n\nWell, in this special case it would also work with `%namexyz` but I'd personally prefer to have it with separation characters (i.e. `%'name'xyz` or similar) also here in order to have more unique syntax. "}}
{"actor":{"display_login":"modelica-trac-importer"}}