1 Reply by tenyuhuang

(3,508 replies, posted in General discussion)

Hi, I have four discs that has issues with DIC.

First disc (see: WINDOWS_MME_LOG.7z) gives me this GetLastError error, prompting on dumping the disc with "Subcode: 2", resulting in the dumping process being very slow. Another disc from Fujitsu (see: F-BASIC 386 V1.1_logs) have the same problem.

Second disc (see: WIN32_DOS622_OEM_logs) got stuck on "Checking EXE: 24" and refuse to move on, even if I remove the /sf flag;
There are a few very abnormal things in the logs:

QBASIC.EXE: offset is very big (1092628067). read skip [TODO]
SCANDISK.EXE: offset is very big (1092628067). read skip [TODO]
SETUP.EXE: offset is very big (1092628067). read skip [TODO]
UNDELETE.EXE: offset is very big (1092628067). read skip [TODO]

Are these MS-DOS files causing the EXE checking process to stall?

Third disc (see: PAYUTA_FRE_logs.7z) quit dumping after detecting a protected file ".Process$".

Could you look into the issues?

Thank you very much!

Go to forum: General discussion

2 Reply by tenyuhuang

(3,508 replies, posted in General discussion)

sarami wrote:
tenyuhuang wrote:

Here are the logs

It seems good.

Thank you very much for all the fixes!
May I ask what's the cause of those "sub indexes" and what are they? I've ran into dumps like this a few times and wans't sure why.

Go to forum: General discussion

3 Reply by tenyuhuang

(3,508 replies, posted in General discussion)

sarami wrote:
tenyuhuang wrote:

Probably it's this really huge offset that caused all these issues, is it?

Yes. Btw, the problem still exists in this dump. (subchannel)
I fixed it. Retest and upload all logs, plz.

Thanks again for the fix! Here are the logs big_smile

Go to forum: General discussion

4 Reply by tenyuhuang

(3,508 replies, posted in General discussion)

sarami wrote:

Re-uploaded. Link is same. Try again, plz.

Thank you very much! It worked! big_smile

Probably it's this really huge offset that caused all these issues, is it?

     Combined Offset(Byte)   9784, (Samples)  2446
    -   Drive Offset(Byte)    120, (Samples)    30
    ----------------------------------------------
           CD Offset(Byte)   9664, (Samples)  2416
    Overread sector: 5
    SubChannel Offset: 0

I've also attached all log files if anyone's interested.

Go to forum: General discussion

5 Reply by tenyuhuang

(3,508 replies, posted in General discussion)

sarami wrote:

@tenyuhuang
http://www.mediafire.com/file/eq80y20l9 … st.7z/file
Try and upload logs.

Thank you for the build, here's the logs:

Go to forum: General discussion

6 Reply by tenyuhuang

(3,508 replies, posted in General discussion)

sarami wrote:
tenyuhuang wrote:

Track 1 is supposed to be a data track

All logs, please.

These are all the generated logs.

Here's a screenshot from Isobuster, just in case.

Go to forum: General discussion

7 Reply by tenyuhuang

(3,508 replies, posted in General discussion)

"Failed to get write-offset" on erratic discs

I have a weird disc; DIC refuses to dump it because it keeps reporting "Failed to get write-offsets" on all of my 4 Plextors.

AppVersion
        x86, AnsiBuild, 20200709T220736
/c2 val2 was omitted. set [0]
/sf val was omitted. set [60]
F:\archives\#tools\Programs\Creator\ISO3\mk_demo_V\ doesn't exist, so create.
CurrentDirectory
        F:\archives\#tools\Programs\Creator
WorkingPath
         Argument: ISO3\mk_demo_V\mk_demo.bin
         FullPath: F:\archives\#tools\Programs\Creator\ISO3\mk_demo_V\mk_demo.bin
            Drive: F:
        Directory: \archives\#tools\Programs\Creator\ISO3\mk_demo_V\
         Filename: mk_demo
        Extension: .bin
