1. Introduction
We are witnessing a tipping point in ecommerce as more and more people purchase goods online. Yet most clothing purchases are still made within physical stores (Clement, 2018). This is due to the fact that purchasing clothing and shoes online is a still a gamble for consumers. When they do shop online, many customers order multiple sizes with the purpose of returning the ones that don’t fit. Not surprisingly, as online shopping for clothing and shoes grows, so have return rates. According to a recent study, 20% of purchases made online are returned, 52% of those indicated a problem with fit to be the reason for return (Orendorff, ). Presenting reliable and personalized size recommendations to shoppers is a core concern for retailers. Not only will accurate recommendations reduce return rates, they will also increase engagement and boost consumer loyalty.
True Fit is an industry leading provider of personalized size recommendations. Its fit and size recommender systems support detailed size recommendations at hundreds of different retailers with thousands of different brands. As an aggregator of retail fashion data, combining catalog and transaction data across all of its retail partners, there are unique challenges around understanding garment sizing.
A key step to serve accurate size recommendations is understanding the wide variations in garment sizing. In the real world, the same size strings may not consistently have the same meaning. For example, the size “small” in a regularsize brand means a smaller fit than a “small” in a plussize brand. On the other hand, sizes that look different, such as “S”, “SM”, “SML”, and even “P” within the same brand may all mean the same fit. The relationship between different sizes, for instance “S” and “6R”, is less obvious; they may or may not mean a similar fit depending on which brand each belongs to. In order to make sense of all this variation, we embed (or normalize) all the sizes across brands into a shared universal space, where sizes can be meaningfully compared with each other. We call this task “size normalization”. In this paper, we will focus on size normalization into a 1dimensional space.
Traditionally, domain experts conduct size normalization by manually inspecting the sizes and the related products. This is an expensive and timeconsuming process. We propose an automated size normalization framework, as shown in Figure 1, using only transactions data—more specifically, data on sales where the item was not returned. We believe that size normalization systems can leverage this automated framework as part of their workflow to improve their effectiveness and efficiency.
Using sales data to normalize sizes brings two main challenges. First, connections between sizes across brands can be sparse. We rely on customers who have purchased across multiple brands to relate sizes to each other. When there is little to no customer overlap, we must rely on derived or secondary connections. Second, user buying preferences are inherently noisy due to each individual’s taste. Our algorithm strives to be robust to such noise.
Organization of the Paper: We first present related research on fashion size recommendations. We then propose an automated framework to compute size normalizations strictly using sales data. Two optimization approaches are presented: a gradient descent based method and a quadratic program. Subsequently, we propose an evaluation framework for the size normalization problem and use it to compare the two optimization methods against a humanannotated size normalization approach.
2. Related Work
There is currently a variety of work that provides size recommendation. Some tools focus on electronically measuring a user’s body shape from users’ pictures ((Neophytou et al., 2013), (Peng et al., 2014)
), while others suggest a user’s body measurement by using a multiple linear regression approach and a neural network approach when given information on a user’s stature, weight, span, and age
(Löfström et al., ). However, in a study, authors have found that most of the users who received the correct size recommendation would not buy the size recommended due to fit preferences (Vecchi et al., 2015).In order to address users’ individual fit preferences, many in the literature suggest leveraging users’ return information and past transactions data (Misra et al., 2018). One such approach uses a skipgram based approach to size recommendation and captures the users’ fit preferences by utilizing the product content data and purchase return information (Abdulla and Borar, 2017)
. The intuition is that all products purchased by a user are similar in size and fit; based on that information, the authors construct joint probability functions for products purchased by users. The size recommendation is then formulated as a binary classification, using the gradient boosted trees method, to predict whether a product and size will fit a specific user or not. In a subsequent work, the authors provide an additional graphbased approach methodology for size recommendation on shoes
(Singh et al., 2018) to combat sparsity and address the cold start problem. Furthermore, a group at Amazon suggests a latent factor model that predicts whether a product will fit small, right, or large to a specific customer (Sembium et al., 2017). The authors first present an algorithm to compute the true (latent) size of a user and a product using various loss functions. After computing the true sizes of users and products, a recommendation is made. This model was tested on Amazon shoe datasets. A Bayesian approach was later proposed that allowed a more robust fit probability
(Sembium et al., 2018). This approach was tested on the same Amazon shoe dataset and showed better results than the original nonBayesian approach.In many of the proposed work described above ((Sembium et al., 2017), (Sembium et al., 2018)), the data used to compute the products’ true sizes are based on clean catalog data. For example, the size “small” would always be spelled “SM”, and always holds the same meaning. However, as we observe in the real world, the data comes in many different forms and often contains typos and mistakes. There seems little work in understanding and standardizing fashion products. Our work targets this specific problem of size normalization in order to provide more accurate information and inputs for size recommendation systems.
3. Methodology
The task of size normalization is to map each unique size in each size type to a scalar value such that sizes that offer the same fit are close together. We approach this problem in 3 steps:

First, we group the raw size strings within each brand into brandspecific “size types” such as alpha sizes, numerical sizes, plus sizes, etc. by analyzing their string pattern and sorting them monotonically.

Next, we create “frequency matrices” that counts the copurchases of sizes across brands and size types using the sales data.

Finally, we infer a scalar value for each size in each brandspecific size types to minimize the distance between pairs of sizes that are commonly copurchased together.
Note that we consider each category separately; for example, we learn a set of normalized sizes for Women’s Shoes, another set for Women’s Tops, another set for Men’s Suits, and so on. Within each category, we consider all the brands. Size normalization is therefore useful for comparing sizes across brands within the same category.
A list of all notations used is presented in Appendix A.
3.1. Size Type Inference
A size type is unique to each brand and is defined as a set of sizes with a strict order, that is, each pair of sizes can be compared with greater than or less than. Specifically, sizes are compared by their semantic meanings, ie. how humans would order size strings without context. For example, sizes “Small” and “Large” from brand A can be in the same size type because “Small” is less than “Large”. and are both valid size types. is not valid, since we cannot be sure of the position of relative to the other sizes. Within a brand, we aim to partition all sizes into as few size types as possible. That is, while “S,M,L” and “XS,XL” are both valid size types, we prefer if they are together, “XS,S,M,L,XL”.
Size types mainly help address data sparsity issues: typically, we only observe transactions for a few sizes in a size type; knowing the order of sizes help us infer the normalized value for the rest of the sizes. As a bonus, size types help us visualize the relationship between sizes, as seen as in Figure 2.
The remaining of this section describes how to partition all the sizes within a brand into size types, and how to determine the ordering of sizes within each size type.
3.1.1. Partitioning
We propose a distance measure between size strings, then based on the distance measure, we partition all sizes available for sale within a brand into disjoint clusters. The resulting clusters are the (unordered) size types. Note we run this for each brand independently; the result is that each brand has its own set of size types.
The proposed distance measure between size strings is computed on top of string “tokens”. The tokenization procedure works by applying regular expressions to capture substrings that are semantically meaningful (ie. sequences of numbers, sequences of characters, and punctuation) and assigning them each a token type (ie. NUMER, ALPHA, and OTHER). For example, “14P” is parsed into [“14”, “P”] with the pattern [NUMER, ALPHA]. “12.5” is parsed into one token, [“12.5”], with pattern [NUMER]. “EXTRA SMALL WIDE” is parsed into [“EXTRA SMALL”, “WIDE”], with pattern [ALPHA, ALPHA]; as an exception, the word “EXTRA” followed by an alpha token is considered the same token.
Next, sizes are grouped by their token type pattern. For example, “14P” with pattern [NUMER, ALPHA] is in a different group than “SML” with pattern [ALPHA]. A pair of sizes with different patterns have infinite distance; they definitely do not belong to the same size type. However, sizes within the same group still may or may not belong to the same size type. For example, “13P” and “13W” both share the pattern [NUMER, ALPHA], but clearly belong to different size types.
For each token pattern, we assume that the value at one of the positions is indicative of the size type. For example, in [“13P”, “14P”, “15P”, “13W”, “14W”], the second position has unique values of “P” and “W”, which indicates two size types. Intuitively, if there less unique values at a position, it is more likely to indicate different types. Using this insight, we define , the probability that position in a pattern of length is indicative of the size type, as follows:
(1) 
Here, we apply a softmax to normalize
into a value in a distribution. In addition, the hyperparameter
controls how smooth the resulting distribution is. This parameter will be used later to help with the clustering step.Let and be lists of tokens representing two size strings, both with the same token pattern of length . The similarity and distance between and are defined as follow:
(2) 
(3) 
With this distance measure, any classical clustering algorithm can be employed. We use the offtheshelf implementation of Aggolomerative Clustering with complete linkage from scikitlearn (Pedregosa et al., 2011)
. We set the number of clusters to maximize the Silhouette distance. Importantly, the Silhouette distance does not inform us when there should be only one cluster. We make this decision when the offdiagonal elements of the distance matrix has a standard deviation less than a small value
. In practice, we first fix , then tune the value of to maximize the number of correct partitioning on a small handlabeled dev set. We found and to work well. The resulting clusters represent different size types.3.1.2. Sorting
After grouping sizes into size types, we sort the sizes using a binary classifier. With the input of two size strings, the classifier outputs 1 if the first size is semantically smaller than the second size, and 0 otherwise.
The training data for the model is taken from a limited set of size charts, with some data augmentation by randomly permuting the variations of a size string (eg. replacing “Small” with “SM”). Each row of data contains a pair of sizes, and , and is labelled 1 if is smaller than , and 0 otherwise. After data augmentation, we had rows of data. We used for training and for validation.
The classification model is a 1layer, 32dimensional characterLSTM (Hochreiter and Schmidhuber, 1997) followed by a fully connected layer and a sigmoid activation. In training, we concatenate the size strings (ie. into ) then pass it to the model to predict the binary label. At inference time, we pass both and into the model, and whichever has a higher score determines the order. We trained with the Adam optimizer (Kingma and Ba, 2014)
which was able to achieve 98% validation accuracy in 30 epochs. The resulting model was reused across brands and garment types.
3.1.3. Output
After size type inference, each brand contains its own unique set of size types. Each size in each brand is mapped to a sorted index within a size type.
3.2. Frequency Matrix
We use the sales data along with the size types from the previous section to compute the frequency matrix, which counts copurchases of sizes within each pair of size types. Let be the set of unique size types, , be size type and in . Let be the set of sizes in brand . Then an entry in the frequency matrix , counts the number of times size where and size where are purchased together. We recognize that some users with a lot of purchases may be bulkbuyers or are buying for others, and to counter this, we dilute the count of each user by the total number of purchases that user has made. Let denote the set of users, then, instead of counting 1 for each copurchase, we count for . The way to construct the frequency matrix is outlined in Algorithm 1.
The frequency matrix is made up of block matrices, each offdiagonal block represents the relationship between a pair of size types. In Figure 2, we show a colourcoded example of a block matrix between two size types. The brighter the color, the higher the count. We can see that a “S” in one size type is around a “5” to “6.5” in the other size type, an “M” is around a “6” to “10”, and an “L” is around an “8.5” to “11”. In dense blocks, we can see the relationship clearly, as shown in Figure 2. However, in sparser blocks, the relationship is not immediately obvious, and would need to be inferred transitively through other size types.
3.3. Size Inference
The frequency matrix informs us of the relationships between sizes across size types. In this step, we use those relationships to normalize sizes to a universal space. We learn a mapping of sizes that minimizes the weighted sum of squares between mapped values, where the weights are proportional to their entries in the frequency matrix. In order for the mapping to look realistic and prevent overfitting, we also add a regularization term. In this section, we describe the formulation in more detail, and show two implementations of the optimization procedure with quadratic programming and gradient descent.
3.3.1. Objective Function
The objective function that we consider here is simply the squared distance. For each pair of sizes and from size types and , we compute the difference between and we want to minimize the total squared difference multiplied by the penalty weights from the frequency matrix as shown in Equation 4.
(4) 
Furthermore, we often don’t observe any transactions for sizes on the extremities, such as XXS or XXL. And so, using only the above objective function, these sizes’ normalized values cannot be determined. Therefore, we add an extra set of regularization terms to the objective functions to make sure that within each size type, the normalized sizes are placed somewhat tightly together. This allows sizes like XXS and XXL to be “dragged along” with the other sizes in the size type. For each size type , we also minimize the distance between the location of the first size, in and the last size penalized by the minimum length of the entire sizerun in size type . The regularizer is shown in Equation (5).
(5) 
Overall, our objective is to minimize both terms.
3.3.2. Constraints
We impose one set of constraints that for each size type , the location of a larger size must be greater or equal to the closest smaller size by at least .
(6) 
3.3.3. Quadratic Program (QP)
This problem can be formulated as a quadratic program as shown in Figure 3.
(7)  min  
s.t.  
(8) 
The objective function (7) minimizes the weighted pairwise squared difference between normalized sizes across all size types such that the location of the next size must be greater than than the previous size in the same size type for all the size types. Constraints (8) specify that all sizes must be greater than 0. Note that the is arbitrary and is in place to ensure separation of the different sizes.
3.3.4. Gradient Descent (GD)
Since we cannot enforce hard constraints with gradient descent, we need to make several adjustments. First, to satisfy the size ordering constraint (6), we introduce variables such that:
(9) 
Thereby ensuring the strictly increasing order of normalized sizes within a size type. In order to further ensure the minimum margin of , we introduce a hinge loss:
(10) 
The complete objective we optimize is thus:
(11) 
In practice, we found that and work well. This indicates a strong preference to ensure the minimum margin and a weak preference for sizes to stay close together. These values were tuned using another category of garments: Men’s suits. Although the sizing for Men’s suits is naturally different from other categories, we found that the resulting hyperparameters work well empirically.
Note that while the reparameterization to (Equation 9) is not absolutely necessary, we found that in practice the optimization was a lot faster and more stable using it.
4. Experiments and Results
Normalized sizes, learned with QP and GD, are compared against a set of humanannotated normalized sizes on an evaluation system described below. Human annotators were able to use any data (including size charts, product manufacturing specifications, and so on), while our method relied solely on sales data.
4.1. Evaluation System
With the assumption that a user’s true size does not change much in a short period of time, we can expect that the sizes of that user’s purchases in that period of time to be close, or “consistent”, in the normalized space. Measuring how well this holds across all users would inform to what extent we are achieving the goal of making sizes in the normalized space comparable. To do so, we propose an evaluation framework that measures the “consistency” of normalized sizes. The system takes as input a set of size normalization mappings and a set of test cases. Each test case is a pair of purchases, A and B, made by the same user close in time. The system looks up the normalized value of the size purchased in A, then returns the size in B with the closest normalized value. That is, the system tries to predict the size purchased in B using the size purchased in A using normalized sizes. When a size does not have a normalized value, the system abstains from making a prediction.
Two metrics are measured.

Coverage: for how many test cases were predictions made.

Accuracy: out of all the predictions made, how many of them were correct
The definition of correctness is slightly nuanced. Variants of the same size can be normalized to exactly the same number—this happens often with human annotators. For example, let’s say that “12 Regular” and “12” both map to the same normalized size, and the target answer is “12”. In this case, either prediction should be correct, as both sizes indicate the same fit. If we assess correctness by string comparison, we would wrongly mark a correct prediction as incorrect half of the time. Instead, we defined “correct” to be when the humannormalized size of the prediction and the target are equal.
4.2. Train and Test Data
The data we used to train and test is a two year snapshot of sales data from a subset of True Fit’s cooperative of fashion retailers. Each sale contains which size was purchased, what other sizes were available at the time, and an anonymized user id.
In total, the dataset contains 56 retailers and 5918 brands. There are approximately 60 categories ranging from Men’s Tops to Unisex Kid’s Shoes. The two year snapshot of sales data represents the purchases of 187 million users across 329 million orders which account for 827 million total purchased items. Across the products in this dataset, there are approximately 29 thousand distinct sizes and 150 thousand distinct product size sets. The category with the highest variation of sizes is Women’s Bottoms with approximately 6,500 distinct sizes (and 16 thousand size runs). And finally the highest variation of product size sets is in the category of Women’s Shoes with approximately 35 thousand distinct product size sets (comprised of groupings of approximately 5,400 women’s shoe sizes).
Out of the two years of data available, we used the first year (May 2016  Apr 2017) for training size normalization mappings. The second year (May 2017  Apr 2018) was set aside for testing. We chose to train on a full year to reduce the effects of seasonality.
Around 400k and 300k test cases were randomly sampled for women’s shoes and women’s dresses respectively. Among these, 35% and 44% occurred in the first year (data used for training), and the rest in the second year. Each test case was generated by sampling two purchases from the same user made within the same month, and filtering out trivial scenarios (e.g. both purchases were of the same product). The same user would not be used in another test case within that month.
4.3. Experimental Setup
For GD, we used the Adam optimizer (Kingma and Ba, 2014) with learning rates of , and trained for iterations with each learning rate. For QP, CPLEX 12.8 is used with default parameters and a time limit of 600 seconds.
4.4. Results
First, Table 1 shows the coverage in the training and test data throughout the two years. The high coverage in the first year (training set) shows that our procedure was able to assign size mappings to the vast majority of sizes used in practice. The 10% lower coverage in the second year as compared to the first year is expected, since more brands are introduced over time. Both optimization methods, QP and GD, have the same coverage.
First Year Coverage (Training Set)  Second Year Coverage (Test Set)  

Women’s  136,081/139,164 (98%)  225,854/254,199 (89%) 
shoes  
Women’s  132,077/136,774 (97%)  148,039/170,847 (87%) 
dresses 
Table 2 shows the accuracy of various size normalizations throughout the two years. It appears the test accuracy (accuracy in the second year) is lower than training accuracy for our automatic size normalizations. We also include the accuracy of humanannotated size normalizations. Note that the human annotation process does not use a traintest split; sizes were normalized without transaction data. However, it does show us a benchmark of reasonable performance. While both GD and QP are almost on par with humanannotated normalizations in the training set, the results are up to 8% worse on the test set. This is an indication that we are perhaps overfitting on the training data.
First Year Accuracy (Training Set)  Second Year Accuracy (Test Set)  
GD  QP  Human  GD  QP  Human  
Women’s  62%  62%  64%  60%  60%  67% 
shoes  
Women’s  58%  58%  59%  50%  50%  58% 
dresses 
We observe that both optimization procedures, QP and GD, appear to perform equally well in terms of accuracy. Figure 4 shows a subsample of normalized sizes produced by GD and QP in women’s dresses and women’s shoes. This is expected as they are both optimizing for very similar objectives. Upon inspection, it turns out both actually produce very similar normalized sizes. However, QP has two advantages over GD. First, it is orders of magnitudes faster (Table 3). Second, it can achieve the global optimal most of the time. We don’t have the same peace of mind with GD, since we’re always left wondering if the optimization could have worked better.
GD Runtime  QP Runtime  

Women’s shoes  3341s  33s 
Women’s dresses  1206s  5s 
5. Conclusions and Future Work
This work explores an automated way to normalize sizes into a universal space using sales data. We introduce a fast and scalable solution and show experiments run on realworld datasets. We propose an evaluation framework for this task, and show that the automatic size normalizations perform just shy of human performance in the training set.
There are a couple of interesting opportunities for future work. First, size type inference (Section 3.1
) is a crucial step because any mistake there would limit the performance of everything downstream. Our proposed algorithm is static and based on heuristics. Perhaps it can be framed as a learning problem and continuously improve. Second, since our method is completely dependant on transaction data, it is not robust when there are very few transactions. We suspect much of the drop in test accuracy may come from overfitting on a few transactions in the training data. It would be interesting to explore how to set priors for size normalizations to account for low data scenarios. This could involve using other sources of data such as size charts, brand properties, product manufacturing specifications, and so on. Lastly, we think it would be interesting to explore the possibility of using more than one dimension for normalized sizes. Some garments, such as dress shirts, are naturally measured by more than one dimension. Embedding all garments into a shared multidimensional space is very hard for humans, but should be feasible with a learned solution such as the one we propose.
References

Size recommendation system for fashion ecommerce.
In
KDD Workshop on Machine Learning Meets Fashion
, Cited by: §2.  Topic: fashion ecommerce in the united states. External Links: Link Cited by: §1.
 Long shortterm memory. Neural Computation 9, pp. 1735–1780. Cited by: §3.1.2.
 Adam: a method for stochastic optimization. arXiv preprint arXiv:1412.6980. Cited by: §3.1.2, §4.3.
 [5] A datadriven approach to online fitting services. Cited by: §2.
 Decomposing fit semantics for product size recommendation in metric spaces. In Proceedings of the 12th ACM Conference on Recommender Systems, pp. 422–426. Cited by: §2.
 ShapeMate: a virtual tape measure. In the 4th International Conference on 3D Body Scanning Technologies, pp. 3. Cited by: §2.
 [8] The plague of ecommerce return rates and how to maintain profitability. External Links: Link Cited by: §1.
 Scikitlearn: machine learning in Python. Journal of Machine Learning Research 12, pp. 2825–2830. Cited by: §3.1.1.
 Personalised size recommendation for online fashion. Cited by: §2.
 Recommending product sizes to customers. In Proceedings of the Eleventh ACM Conference on Recommender Systems, pp. 243–250. Cited by: §2, §2.
 Bayesian models for product size recommendations. In Proceedings of the 2018 World Wide Web Conference on World Wide Web, pp. 679–687. Cited by: §2, §2.
 Footwear size recommendation system. arXiv preprint arXiv:1806.11423. Cited by: §2.
 Looking for the perfect fit? online fashion retailopportunities and challenges. In Conference Proceedings: The Business & Management Review, Vol. 6, pp. 134–146. Cited by: §2.
