<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2008-12-20T13:38:53Z</created-on>
  <description>Runtime error after SEEN3429 &lt;0246&gt;</description>
  <from-support type="integer">0</from-support>
  <id type="integer">237114</id>
  <importance type="integer">1</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>chLRt-ZfOr3zMtab7jnrAJ</notification-list>
  <number type="integer">1</number>
  <priority type="integer">3</priority>
  <reporter-id>chLRt-ZfOr3zMtab7jnrAJ</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Runtime error -  SEEN snapshot - 20081207</summary>
  <updated-at type="datetime">2010-08-24T09:42:42Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>chLRt-ZfOr3zMtab7jnrAJ</id><login>ToastOfDoom</login><login_name warning="deprecated">ToastOfDoom</login_name><name>ToastOfDoom</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2008-12-20T18:09:09Z</created-on>
  <description>A runtime error occurs in the scene where Ushio loses her toy in the field of flowers. This is with Japanese non-unicode set, using the 20081207 SEEN snapshot on the voice-patched original unvoiced game. The save file &quot;save999&quot; was copied over from a previous installation which unlocked everything, and as such the girl is seen on the title screen rather than the colleciton of lights.

The SAVEDATA that would recreate this situation can be found here: http://www.sendspace.com/file/ofafeg</description>
  <from-support type="integer">0</from-support>
  <id type="integer">237169</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>bQb3T8ZMer3zP0ab7jnrAJ</notification-list>
  <number type="integer">2</number>
  <priority type="integer">3</priority>
  <reporter-id>bQb3T8ZMer3zP0ab7jnrAJ</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Runtime error -  SEEN snapshot 20081207 (Late After Story)</summary>
  <updated-at type="datetime">2010-08-24T09:42:44Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>bQb3T8ZMer3zP0ab7jnrAJ</id><login>Nate RFB</login><login_name warning="deprecated">Nate RFB</login_name><name>Nate RFB</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2008-12-22T05:32:08Z</created-on>
  <description>Occasionally &quot;Tomoya&quot; (or what your character's name is) is displayed for no apparent reason.

Example: 

SEEN3509
&lt;0231&gt; And, on the way..
? Kyou says &quot;ah..&quot; &quot;Tomoya&quot; is shown
&lt;0232&gt; A meeting...

Savefile for SEEN_snapshot_20081207
http://www.sendspace.com/file/es343o</description>
  <from-support type="integer">0</from-support>
  <id type="integer">237737</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>chLRt-ZfOr3zMtab7jnrAJ</notification-list>
  <number type="integer">3</number>
  <priority type="integer">3</priority>
  <reporter-id>chLRt-ZfOr3zMtab7jnrAJ</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Random &quot;Tomoya&quot; lines</summary>
  <updated-at type="datetime">2011-09-21T15:33:24Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>chLRt-ZfOr3zMtab7jnrAJ</id><login>ToastOfDoom</login><login_name warning="deprecated">ToastOfDoom</login_name><name>ToastOfDoom</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-01-04T07:08:05Z</created-on>
  <description>While testing the game through the 20081207 snapshot, I was told by the game to make a ticket when a sudden issue came up.

At SEEN6417 just before the passage(?) &lt;0720&gt; occurs, there appears three lines stating &quot;No valid string, make a ticket about it&quot;. In the interest of being helpful, that is what I have done. I made a save file at this point; when loading it, usually REALLIVE freezes before anything can occur and sometimes it doesn't, so I guess it is a little fatal.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">244910</id>
  <importance type="integer">4</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>ae5rOO2IKr3z1Yab7jnrAJ</notification-list>
  <number type="integer">4</number>
  <priority type="integer">3</priority>
  <reporter-id>ae5rOO2IKr3z1Yab7jnrAJ</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>No Valid String - SEEN snapshot 20081207</summary>
  <updated-at type="datetime">2011-09-21T15:33:24Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>ae5rOO2IKr3z1Yab7jnrAJ</id><login>OmegaPhlare</login><login_name warning="deprecated">OmegaPhlare</login_name><name>OmegaPhlare</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-02-06T20:47:51Z</created-on>
  <description>In Kotomi's path, on April 24th, I was introducing Kotomi to Fujibayashi Ryou. During the fortune telling, a line includes comments and suggestions for translation (totalling nine clicks). This occurs occasionally, but here the extra information gives away spoilers towards even Kotomi's ending. There is likely a missing quotation mark or something.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">274574</id>
  <importance type="integer">6</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>aZkLqY9i4r3AiLeJe5afGb</notification-list>
  <number type="integer">6</number>
  <priority type="integer">3</priority>
  <reporter-id>aZkLqY9i4r3AiLeJe5afGb</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Runtime Error: 12/20 FV Build</summary>
  <updated-at type="datetime">2010-08-24T09:55:35Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>aZkLqY9i4r3AiLeJe5afGb</id><login>pondrthis</login><login_name warning="deprecated">pondrthis</login_name><name>pondrthis</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>ddwExa64ur3Bwfab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-02-09T20:32:05Z</created-on>
  <description>I'll post the SEEN files this and the last errors are in as soon as the wiki is back up (that's where I look over the SEEN files).

