public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Aw: Re: [PATCH] Syntax fixes in several CGIs
Date: Wed, 30 Dec 2020 08:31:25 +0100	[thread overview]
Message-ID: <676b8f9d-16f7-a0a4-4a39-fc0d3ec08ce1@ipfire.org> (raw)
In-Reply-To: <trinity-abc22bbb-697c-449c-99be-3467dc7b4db5-1609271525337@3c-app-gmx-bap73>

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Hi,

On 29.12.2020 20:52, Bernhard Bitsch wrote:
> 
>> ...
> 
> First just an excuse. I wrote 'hash tag' without thinking thoroughly about the term. ;)
> I meant 'hash key'. If this key consists of just one word ( no spaces ) it is sufficient just to use this word as key.
> Your example uses a string with spaces, thus you must "stringify" the key.

Ok, got it.

>> But at the risk of sounding silly: I still got translation and
>> designation(?) problems, sorry.
>>
>> Hash tag = '$Lang::tr{'update'}'!?
>>
>> Stringifying = ???
>>
> 
> See above. In case of translation hash %Lang::tr many keys are composed of several words, requesting the string representation 'this is a key'.
> The example
>    value = '$Lang::tr{'update'}'
> could also read
>    value = '$Lang::tr{"update"}'
> not using the same delimiters for the string update.
> Remember, a regex automaton usually doesn't count, thus it cannot distinguish start and end delimeters. The second ' is treated as the end of the string.
> 
> Hope, this makes my suggestion a bit clearer.

Yep. Thanks a lot. ;-)

I hope I can remember this next time...

Best,
Matthias

P.S.: I know, why I have specialized on hardware - software is more
complicated. ;-)

  reply	other threads:[~2020-12-30  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 12:50 Matthias Fischer
2020-12-29 13:50 ` Aw: " Bernhard Bitsch
2020-12-29 16:51   ` Matthias Fischer
2020-12-29 19:52     ` Aw: " Bernhard Bitsch
2020-12-30  7:31       ` Matthias Fischer [this message]
2020-12-30 10:44     ` Leo Hofmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=676b8f9d-16f7-a0a4-4a39-fc0d3ec08ce1@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox