blocks|key|3963466|text|数据压缩可能是一种签出的可能性，但您不能仅仅将40字节的消息压缩为6个字节(例如)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3963467|如果可能的字符串/类型的空间有限，则将它们映射到列表(信息编码)。|3963468|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Data compression may be a possiblity to check out, but you can't just compress a 40-byte message to 6 bytes (for example). 

If the space of possible strings/types is limited, map them to a list (information coding).

blocks|key|3982438|text|我不知道有什么比基数64更好的了，如果你真的要传递这个值，并且用户必须输入它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3982439|如果您有一个中央数据存储区，它们都可以访问，那么您可以只给他们您保存它的行的ID。当然，这取决于这些数据的“秘密”程度。|3982440|但我怀疑，如果您试图使用这个激活，您需要他们有一个实际的价值。|3982441|字符串将如何传递？你能指望用户可能只是复制/粘贴吗？也许花了一些时间来清理来自电子邮件阅读器的多余的中断，甚至您的“从这里复制”和“复制到这里”行可能会产生更多的成果！|3982442|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I don't know of anything better than base-64 if you actually have to pass the value around and if users have to type it in.

If you have a central data store they can all access, you could just give them the ID of the row where you saved it. This of course depends on how "secret" this data needs to be.

But I suspect that if you're trying to use this for activation, you need them to have an actual value.

How will the string be passed? Can you expect users to perhaps just copy/paste? Maybe some time spent on clearing up superfluous line breaks that come from an email reader or even your "Copy from here" and "Copy to here" lines might bear more fruit!

blocks|key|1477521|text|字符串中的字符可以有不可打印的字符吗？如果是这样，则不需要对字节进行base64+64编码，只需从它们创建字符串(保存了33%25)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1477522|string+str+=+new+string(byteArray.Cast<char>().ToArray());|code-block|syntax|javascript|1477523|另外，字节数组中的值是否受到某种程度的限制？如果它们属于某个范围(即不是所有256个可能的值)，则可以考虑在字符串的每个字符中填充每个字符中的两个。|1477524|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Can the characters in your string have non-printable chars? If so, you don't need to base64-encode the bytes, you can simply create the string from them (saved 33%)

<pre><code>string str = new string(byteArray.Cast&lt;char&gt;().ToArray());
</code></pre>

Also, are the values in the byte array restricted somehow? If they fall into a certain range (i.e., not all of the 256 possible values), you can consider stuffing two of each in each character of the string.

blocks|key|3963488|text|如果你真的有37个字节的非冗余信息，那么你就倒霉了。压缩在某些情况下可能会有所帮助，但如果这是一个激活密钥，我建议使用长度相同的键(而且压缩不会强制执行此操作)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3963489|如果这段代码要通过电子邮件传递，那么我认为拥有一个更大的密钥没有问题。另一种选择可能是每5个左右的字符插入连字符，将其分解为较小的块(例如XXXXX-XXXXX-XXXXX-XXXXX-XXXXX)。|CODE|3963490|entityMap^0|1N|5|0|1H|3|1X|T|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|J|$]]

If you really have 37 bytes of non-redundant information, then you are out of luck. Compression may help in some cases, but if this is an activation key, I would recommend having keys of same length (and compression will not enforce this).

If this code is going to be passed over e-mail, then I see no problem in having an even larger key. Another option might be to insert hyphens every 5-or-so characters, to break it into smaller chunks (e.g. <code>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</code>).

blocks|key|3982493|text|在一般情况下，从任意的byte[]到字符串需要更多的数据，因为我们假设我们希望避免不可打印的字符。减少的唯一方法是在基础之前进行压缩--不管是什么(你可以比基数稍微高一点--64，但不多--当然，不再是“友好的”了)，但是压缩对于这么短的尺寸是不会真正起作用的。基本上你不能这么做。你想把一夸脱装进一品脱的锅里，但那不管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3982494|你可能不得不重新考虑你的要求。可能在内部保存BLOB，并发出一个较短的令牌(可能是10个字符，可能是一个guid)，它是对实际BLOB的键。|offset|length|style|BOLD|3982495|entityMap^0|0|1W|1|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

In the general case, going from an arbitrary byte[] to a string requires more data, since we assume we want to avoid non-printable characters. The only way to reduce it is to compress before the base-whatever (you can get a little higher than base-64, but not much - and it certainly isn't any more "friendly") - but compression won't really kick in for such a short size. Basically, you can't do that. You are trying to fit a quart in a pint pot, and that doesn't work.

You may have to rethink your requirements. Perhaps save the BLOB internally, and issue a shorter token (maybe 10 chars, maybe a guid) that is a key to the actual BLOB.

blocks|key|1476968|text|使用160位散列，希望没有冲突？它会短得多。如果可以使用查找表，只需使用128甚至64位增量值即可。比你的37个字符要短得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476969|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Use a 160bit hash and hope no collisions? It would be much shorter. If you can use a look-up table, just use a 128 or even 64bit incremental value. Much much shorter than your 37 chars.

I have a structure that I am converting to a byte array of length 37, then to a string from that.

I am writing a very basic activation type library, and this string will be passed between people. So I want to shorten it from length 37 to something more manageable to type.

Right now:

<ul>
<li>Convert the structure to a byte array,</li>
<li>Convert the byte array to a base 64 string (which is still too long).</li>
</ul>

What is a good way to shorten this string, yet still maintain the data stored in it?

Thanks.

Shorten String from Byte Array

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个结构，我正在转换成一个长度为37的字节数组，然后从它转换成一个字符串。我正在编写一个非常基本的激活类型库，这个字符串将在人与人之间传递。所以我想把它从37长度缩短到更便于打字的东西。现在：将结构转换为字节数组，将字节数组转换为基64字符串(这仍然太长)。什么是缩短字符串的好方法，但仍然维护存储在其中的数据？谢谢...

问缩短字节数组中的字符串
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问缩短字节数组中的字符串EN