April 25th, Fuuko's route:
Throughout this whole day, the following error is repeated a multitude of times:

I'm seeing that a huge amount of occurences of &quot;Tomoya-kun&quot; are being replaced by, &quot;No valid string, make a ticket about it&quot; and &quot;Furukawa&quot; by &quot; &quot;. This may be the whole SEEN file (I'm thinking Fuuko's 4/25 SEEN).</description>
  <from-support type="integer">0</from-support>
  <id type="integer">276640</id>
  <importance type="integer">8</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>aZkLqY9i4r3AiLeJe5afGb,ddwExa64ur3Bwfab7jnrAJ</notification-list>
  <number type="integer">8</number>
  <priority type="integer">3</priority>
  <reporter-id>aZkLqY9i4r3AiLeJe5afGb</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>FV 12/20 Build error</summary>
  <updated-at type="datetime">2010-08-24T09:56:18Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>ddwExa64ur3Bwfab7jnrAJ</id><login>Shizuka</login><login_name warning="deprecated">Shizuka</login_name><name>Shizuka</name></assigned-to>
  <reporter><id>aZkLqY9i4r3AiLeJe5afGb</id><login>pondrthis</login><login_name warning="deprecated">pondrthis</login_name><name>pondrthis</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-03-25T17:46:58Z</created-on>
  <description>When using this translation patch the name of the character currently speaking (unless, of course, we are listening to Tomoya's thoughts and narrative) is displayed in a separate frame above the text frame. This is a break with how the original version of the game handles this (I don't know about FULL VOICE). 
In addition I think it's annoying because the additional floating window obstructs your view of the great game art.

I think this should be turned back to the original game's behavior, displaying the names of characters within the text frame and indenting spoken lines. By doing this, the Look &amp; Feel of the original game would be maintained, which I think is very important.

Comments and discussion welcome.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">316636</id>
  <importance type="integer">12</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cRQwiugwmr3RDteJe5afGb</notification-list>
  <number type="integer">12</number>
  <priority type="integer">3</priority>
  <reporter-id>cRQwiugwmr3RDteJe5afGb</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Names of characters are displayed separately</summary>
  <updated-at type="datetime">2010-08-24T10:10:13Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>cRQwiugwmr3RDteJe5afGb</id><login>Keksmeister</login><login_name warning="deprecated">Keksmeister</login_name><name>Keksmeister</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-04-23T06:09:10Z</created-on>
  <description>Kepago code in the SEEN9075.KE file places the location of the text below the cutoff box for rlBabel. This results in clipped text at the bottom.

Note that regular text terminates two or three pixels above the (invisible) cutoff box normally, it's just the KE that forces the location of the text.

This is tested on FV, but could be present on VP as well.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">345574</id>
  <importance type="integer">15</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>ddwExa64ur3Bwfab7jnrAJ</notification-list>
  <number type="integer">15</number>
  <priority type="integer">3</priority>
  <reporter-id>ddwExa64ur3Bwfab7jnrAJ</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>rlBabel FV(VP?) SEEN9075 bug</summary>
  <updated-at type="datetime">2010-08-24T10:21:05Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>ddwExa64ur3Bwfab7jnrAJ</id><login>Shizuka</login><login_name warning="deprecated">Shizuka</login_name><name>Shizuka</name></reporter>
