particular C<< key => value >> pair is translatable. This is of
very limited usefulness.
-C<#loc_right_pair> does NOT exist. C<#loc> works in such cases since
-its parser does not extend beyond the string at the end of a line.
+C<#loc_right_pair> does NOT exist. C<#loc> works in such cases since its
+parser does not extend beyond the string at the end of a line. However,
+if the string is I<not> at the end of the line, C<#loc{word}> declares
+that the value associated with the key I<word> (earlier on the same
+line) is to be loc'd. This is useful for inline hashes:
+
+ # Note the string "baz" is to be loc'd
+ foo => { bar => "baz", troz => "zort" }, # loc{bar}
=head1 Development tips
You'll need to configure RT and make sure you have all the dependencies
before running tests. To do this in place without installing:
- ./configure.ac --with-my-user-group --enable-layout=inplace --with-devel-mode
+ ./configure.ac --with-my-user-group --enable-layout=inplace --enable-developer
make testdeps
make fixdeps
=head1 git quickstart
+The process below describes how to get a copy of an RT repo,
+modify it, and submit your changes as a patch. You can also create
+an account on GitHub, fork RT, and submit a PR. GitHub has documentation
+on this process: L<https://help.github.com/articles/fork-a-repo/>.
+
=over
=item 1.
=item 9.
Attach these files to an email using your standard email client, and
-send it to C<rt-devel@bestpractical.com>.
+send it to C<rt-bugs@bestpractical.com>. This will create a ticket in
+our public RT instance at L<https://issues.bestpractical.com>.
=back