StartTime: 2020-07-24T01:07:18+0800
Set the drive speed: 3528KB/sec
This drive supports [OpCode: 0xd8, SubCode: 0]
Failed to get write-offset
This drive supports [OpCode: 0xd8, SubCode: 1]
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 1/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 2/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 3/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 4/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 5/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 6/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 7/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 8/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
Retry 9/10 after 10000 milliseconds
This drive supports [OpCode: 0xd8, SubCode: 2]
Failed to get write-offset
This drive supports [OpCode: 0xd8, SubCode: 8]
Failed to get write-offset
EndTime: 2020-07-24T01:09:49+0800

When using px_d8 on the first 3 sectors, the output are as follows:

Using 1.01A:

F:\archives\#tools>px_d8_A J 0 0
Px_D8 v1.01A.  22 Oct 2008.  Truong Hy, Dremora.
Usage: px_d8 <drive letter> <LBA sector>

F:\archives\#tools>px_d8_A J 0
Error searching for sync!

Using 1.01:
(the output is mostly zeroes until the end of sector 2)

F:\archives\#tools>px_d8
Px_D8 v1.01.  09 Dec 2007.  Truong Hy.
Usage: px_d8 <drive letter> <LBA sector> [sub-ch bits]
sub-ch bits:
  0 or ommit for no sub-ch data
  1=16 PQ
  2=96 PW packed mode

F:\archives\#tools>px_d8 J 0 0
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000

F:\archives\#tools>px_d8 J 1 0
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000

F:\archives\#tools>px_d8 J 2 0
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
FB7F036001E8004E80346017680EAE84
7C6361E9E84ECEB454777F66A02AF81F
028801A6807AE0230819C68AD2E71D8A

Note that Track 1 is supposed to be a data track as opposed to audio; according to my limited understanding and suggestions from others, this is likely to a disc DIC isn't ready for (because its irrational mastering).

Could you look into the issue? Thank you very much!

Go to forum: General discussion

8 Reply by tenyuhuang

(1 replies, posted in General discussion)

Such a coincidence!
Just less than 24 hours after I read your interesting article, I ran into a ring protected DVD, too.

Click here to view the image.

It's not reflection or something, every drive and every dumping software on my side is moaning about it.

Now trying to dump it with Chef big_smile

Go to forum: General discussion

9 Reply by tenyuhuang

(13 replies, posted in General discussion)

F1ReB4LL wrote:

As I've said, it depends on the case. Japanese titles often have an English title and Japanese one is only on the side of the box or on the spine and the 'main' title is the English one.

In such scenario, are those Japanese texts usually Katakana transcriptions of the English title?

Deciding titles case by case is of course what we should do when actually adding something, but yeah the purpose of this post is to figure out a (mostly) working, supplementary rather than obligatory guide to let people who have no idea which title to pick for CJK games get their submission optimized big_smile

Go to forum: General discussion

10 Reply by tenyuhuang

(13 replies, posted in General discussion)

F1ReB4LL wrote:

When the ingame title is completely different from the box title - use the box one, the ingame one goes into the comments.
When the box has both Western and Eastern titles and the ingame title is Western - the Western one can be used as main title, another one goes into the comments.
Each case should be discussed separately, though.

Since the box would most likely be in the language of the region, so I assume it's overall a language-first approach? i.e. Games in Eastern languages use romanized Eastern titles, and vice versa...which we actually agree with, despite our approach are seemingly different.

Jackal wrote:

The No-Intro rules aren't suited for Chinese releases.. games can have really weird box titles that are completely different from the (often English) ingame title.

That is why I needed more site codes big_smile Fortunately it seems that I can do that with HTML codes anyway, not sure if there will be a difference in terms of indexing and searching tho.

Go to forum: General discussion

11 Reply by tenyuhuang

(13 replies, posted in General discussion)

So, after a few discussions with some collectors and archivists, it seems that under certain circumstances, overriding everything with in-game title (especially for domestic games) isn't a favorable plan.