</ticket>
<ticket>
  <assigned-to-id></assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-01-25T09:28:04Z</created-on>
  <description>I've checked pretty much all the .ke files for untranslated text and come up with this list (may not be complete).
I just checked .ke files for any lines that weren't separated into utf files and so have yet to be translated.
When listing which res line they come after I mean in the actual file, not based on in-game events.
Any of the form *SEEN files have lines where the Character speaking and the Spoken words are in one string variable, not separated into two.

SEEN1005.ke after res&lt;0339&gt; (4 lines = Fuuko and a Female Student talk)

SEEN1423.ke after res&lt;0038&gt; (4 lines = Tomoya and Sunohara talk)

SEEN1518.ke after res&lt;0371&gt; (7 lines = Tomoya, Sunohara, Nagisa or Furukawa [Nagisa] talk)

*SEEN2424.ke after res&lt;0106&gt; (4 lines immediately after, 10 lines after @15)
One weird thing to note in SEEN2424 is that soon after res&lt;0106&gt; there is a line with two apostrophes and nothing else. Is this a valid code line?

*SEEN2506.ke after res&lt;0587&gt;, res&lt;0611&gt;, and res&lt;0615&gt; (1 line each = Sunohara says something interesting. Same line 3 times.)

*SEEN2507.ke after res&lt;0018&gt; and res&lt;0061&gt; (1 line each, same as SEEN2506 = Sunohara talks)

SEEN3418.ke after res&lt;0145&gt;, res&lt;0251&gt;, res&lt;0391&gt;, and res&lt;0425&gt; (3 lines each = Kyou and Tomoya talk. Same 4 lines repeated, speaker order varies sometimes.)
SEEN3418.ke after res&lt;0388&gt; (3 lines = Kyou and Tomoya talk.)

SEEN3419.ke after res&lt;0050&gt; (5 lines = Sunohara, Tomoya, and ?? [Botan] talk)

SEEN3424.ke after res&lt;0092&gt;, res&lt;0557&gt;, and res&lt;0563&gt; (3 lines each = Tomoya and Kyou talk. Same 3 lines repeated.)
SEEN3424.ke after res&lt;0549&gt; (3 lines = Tomoya and Kyou talk)

SEEN3425.ke after res&lt;0111&gt; (3 lines = same lines as the first set in SEEN3424, Tomoya and Kyou talk)

SEEN3426.ke after res&lt;0188&gt; (3 lines = Tomoya and Kyou talk)

SEEN3429.ke after res&lt;0246&gt; (4 lines = Ryou and Kyou talk. Kinny Riddle mentioned these lines in the utf SEEN)

SEEN5424.ke after res&lt;0130&gt; (6 lines = Sunohara and Tomoya talk)

SEEN7100.ke after res&lt;1077&gt; (4 lines = Nagisa and Sanae talk)
SEEN7100.ke after res&lt;1265&gt; (3 lines = Nagisa and Tomoya talk)
SEEN7100.ke after res&lt;1605&gt; (3 lines = Nagisa and Tomoya talk)

SEEN7300.ke after res&lt;0224&gt; (3 lines = Tomoya and Sunohara talk)