Appendix A Notations
Description  

Set of unique users  
Total number of unique users  
Set of unique brandsizetypes  
Total number of unique brandsizetypes  
Set of sizes in brand  
Total number of sizes in brand  
Counts of how many times size in size type is purchased together with size in size type  
Variable denoting the location of size from size type  
Auxiliary variable to compute in GD  
probability that position is the indicator of the size type 
Appendix B Size Partitioning Example
A working example is shown to help provide more clarity to the algorithm described in Section 3.1.1. Consider we wish to partition a list of sizes into size types. Given the size strings, we first partition the sizes by regular expressions as shown in Table 5.
Raw size strings  Partitioned sizes 

1.5M Youth  [’1.5’, ’M’, ’YOUTH’] 
10.5M Toddler  [’10.5’, ’M’, ’TODDLER’] 
11.5M Toddler  [’11.5’, ’M’, ’TODDLER’] 
11M Toddler  [’11’, ’M’, ’TODDLER’] 
12.5M Youth  [’12.5’, ’M’, ’YOUTH’] 
12M Toddler  [’12’, ’M’, ’TODDLER’] 
13M Youth  [’13’, ’M’, ’YOUTH’] 
1M Youth  [’1’, ’M’, ’YOUTH’] 
2.5M Youth  [’2.5’, ’M’, ’YOUTH’] 
2M Youth  [’2’, ’M’, ’YOUTH’] 
3.5M Youth  [’3.5’, ’M’, ’YOUTH’] 
3.5W Youth  [’3.5’, ’W’, ’YOUTH’] 
3M Youth  [’3’, ’M’, ’YOUTH’] 
4.5W Youth  [’4.5’, ’W’, ’YOUTH’] 
4M Youth  [’4’, ’M’, ’YOUTH’] 
4W Youth  [’4’, ’W’, ’YOUTH’] 
5.5W Youth  [’5.5’, ’W’, ’YOUTH’] 
5M Youth  [’5’, ’M’, ’YOUTH’] 
5W Youth  [’5’, ’W’, ’YOUTH’] 
6.5W Youth  [’6.5’, ’W’, ’YOUTH’] 
6M Youth  [’6’, ’M’, ’YOUTH’] 
6W Youth  [’6’, ’W’, ’YOUTH’] 
7W Youth  [’7’, ’W’, ’YOUTH’] 
In this example, all sizes have the same pattern, [NUMER, ALPHA, ALPHA]. There are 19, 2, and 2 unique tokens in each position respectively, for a total of 23 unique tokens in total. We use this information to compute :
We then pass through a softmax with . The softmax function normalizes into a distribution, and the parameter makes the values more polarized. Note that more polarity effectively makes points that are closer to be even closer, and points further apart to be even more further apart. Therefore, finding the right amount of polarity helps to determine the right number of clusters. This is why we opt to fix the method to find number of clusters, then tune the parameter until we reach a value that can accurately determine the number of clusters on a development set. The result of softmax is:
Next, Equation 3 is used to compute the distance between all pairs of sizes. This resulting distance matrix is shown in Figure 4(a). The Silhouette Score is computed on all possible number of clusters, see Figure 6
. In this case, it appears that 3 clusters is optimal. Finally, we run Hierarchical Clustering with the aim to find 3 clusters. This results in 3 size types, as one can see in Figure
4(b).A reader who understands US kids shoe sizing might notice that the “M” in the toddler size represents “months”, while the “M” in the youth size represents “medium”. Our proposed method gets around the need to assign such meaning to sizes while still achieving semantically meaningful partitions most of the time.
Comments
There are no comments yet.