|
| msg11991 (view) |
Author: malte |
Date: 2026-02-13.12:19:55 |
|
It's not perfect because we now have to break paragraphs manually or else they can be very wide if you have a wide browser window, but that's certainly a great improvement over the previous situation. Thanks for taking care of this!
|
| msg11990 (view) |
Author: malte |
Date: 2026-02-13.12:18:28 |
|
If a short paragraph won't do, you need a long one. If your paragraph is shorter than it ought to be, one thing you can do is just repeat some sentences. If a short paragraph won't do, you need a long one. If your paragraph is shorter than it ought to be, one thing you can do is just repeat some sentences. If a short paragraph won't do, you need a long one. If your paragraph is shorter than it ought to be, one thing you can do is just repeat some sentences. If a short paragraph won't do, you need a long one. If your paragraph is shorter than it ought to be, one thing you can do is just repeat some sentences. If a short paragraph won't do, you need a long one. If your paragraph is shorter than it ought to be, one thing you can do is just repeat some sentences. If a short paragraph won't do, you need a long one. If your paragraph is shorter than it ought to be, one thing you can do is just repeat some sentences.
|
| msg11989 (view) |
Author: malte |
Date: 2026-02-13.12:17:06 |
|
Now that we have a dedicated URL namespace for this, I have moved the results
there:
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v10-base-30min-issue814-base-issue814-v10-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v10-issue814-v9-issue814-v10-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v11-base-hmax-30min-issue814-base-issue814-v11-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v1_7_10.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v1-issue814-base-issue814-v1-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v2-issue814-v1-issue814-v2-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v3-issue814-v2-issue814-v3-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v4-issue814-base-issue814-v4-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v5-issue814-v4-issue814-v5-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v6-issue814-v5-issue814-v6-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v7-issue814-v6-issue814-v7-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v8-issue814-v7-issue814-v8-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v9-issue814-v8-issue814-v9-compare.html
The old links to
_tmp_files/helmert/... are no longer valid.
|
| msg11987 (view) |
Author: davidspeck |
Date: 2026-02-13.10:56:39 |
|
We changed it for msg11965 of issue814 manually. Seems to work :)
|
| msg11986 (view) |
Author: davidspeck |
Date: 2026-02-13.10:53:21 |
|
@Malte Can you try if this soft line breaking is now how you like it? For old messages our change has no effect because the messages are stored the wrong way. We could change the messages in the database with a subsequent reindex step for the search. The question is if this worth it. Maybe for the link list of issue814.
|
| msg11985 (view) |
Author: davidspeck |
Date: 2026-02-13.10:49:32 |
|
This is a text for line breaks:
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v10-base-30min-issue814-base-issue814-v10-compare.html
https://ai.dmi.unibas.ch/_experiments/ai/downward/issue814/data/issue814-v10-issue814-v9-issue814-v10-compare.html
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
|
| msg11984 (view) |
Author: malte |
Date: 2026-02-12.18:15:32 |
|
OK, so with Chromium it does seem to wrap according to the actual width of the
text area in the browser, which also means it doesn't roundtrip. It's probably a
good idea to remove the hard wrap setting. That's also what ChatGPT says.
The question is whether we then want to wrap server-side to avoid extremely long
lines. (The drawback of this is that there may be situations were people want
really long lines due to ASCII art like tables etc.)
|
| msg11983 (view) |
Author: malte |
Date: 2026-02-12.18:13:47 |
|
With Chromium, it wraps more reasonably at least in the example -- although it's
certainly not after 80 characters, more like 120. (My browser windows was much
wider, more like 200 characters wide).
|
| msg11982 (view) |
Author: malte |
Date: 2026-02-12.18:11:57 |
|
Now testing with Chromium.
|
| msg11981 (view) |
Author: malte |
Date: 2026-02-12.18:02:50 |
|
The rewrapping problem seems to persist.
|
| msg11980 (view) |
Author: malte |
Date: 2026-02-12.18:02:27 |
|
I received a notification after Florian's message.
|
| msg11979 (view) |
Author: florian |
Date: 2026-02-12.18:01:39 |
|
Testing after upgrade
|
| msg11977 (view) |
Author: malte |
Date: 2026-02-10.15:49:36 |
|
OK, so it can also introduce new line-breaks into the summary if you don't
update it at all, i.e., the behaviour is not idempotent.
|
| msg11976 (view) |
Author: malte |
Date: 2026-02-10.15:48:37 |
|
I updated the summary a bunch of times, adding only the linebreaks between the
two paragraphs, but it consistently inserts at least one additional weird
linebreak. (I may have messed up one or two updates, and I'm not sure if the
behaviour is reproducible or the breaks occur in different places.)
|
| msg4671 (view) |
Author: florian |
Date: 2015-10-26.14:50:40 |
|
Testing the summary field. Why is it bold?
|
| msg4667 (view) |
Author: florian |
Date: 2015-10-26.12:46:27 |
|
Test the strikethrough feature.
dasldkn
laskdja
dasldkn
laskdja
dasldkn
laskdja
a~~asldkn
laskdja~~
~~ asldkn
laskdja~~
foo
asldkn
laskdja ~~
~~asldkn
laskdja ~~
~~bar
~~ asldkn
laskdja~~
dasldkn
laskdja
|
| msg5 (view) |
Author: malte |
Date: 2009-10-06.00:20:04 |
|
Malte Helmert wrote:
> Malte Helmert <helmert@informatik.uni-freiburg.de> added the comment:
>
> malte wrote:
>> New submission from malte <helmert@informatik.uni-freiburg.de>:
>>
>> Seems to be working.
>
> This is a reply to the initial comment through the mail interface.
And this is a reply to that reply, also through the mail interface.
|
| msg4 (view) |
Author: malte |
Date: 2009-10-06.00:20:02 |
|
malte wrote:
> malte <helmert@informatik.uni-freiburg.de> added the comment:
>
> This is a reply in the web interface with an attached file.
This is a reply to that reply from the mail interface, also with an
attached file.
|
| msg3 (view) |
Author: malte |
Date: 2009-10-06.00:15:02 |
|
malte wrote:
> New submission from malte <helmert@informatik.uni-freiburg.de>:
>
> Seems to be working.
This is a reply to the initial comment through the mail interface.
|
| msg2 (view) |
Author: malte |
Date: 2009-10-06.00:11:59 |
|
This is a reply in the web interface with an attached file.
|
| msg1 (view) |
Author: malte |
Date: 2009-10-06.00:10:53 |
|
Seems to be working.
|
|
| Date |
User |
Action |
Args |
| 2026-02-13 12:19:55 | malte | set | messages:
+ msg11991 |
| 2026-02-13 12:18:28 | malte | set | messages:
+ msg11990 |
| 2026-02-13 12:17:06 | malte | set | messages:
+ msg11989 |
| 2026-02-13 10:56:39 | davidspeck | set | messages:
+ msg11987 |
| 2026-02-13 10:53:21 | davidspeck | set | messages:
+ msg11986 |
| 2026-02-13 10:49:32 | davidspeck | set | messages:
+ msg11985 |
| 2026-02-12 21:12:08 | davidspeck | set | nosy:
+ davidspeck
summary: We updated the pull request to handle default values and bounds checks. This adds a dependency on the parser that we
originally wanted to avoid. We are fine with accepting this dependency for now as the default values and bounds are specified
as strings, so they have to be parsed in some form.
We also ran into a problem with the registry that we will solve in a separate issue (we did a hot-fix in the pull request for
now). -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we
originally wanted to avoid. We are fine with accepting this dependency for now
as the default values and bounds are specified
as strings, so they have to be parsed in some form.
We also ran into a problem with the registry that we will solve in a separate
issue (we did a hot-fix in the pull request for
now). |
| 2026-02-12 18:15:32 | malte | set | messages:
+ msg11984 |
| 2026-02-12 18:14:06 | malte | set | summary: We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we
originally wanted to avoid. We are fine with accepting this dependency for now
as the default values and bounds are specified
as strings, so they have to be parsed in some form.
We also ran into a problem with the registry that we will solve in a separate
issue (we did a hot-fix in the pull request for
now). -> We updated the pull request to handle default values and bounds checks. This adds a dependency on the parser that we
originally wanted to avoid. We are fine with accepting this dependency for now as the default values and bounds are specified
as strings, so they have to be parsed in some form.
We also ran into a problem with the registry that we will solve in a separate issue (we did a hot-fix in the pull request for
now). |
| 2026-02-12 18:13:47 | malte | set | messages:
+ msg11983
summary: We updated the pull request to handle default values and bounds checks. This adds a dependency on the parser that we
originally wanted to avoid. We are fine with accepting this dependency for now as the default values and bounds are specified
as strings, so they have to be parsed in some form.
We also ran into a problem with the registry that we will solve in a separate issue (we did a hot-fix in the pull request for
now). -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we
originally wanted to avoid. We are fine with accepting this dependency for now
as the default values and bounds are specified
as strings, so they have to be parsed in some form.
We also ran into a problem with the registry that we will solve in a separate
issue (we did a hot-fix in the pull request for
now). |
| 2026-02-12 18:11:57 | malte | set | messages:
+ msg11982
summary: We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form.
We also ran into
a problem with the registry that we will solve in a separate issue (we did a
hot-fix in the pull request for now). -> We updated the pull request to handle default values and bounds checks. This adds a dependency on the parser that we
originally wanted to avoid. We are fine with accepting this dependency for now as the default values and bounds are specified
as strings, so they have to be parsed in some form.
We also ran into a problem with the registry that we will solve in a separate issue (we did a hot-fix in the pull request for
now). |
| 2026-02-12 18:02:50 | malte | set | messages:
+ msg11981 |
| 2026-02-12 18:02:27 | malte | set | messages:
+ msg11980
summary: We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into
a
problem with the registry that we will solve in a separate issue (we did a
hot-
fix in the pull request for now).
We also ran into a problem with the
registry
that we will solve in a separate issue (we did a hot-fix in the pull
request for
now). -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form.
We also ran into
a problem with the registry that we will solve in a separate issue (we did a
hot-fix in the pull request for now). |
| 2026-02-12 18:01:39 | florian | set | messages:
+ msg11979 |
| 2026-02-10 15:49:36 | malte | set | messages:
+ msg11977 |
| 2026-02-10 15:48:37 | malte | set | messages:
+ msg11976
summary: We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into a
problem with the registry that we will solve in a separate issue (we did a hot-
fix in the pull request for now).
We also ran into a problem with the registry
that we will solve in a separate issue (we did a hot-fix in the pull request for
now). -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into
a
problem with the registry that we will solve in a separate issue (we did a
hot-
fix in the pull request for now).
We also ran into a problem with the
registry
that we will solve in a separate issue (we did a hot-fix in the pull
request for
now). |
| 2026-02-10 15:47:05 | malte | set | summary: We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into
a
problem with the registry that we will solve in a separate issue (we did a
hot-
fix in the pull request for now).
We also ran into a problem with the
registry that we will solve in a separate issue (we did a hot-fix in the pull
request for
now). -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into a
problem with the registry that we will solve in a separate issue (we did a hot-
fix in the pull request for now).
We also ran into a problem with the registry
that we will solve in a separate issue (we did a hot-fix in the pull request for
now). |
| 2026-02-10 15:46:49 | malte | set | summary: We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into a
problem with the registry that we will solve in a separate issue (we did a hot-
fix in the pull request for now).
We also ran into a problem with the registry
that we will solve in a separate issue (we did a hot-fix in the pull request for
now). -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into
a
problem with the registry that we will solve in a separate issue (we did a
hot-
fix in the pull request for now).
We also ran into a problem with the
registry that we will solve in a separate issue (we did a hot-fix in the pull
request for
now). |
| 2026-02-10 15:46:31 | malte | set | summary: We also ran into a problem with the registry that we will solve in a separate
issue (we did a hot-fix in the pull request for now). -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form. We also ran into a
problem with the registry that we will solve in a separate issue (we did a hot-
fix in the pull request for now).
We also ran into a problem with the registry
that we will solve in a separate issue (we did a hot-fix in the pull request for
now). |
| 2026-02-10 15:45:59 | malte | set | summary: We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form.
We also ran into
a problem with the registry that we will solve in a separate issue (we did a
hot-fix in the pull request for now). -> We also ran into a problem with the registry that we will solve in a separate
issue (we did a hot-fix in the pull request for now). |
| 2026-02-10 15:45:37 | malte | set | summary: I have edited the summary field again. Hip, hip. Hooray? I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h amklssg as fas I
asmn ~~asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm~~ lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh mklshkl;ahmkl
;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl
;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas -> We updated the pull request to handle default values and bounds checks. This
adds a dependency on the parser that we originally wanted to avoid. We are fine
with accepting this dependency for now as the default values and bounds are
specified as strings, so they have to be parsed in some form.
We also ran into
a problem with the registry that we will solve in a separate issue (we did a
hot-fix in the pull request for now). |
| 2015-10-26 17:09:18 | florian | set | summary: I have edited the summary field again. Hip, hip. Hooray? I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h amklssg as fas I
asmn ~~asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm~~ lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh mklshkl;ahmkl
;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl
;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm
lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas |
| 2015-10-26 17:08:39 | florian | set | summary: I have edited the summary field again.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h
amklssg as fas I asmn ~~asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h
amklssg as fas I asmn asasgasmogamslgm~~ lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas -> (no value) |
| 2015-10-26 17:03:56 | malte | set | title: This is a test issue. -> This is a cromulent test issue. |
| 2015-10-26 17:02:01 | malte | set | summary: I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h
amklssg as fas I asmn ~~asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h
amklssg as fas I asmn asasgasmogamslgm~~ lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas -> I have edited the summary field again.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h
amklssg as fas I asmn ~~asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h
amklssg as fas I asmn asasgasmogamslgm~~ lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas |
| 2015-10-26 15:19:55 | florian | set | summary: I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h
amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h
amklssg as fas I asmn asasgasmogamslgm lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas -> I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h
amklssg as fas I asmn ~~asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h
amklssg as fas I asmn asasgasmogamslgm~~ lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas |
| 2015-10-26 14:57:52 | florian | set | summary: I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas -> I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I
asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas Iasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h
amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h
amklssg as fas I asmn asasgasmogamslgm lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh
mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn
asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas |
| 2015-10-26 14:56:18 | florian | set | summary: I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mkls<hkl;a<hmkl ;hahasmkl;h amklssg as fas gmkl asgmkl as gmkasmkl gamkl sgmkl asgmnkl asmklg asgmkl ;asgmkl asmklg asmklga sgmkl;a sgkla smklgmkl asgmkl asmklga smklgmkl asgmkl asmklgasmkl;gmkl ;asmkl hahasdhadha<dhadahaaghkl asdlhnlasdh asdhadh. -> I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahhsdhmsd h;lsmd hsd;mlh asmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lahs;ld hsklmdhsmhsd;h sd;hmlsdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asgml;a sgl asglkas gasgasmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas I asmn asasgasmogamslgm lasdhmkldh mklshkl;ahmkl ;hahasmkl;h amklssg as fas |
| 2015-10-26 14:53:57 | florian | set | summary: I have edited the summary field.
Hip, hip. Hooray? -> I have edited the summary field.
Hip, hip. Hooray?
I asmn asasgasmogamslgm lasdhmkldh mkls<hkl;a<hmkl ;hahasmkl;h amklssg as fas gmkl asgmkl as gmkasmkl gamkl sgmkl asgmnkl asmklg asgmkl ;asgmkl asmklg asmklga sgmkl;a sgkla smklgmkl asgmkl asmklga smklgmkl asgmkl asmklgasmkl;gmkl ;asmkl hahasdhadha<dhadahaaghkl asdlhnlasdh asdhadh. |
| 2015-10-26 14:50:40 | florian | set | messages:
+ msg4671
summary: This is our new summary field.
Hip, hip. Hooray? -> I have edited the summary field.
Hip, hip. Hooray? |
| 2015-10-26 14:50:20 | florian | set | summary: This is our new summary field.
Hip, hip. Hooray? |
| 2015-10-26 12:46:27 | florian | set | nosy:
+ florian
messages:
+ msg4667 |
| 2009-10-07 17:41:04 | malte | set | status: chatting -> resolved
assignedto: malte |
| 2009-10-06 00:20:04 | malte | set | messages:
+ msg5 |
| 2009-10-06 00:20:02 | malte | set | files:
+ self-referential-screenshot.png
messages:
+ msg4 |
| 2009-10-06 00:15:02 | malte | set | messages:
+ msg3 |
| 2009-10-06 00:11:59 | malte | set | files:
+ AIJ09_Translator.pdf
status: unread -> chatting
messages:
+ msg2 |
| 2009-10-06 00:10:53 | malte | create | |