SEEN7400.ke after res&lt;0522&gt; and res&lt;0530&gt; (3 lines each = Tomoya and Sunohara talk. Repeated lines.)
SEEN7400.ke after res&lt;0527&gt; (3 lines = Tomoya and Sunohara talk)
SEEN7400.ke after res&lt;1182&gt; (3 lines = Tomoya and Sunohara talk)
SEEN7400.ke after res&lt;2509&gt; (3 lines = Tomoya and Mei talk)
SEEN7400.ke after res&lt;2522&gt; (3 lines = Tomoya and Mei talk)</description>
  <from-support type="integer">0</from-support>
  <id type="integer">874409</id>
  <importance type="integer">17</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>daFGVycyqr37PueJe5aVNr</notification-list>
  <number type="integer">17</number>
  <priority type="integer">3</priority>
  <reporter-id>daFGVycyqr37PueJe5aVNr</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>ke files with Untranslated characters</summary>
  <updated-at type="datetime">2011-09-21T15:33:24Z</updated-at>
  <working-hours type="float">0.0</working-hours>
  <working-hour type="float" warning="deprecated">0.0</working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to></assigned-to>
  <reporter><id>daFGVycyqr37PueJe5aVNr</id><login>ZeikJT</login><login_name warning="deprecated">ZeikJT</login_name><name>ZeikJT</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>cRQwiugwmr3RDteJe5afGb</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2010-03-21T19:00:34Z</created-on>
  <description>After playing the final prank on Fuuko and achieving &quot;Fuuko Master&quot; status, BGM stops and won't ever return.

After playing the prank, BGM fades then two messages pop up, one after another. There is no text (I assume it's untranslated) but the fanfare is played.

Normally, when only one message is displayed the BGM correctly comes back on. This time, with two consecutive messages the BGM stays off and doesn't come back on.

Whenever you play a prank on Fuuko and &quot;level up&quot; or become &quot;master&quot;, the game does a farcall() to SEEN9070.ke. 
So I added an additional bgmUnMute() call to SEEN9070, right before it returns from the farcall(). That is to ensure the BGM is turned back on.

It fixes the issue I described above, but I don't know if it might lead to undesired behavior in other places. There might be a smarter fix.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">1116661</id>
  <importance type="integer">18</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>cRQwiugwmr3RDteJe5afGb</notification-list>
  <number type="integer">18</number>
  <priority type="integer">3</priority>
  <reporter-id>cRQwiugwmr3RDteJe5afGb</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>BGM goes missing after achieving &quot;Fuuko Master&quot;</summary>
  <updated-at type="datetime">2010-08-24T13:58:10Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>cRQwiugwmr3RDteJe5afGb</id><login>Keksmeister</login><login_name warning="deprecated">Keksmeister</login_name><name>Keksmeister</name></assigned-to>
  <reporter><id>cRQwiugwmr3RDteJe5afGb</id><login>Keksmeister</login><login_name warning="deprecated">Keksmeister</login_name><name>Keksmeister</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>ddwExa64ur3Bwfab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-02-09T05:21:14Z</created-on>
  <description>When running the FV 12/20 build, I came upon a situation where a character without a gender-specific name (or, presumably, line) was confused with a member of the opposite sex. There may be more cases of this in the FV version of CLANNAD.

The case I came across was on April 22nd, in Fuuko's path (most of the scenes so far are shared with Koumura's and Furukawa's path). The character was &quot;Teacher&quot; in the staff lounge. &quot;Finding a teacher I recognize...&quot; refers to &quot;him&quot; and the voice acting is clearly feminine.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">275653</id>
  <importance type="integer">7</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>aZkLqY9i4r3AiLeJe5afGb,ddwExa64ur3Bwfab7jnrAJ</notification-list>
  <number type="integer">7</number>
  <priority type="integer">4</priority>
  <reporter-id>aZkLqY9i4r3AiLeJe5afGb</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>FV Extra Gender Confusion</summary>
  <updated-at type="datetime">2010-08-24T09:55:58Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>ddwExa64ur3Bwfab7jnrAJ</id><login>Shizuka</login><login_name warning="deprecated">Shizuka</login_name><name>Shizuka</name></assigned-to>
  <reporter><id>aZkLqY9i4r3AiLeJe5afGb</id><login>pondrthis</login><login_name warning="deprecated">pondrthis</login_name><name>pondrthis</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>ddwExa64ur3Bwfab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-04-23T00:56:18Z</created-on>
  <description>Loading screen (SEEN95xx)
Saving screen (SEEN95xx)
Fuuko List Box Choices &amp; Level Up notifications (scattered throughout KE files)

aka. Special Cases where rlBabel needs to be invoked but isn't.

Update after realizing 10L in #14: No, disabling / enabling rlBabel has no impact (although currently I have these SEENs compiling without rlBabel). This makes sense anyway: the resource strings aren't used to display the text, nor is there any Select's or Gloss'es to call in rlBabel.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">345314</id>
  <importance type="integer">13</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>ddwExa64ur3Bwfab7jnrAJ</notification-list>
  <number type="integer">13</number>
  <priority type="integer">5</priority>
  <reporter-id>ddwExa64ur3Bwfab7jnrAJ</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Full Voice has lots of places where rlBabel does not kick in.</summary>
  <updated-at type="datetime">2010-08-24T10:21:02Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>ddwExa64ur3Bwfab7jnrAJ</id><login>Shizuka</login><login_name warning="deprecated">Shizuka</login_name><name>Shizuka</name></assigned-to>
  <reporter><id>ddwExa64ur3Bwfab7jnrAJ</id><login>Shizuka</login><login_name warning="deprecated">Shizuka</login_name><name>Shizuka</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>ddwExa64ur3Bwfab7jnrAJ</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-04-23T03:55:39Z</created-on>
  <description>This ticket encompasses all instances of multiple people speaking at once. Most of the time, this is not split into the resource file, and therefore is untranslated. This causes issues during compilation and gameplay.

Remedies needed:
The text needs to be translated into English. Currently, JP text is stripped out by rlc. This leads to missing text display.

Places needing attention, dumped from Full Voice: (entrypoint 0 pauses, entrypoint 1 returns immediately) [VP version should be the same]
---------- SEEN1005.KE
farcall (9075, 0)
---------- SEEN1423.KE
farcall (9075, 0)
---------- SEEN1514.KE
farcall (9075, 0)
---------- SEEN1516.KE
farcall (9075, 0)
---------- SEEN1518.KE
farcall (9075, 0)
---------- SEEN3418.KE
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
---------- SEEN3419.KE
farcall (9075, 0)
---------- SEEN3424.KE
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
---------- SEEN3425.KE
farcall (9075, 0)
---------- SEEN3426.KE
farcall (9075, 0)
---------- SEEN3429.KE
farcall (9075, 0)
---------- SEEN3509.KE
farcall (9075, 0)
---------- SEEN5421.KE
farcall (9075, 0)
farcall (9075, 0)
---------- SEEN5424.KE
farcall (9075, 0)
farcall (9075, 0)
---------- SEEN5426.KE
farcall (9075, 0)
---------- SEEN6417.KE
farcall (9075, 0)
---------- SEEN6800.KE
farcall (9075, 0)
---------- SEEN6802.KE
farcall (9075, 0)
---------- SEEN7100.KE
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
---------- SEEN7300.KE
farcall (9075, 0)
---------- SEEN7400.KE
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
---------- SEEN7600.KE
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 0)
farcall (9075, 1)

