We can insert Japanese characters on Sybase ASE where datatype of column is varchar. The same is replicated to MSSQL server without any issues when integrate is run in burst mode. The same doesn't works with continuous mode.

However, when we insert Japanese characters on MSSQL column of datatype varchar, during replication to ASE, data is garbled.

We can insert and retrieve the same data on MSSQL via Management Studio or Aqua data studio. We need HVR to do this during replication.

We need to have ability to replicate multibyte data in varchar from Sybase to MSSQL and vice versa in both continuous mode and burst mode.

We opened a support ticket for this with you and were provided a workaround of using univarchar on Sybase and to enable unicode conversion. However, that cannot be done due to following reasons - 

1. Client applications may receive garbled text
   If the client uses a different charset (e.g., UTF-8 or SJIS) than the server (iso_1), text will not be converted, resulting in unreadable characters.

2. Replication issues may worsen
   Replication Server or HVR often relies on conversions for multilingual data. Disabling conversions can cause:

   • Incorrect data in target MSSQL (e.g., mojibake for Japanese text).
   • Possible replication errors if the target collation expects Unicode.

3. Stored procedures and triggers may fail
   If they assume conversions for comparisons or sorting, behavior can change unexpectedly.

4. Mixed-language environments break
   Any client that isn’t using the same charset as ASE will see incorrect data.

5. No fallback for Unicode
   If you have enable unicode conversions turned on, disabling conversions overrides that.

Please help to include the ability to replicate Japanese characters / German Characters or any multibyte characters which can be stored on varchar datatype from Sybase to MSSQL and vice versa ASAP in both continuous and burst integrate mode.