For example here's a Chinese game called 致命武力2：觉醒, this Chinese title is seen on box, in media, on the official website, pretty much everywhere except in the game - when you get into the game, there is only "Thunder Force 2 Rebirth", which is only a small subtitle on the box and otherwise seen only once in the title screen. Given the situation, romanizing 致命武力2：觉醒 and make it the Latin title would be a better choice.

Therefore, it might be better to pick a title based on the language for domestic games (unless it's a phonetically translated title).

Go to forum: General discussion

12 Reply by tenyuhuang

(13 replies, posted in General discussion)

KailoKyra wrote:

For imported / exported release, use the in-game title to rule out everything else;

In which case, for CJK submissions, would the english in-game title prevails, or the one used by the version from the country of origin of the game) ?

If not, what if the in-game title is also localized ?

I feel like the packaging title is more important than the in-game title to reference a game, but sometimes it's indeed not applicable or just wrong.

Some examples would be better - so here's a few hypothetical but very common situations:

(A) A US game got imported to China, in-game title retained English -> use the English title;
(B) A US game got imported to China, in-game title translated into Chinese -> use the Chinese title.

This is where redump's non-Latin name & parent / clone function becomes useful big_smile

Also actually, I'm not sure whether deciding by title or language is more appropriate in this situation. That's one of the things we'll either need to think over or decide on a case-by-case scenario.

KailoKyra wrote:

If it's a domestic game without an official Latin / Germanic title, pick an appropriate Latin main title Romanized from the language of that region;

So just the name using pinyin for Chinese-only releases ? Or a "litteral/personnal translation" of the title to English ? I think that the latter might not be a good idea as the main title for an entry tongue


Will these entries, with other alphabets need to be fixed as well ? (and thus extend these naming principles to other games than CJK submissions ?)

To be honest I'd like to keep both, but yes you're right - the main title for each submission should be more objective, thus a literal translation is not preferable, i.e. plain Romanization is still a better option with main Latin title.

That's why I've additionally proposed an optional "Literal Translation" field for reference, despite not necessary for everyone (?).

For submissions of other languages, I'm not sure if similar regulation is in demand or necessary, so that's another story. I'd like to hear everyone's opinion about it tho.

Go to forum: General discussion

13 Reply by tenyuhuang

(13 replies, posted in General discussion)

JosJuice wrote:

Is there a particular reason you are suggesting to not mark tones? Problems with storing them in databases, or just that they're inconvenient to type? I'm not saying that it necessarily is a bad decision, but it would be good to note the reasoning.

Majority of the media outlets (in English), both domestic and foreign ones, aren't adopting tones either - maybe for the inconvenience to type, maybe because tones make the texts less readable, I'm not very sure, but it seems to be some kind of unannounced rules everybody magically abides to.

Also, I thought it would be a good a idea to introduce as little extra characters as possible to Latin name field, that is also why I'm reasoning about Umlaut ü smile

Go to forum: General discussion

14 Topic by tenyuhuang

(13 replies, posted in General discussion)

Hi everybody, I'm tenyuhuang a.k.a. Tenyu, from mainland China. I've joined redump.org last October, and has been dumping and submitting games since then. While I'm glad to have all the support and help from the team, since most of my submissions are either Chinese or Japanese, we began to run into some practical problem - one of them being: how to properly name a Chinese submission.

This proposal aims to solve, or figure out a way to solve that issue and move things forward, while providing hints and hopefully valid inputs to other related issues.

I've been writing this during the holiday where there is a lot of distractions, so my apologies in advance for my indecent English writing skills and grammar mistakes.

The full version of the proposal can be seen here.
Since it's a bit too long, I've also provided a significantly shorter version for easy reading and reference.

Bear in mind everything is suggested based on my own experience and knowledge, most of the content will be open for discussion, and I'll be expecting your valuable input.

Thanks in advance!

Update:
If no further suggestions / feedbacks are received by 2019/2/28, I'll finalize the first version of Pinyin adoption plan and CJK naming workflow for review and approval.

Go to forum: General discussion