Update:
10L: Resolved rlBabel problem. Moved SEEN9075 from Compile_Without_rlBabel to Compile_With_rlBabel (in my personal build script). I may move more files in the SEEN9xxx sequence out of there as I understand how they operate. This does NOT affect the save/load screens not working correctly!
However, discovered a rlBabel bug :/ see ticket #15 for screenshot
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">345408</id>
  <importance type="integer">14</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer"></milestone-id>
  <notification-list>ddwExa64ur3Bwfab7jnrAJ</notification-list>
  <number type="integer">14</number>
  <priority type="integer">5</priority>
  <reporter-id>ddwExa64ur3Bwfab7jnrAJ</reporter-id>
  <space-id>aLBRiEXnqr3ztFab7jnrAJ</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Simultaneous Speech untranslated: FV&amp;VP Kepago have Japanese</summary>
  <updated-at type="datetime">2011-09-21T18:58:04Z</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>ddwExa64ur3Bwfab7jnrAJ</id><login>Shizuka</login><login_name warning="deprecated">Shizuka</login_name><name>Shizuka</name></assigned-to>
  <reporter><id>ddwExa64ur3Bwfab7jnrAJ</id><login>Shizuka</login><login_name warning="deprecated">Shizuka</login_name><name>Shizuka</name></reporter>
</ticket>
</tickets>

